Currently when you restrict access to a Section in a Community category the user has to have all of the tags in their user profile.
This is causing problems when adding Sections that need to be visible to some users and not others.
Zendesk is being used by a variety departments in an organization.
Each departments (different software applications) generally have their own unique user base butneed sole access to some of the sections in the Community, shared access with other departments on other sections, and no access to other sections.
User Base A has tag A
User Base B has tag B
User Base C has tag C
Section 1 only allows users with tag A access.
Section 2 only allows users with tag B access.
Section 3 should be accessible to both Users A&B
Section 4 only allows users with tag C access
Section 5 is added and should allow access to B&C
The issue lies with Sections 3 and 5. You have to created an entire new "User segment" and apply this to all users in User Base A and B and not to other users bases in the system.
This can only be done with API's (not feasible to orgs with no development resources) or CSV uploads.
Both take time and have to be done over and over again when you have groups that both need access to the section.
A much easier way would be to simply allow access if you have one of the tags lists. This would (possibly) require the creation of the new User Segment with the tags of the users who need access instead of having to create a new segment and add the segment to ALL use those groups.
Please sign in to leave a comment.