Creating client tag permissions in ContactManager

The base application comes with a set of tag permissions that permit a user to create, delete, edit, and view contacts with any tag. You can add permissions that control access to contact tags at a more granular level.

Tag permissions can cause more restriction on access to contacts than you might intend. A set of permissions for a single tag apply exclusively to that tag. If you want to control access to contact tags at this more granular level, create a set of tag permissions for every contact tag in your system. Then create roles using tag permissions and assign the roles to users based on the tags you expect each subset of contacts to have.

For example, a user is in a role that has only the Client tag permissions and no other tag permissions. That user cannot see contacts that have additional tags, even if those contacts have the Client tag. That user was previously able to see a contact with the Client tag, but now can no longer see that same contact. The reason is that the contact filed a claim, and ClaimCenter automatically tagged the contact with the Claim Party tag. Since the user’s role does not have the Claim Party tag permissions, that user can no longer see the Client contact. Adding the Claim Party tag permissions to the role enables the user to see and work with contacts who have both tags, Client and Claim Party, and no other tags. However, with only these two sets of tag permissions, this user would not be able to see a contact that is tagged both as a Client and a Vendor.