A user segment is a collection of end-users/agents, defined by a specific set of attributes, used to determine access to Help Center content.
User segments are the building blocks for user permissions. You apply user segments to a Help Center, a knowledge base article, or a topic in your community to define viewing access. And you use user segments to build management permissions that you apply to knowledge base articles to define editing and publishing permissions.
There are two built-in user segments by default:
- Signed-in users includes users who are signed-in to your Help Center
- Agents and managers includes all agents and admins
You can create custom user segments to further refine those groups of users as follows:
- Signed-in users (internal and external) - these segments are created in Zendesk Support and can be based on tags, organizations, individual users, or all of them combined
- Staff (internal) - these segments are created in Zendesk Support and are based on tags, groups, individual users or all of them combined
Guide admins have access to all content, regardless of any user segments they belong to. You must be a Guide admin to create user segments.
Understanding access restrictions for user segments
- Signed-in users can be restricted by tags, organizations, individual users, or a combination of all three. Tags must be on the user or an organization they belong to.
When you create a user segment based on tags for signed-in users, you can require that all specified tags match for the agent to be included and/or you can require that at least one of the specified tags match for the user to be included. For organizations, the user must belong to at least one of the specified organizations.
Signed-in agents must have any required tags, agents do not have to belong to any of the specified organizations to be included in the user segment, so the organization is ignored for agents.
Individual users do not need to meet any filters to be included in a user segment, in fact if only individual users are in a user segment, the segment will contain only those users.
- Staff (agents and admins), can be restricted by tags, groups, individual users, or a combination of all three.
When you create a user segment based on tags for staff, you can require that all specified tags match for the agent to be included or you can require that at least one of the specified tags match for the agent to be included. For groups, the agent must belong to at least one of the specified groups.
Guide admins have access to all content, regardless of the user segments that they belong to.
Individual users do not need to meet any filters to be included in the user segment, and if only individual users are in a user segment, the segment will contain only those users.
To define user segments, refer to the following table
User role | Restrict by tags
(users need all tags) |
Restrict by tags
(users need any of the tags) |
Restrict by organizations
(users need at least one org) |
Restrict by groups
(users need at least one group) |
Restrict by individual users |
---|---|---|---|---|---|
Signed-in users | YES | YES | YES
(ignored for agents) |
NO | YES |
Staff | YES | YES | NO | YES | YES |
Creating user segments
The two access types for user segments are: signed-in users and staff. You can create custom user segments to further refine those two groups of users as follows:
- Signed-in users (internal and external) - created in Zendesk Support, these segments are based on tags, organizations, individual users, or a combination of all three.
- Staff (internal) - created in Zendesk Support, these segments are based on tags, groups, individual users, or a combination of all three.
You can create as many as 200 user segments per account. If you have multiple brands in your account, then your user segments are shared across all brands.
Guide admins have access to all content, regardless of the user segments they belong to.
- In Guide, click the User permissions icon (
) in the sidebar.
- On the User Segments page, click Add new.
If you receive an error message, that means you have reached the maximum number of 200 user segments. You can delete some user segments if you want to continue.
- Enter a Name for this user segment.
- Select a User type as the base of your user segment.
- Signed-in users - includes internal and external users who create an account and sign in to your Help Center.
- Staff - is for internal users only, including agents and Guide admins.
- Click Filter by tag.
Then click the drop down menu to select a tag:
- Users and organizations matching ALL of these tags: all of the tags must be on the user or org to be included in the user segment.
- Users and organizations matching ANY of these tags: one or more of the tags must be on the user or org to be included in the user segment.
You can add up to 50 tags each in Users and organizations matching ALL of these tags and Users and organizations matching any of these tags. Not all available tags appear on the list, so use search or scroll to find the tags that you are looking for. You can choose any tag that is applied to existing users or organizations. The tags can be on the user profile or, in the case of end-users, inherited through an organization.
A list of matching users appears to your right. Agents do not appear on the list of matching users. If there are more than 30 matching users, click View all matching users, then you will see the full list.
Note: You must have user tags enabled to create a user segment based on tags. For more information, see Enabling user and organization tagging). - (Optional) You can further refine your user segment by doing one of the following:
- For signed-in users - if you want to restrict by organization, then select an organization from the drop down menu, and click Filter by organizations.
- For staff members if you want to restrict by group, then select a group from the drop down menu, and click Filter by groups.
The user must belong to at least one of the organizations or groups to be included in the user segment. You can add up to 50 organizations or groups to a user segment. The exception is that organization is ignored for signed-in agents. Agents do not need to belong to any of the organizations to be included in the user segment.
The list of matching users will update accordingly.
- To add users to a new user segment, click Add individual users.
You can add up to 50 users to a segment. Likewise, you can add individual users, as well as any group, tag, or organization filters. As you add users, the list of matching users updates.Note: If you add individual users, they are added to the user segment regardless of any group, tag, or organization filters that you may have already set.
- Click Create segment.
See the following topics for more information on how you can apply user segments:
107 Comments
Jordan Prangnell,
It gets a little tricky from what I understand, but assuming you have Enterprise:
This is done as a combination of the permissions set on the articles and the Agent user profiles.
You'll want to set User Segments up as needed and add them to the Articles. I suggest strategically planning this out and documenting as best you can to refer to later.
Also, update the Article "Managed by" selection to roles you've set up that would be allowed the Manage Guide permissions. We have several layers of this based on experience to allow flexibility. Again, documentation is key!
Here are a couple of visuals to help I hope!
Articles:
Agent Profile:
I hope this points you in the right direction!
Sincerely,
Heather
Apologies if this has been covered, but is there any way to create a segment based on the following criteria
(User matches any of a certain tag) OR (belongs to X organization)
I'm trying to set up a segment for a group of customers that share one basic tag, but I also want to include internal end users from my own organization that are not agents.
Example: User has tag "Special", OR Organization is "My Company Name"
It seems that no matter what I try, either I can only show the users with the tag(s) I need, or users from a certain organization, but not both. Thoughts anyone?
Oof. Disregard my last comment. I just added a new tag to my company's org, and added that tag to the former condition. Problem solved.
Thanks for letting us know that you got it figured out, Jimmy!
Hi, apologies if this is covered elsewhere but is there any means to arrange the user segments or management permissions in any sort of order, i.e alphabetical?
Hi Lauren,
No, the user segments do not currently have sorting options beyond the separation of Staff and Signed-In User segments.
Every link I find to " Creating user segments for Guide user permissions" points back here, to this article. Apparently there used to be an article by that name here, but it's not available here anymore -- this one is just about adding individual users. Can someone point me to the correct article on creating user segments?
So sorry about that Marci! I'm in contact with the documentation team about this. Looks like we have a little redirect loop going,
Haha, it happens! ;-) Thanks for checking into it!
Is this feature currently being upgraded or in development? I followed the directions here and none of the tag/group restrictions are actually restricting anything. In these screenshots, there are 57 matched users when no group restrictions are applied and 57 matched users when one group restriction is applied, you can even see the group listed in the matched users for the one match.
Hey Oliver,
This feature should allow you to restrict access based on the group the user is assigned to. Even after saving the user segment and applying that segment to an article, others are still able to view the content?
If so, I'm happy to create a ticket on your behalf to dig into this further.
Let me know!
Добрый день. А как создать сам тег?
Hello,
I'm currently receiving the following error when I'm trying to add another organization for logged-in users.
Can you assist?
Are end users of Guide still able to use IE?
Ryan Nagle Are you still seeing this error? When I have seen it in the past, it has usually been a permissions or network issue. Logging out entirely, closing the browser, and restarting has seemed to fix it.
It would be helpful to have user segments also consider custom user fields as evaluation criterion. Right now, our team would need to have an external process update tags via API, which is not slick. Having extra user data available between support and guide would make this process far easier.
Mary Jo Trapani - Our end users can no longer access Guide through IE because of an error on the Zendesk sign in page. If we bypass the sign in screen, then the site works with no problem.
If you don't use a sign in for Guide, then I'd suspect that it will likely work. However, there's no guarantee since it's an "old" browser.
Please sign in to leave a comment.