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
Hi Bart!
It's not possible to have two separate ticket landing pages, but if you're on Support Professional or Enterprise you have the option of creating custom ticket forms, which would allow you to serve two different form options for your users, depending on their needs. You can read more about those here.
Hi There, I really want to use this feature but I am having issues. I want End-User to be able to view different user segments which is governed by tags/and or organisation but it is not working. If i change the end user to a light agent it then allows access. Please can somebody tell me what i am doing wrong?
Hi Jason,
There are a few different pieces to this setup:
1 - tag the orgs or users with the tags for their user segment
2 - create the user segment in Guide and assign the tag and/or organization to it
3 - assign the help center section to the appropriate user segment
Sounds like either the help center section is assigned to Agents & Managers, the tags aren't assigned on the user segment correct or the users and/or orgs don't have the correct tags on them to connect them to the user segment.
Hope that helps!
Maggie
Maggie,
All the user segments are correctly tagged. The issue is if that if they are end users they cannot view but if i change their role to light agent they can then view. I am assuming that by the information supplied the users role shouldn't matter?
Hi Jason,
And the end users are correctly tagged? Seems like it should be set up to work. Do you have a screen print of one of the user segments, the section assigned to the user segment and the end user with the segment assigned? That might help figure out where the configuration isn't working.
Thanks,
Maggie
Thanks for jumping in to help out, Maggie!
Hey there, am I able to manipulate user segments if I am on the "Support - Essential" Plan coupled with the "Guide - Professional" plan?
Hi Jessie,
This support platform is great and the comments very to the point.
I am also stuck with what Sheldon wrote.
https://support.zendesk.com/hc/en-us/articles/115007686307/comments/360000030828
In summary, to manage the access to sections, how can I add multiple user segments?
I just couldn't find a way to add multiple user segments to a section. For specific section, I need to give access to a user segment A (with signedin end-users with certain tags) and user segment B (my staff in a certain group). I created the user segments for both, they work perfectly but I can only define one user segment as access right to a section.
Many Thanks.

Hi Konrad,
I'm chiming in from Zendesk Support on your question.
If you're on Support Essential and Guide Professional you will have a limited version of the User Segments feature. You would be able to limit for agent only content, but because the Essential plan does not include the Tags feature you would not be able to limit based on those.
All the best,
Hi Gail,
Many thanks for the input but I am in Support Team and Guide Professional plans.
I can create tags, user segments, assign sections to different user segments, etc...
I am stuck in one place where I need to assign a section both to
a) an end-user segment and
b) an agent-user segment.
When creating user segments, ZenDesk does not allow me to add users both from end-users and agents (staff).
ZenDesk forces me to choose either from the signed in users (assume these are end-users, and does not include staff even if they have the same tag as the end-user?), or from the staff.
I also couldn't find a way to add multiple user segments to a section (this would have made my life so easy)...
Appreciate if you can think of any solution to my problem?
Many Thanks,
Hello,
The update for user permissions is much appreciated. I do have a question though. Is it correct to say that with these updates, user segments can only be used to restrict who can view certain sections, but cannot be used to restrict who can edit certain sections? I would like to grant permissions to certain agents to edit certain sections of the Guide but not the whole guide. Is that possible yet?
Hello Cenk,
Applying multiple user segments is not possible at this time, i'm afraid.
I see you've submitted a ticket to us on this though that was escalated to our Tier 2 team. The agent assigned to your ticket can go into a deeper dive on your particular use case and requirements though and may be able to help provide a workaround.
If you have the condition "Signed in users with user tag xxx", does an agent that have the same user tag have the permission to read that article?
I see how I can set user segments so certain end-users can see posts etc, but what I also want to do is disable the ability for end users to create posts. Is that possible? Ideally, just admins would create a handful of posts that end-users could comment on/ask questions but not be able to create their own posts.
Hey Amanda -
There's not a way to do that natively; you would need to use some custom code to hide the "new post" button from end-users' visibility.
I'm curious why there is a limit of 200 user segments, and if there would be any way to increase that limit.
Hi Marshall -
The user segment limit is due to technical and performance consequences that arise above that threshold. It's not something that can be increased.
If you want to share more about how you're using user segments and why you would need more, we'd be happy to see if we can help you come up with a workaround or different workflow that can accomplish what you're looking for.
Hi Nicole,
We leverage a single Help Center to support a number of different companies who use our software. Sometimes those companies have help content specific to them, so historically we restricted sections to just those organizations. We'll exceed 200 companies who need custom content soon, and so far the only alternative we can think of is trying to deploy 200+ brands to keep things separate. That's obviously not ideal so I was hoping the limit could be increased
Thanks for the additional detail, Marshall. I'm going to check around with some folks internally and see if we can come up with a creative solution for you.
Hi,
We want to serve articles to users via tickets, but not have a public KB. I've read through this and want to confirm that if we tag our users:
I know we will need to upgrade to the next level of Guide - we're on Lite right now.
Does this sound correct?
Hi Mary Beth,
From what you've written, sounds like you actually want to de-active your HC (https://support.zendesk.com/hc/en-us/articles/115001440027-Deactivating-your-Help-Center) so it's not available to end users. Tagging just allows you to control the content that users see in the HC but doesn't actually control who can get to the HC.
Hope that helps!
Hi Maggie Ungerboeck ,
Thanks for your response.
I'm not sure. We still want to serve articles to customers in tickets. If we deactivate, I'm not sure customers will be able to see the served articles?
Hi Mary Beth,
I agree - I don't think they will be able to see them if you deactivate but then your HC will be live to your customers which you don't want either. We don't have this configuration so unfortunately I'm not familiar with the details. Maybe post this in their Guide Community area to see if there are others who have the same set up? You'll probably reach a wider audience in there and might be able to find someone who can better help!
Thanks,
Maggie
Thanks, Maggie Ungerboeck,
@Marshal
We were able to reach out internally and unfortunately was not able to come up with an alternative workflow that would address this limitation. The best option is to make a post in our Product Feedback Forum along with your use case for our Product Managers to view. This will help gauge interest from other users that are running into the same roadblocks
We greatly appreciate the time you take sharing your feedback us. Thanks!
Is there also a limit on the amount of tags that can be created?
Hi Jepruitt,
There's no way to set up a tag limit at this time. What workflow have you implemented that would require this limitation?
Hi Brett, thanks for the response. After reading that there is a limit of 200 user segments, I wanted to verify if there is also such a limit for tags.
Thanks for the clarification :)
You can create as many tags as needed for your account.
Awesome! Thank you for the information.
Please sign in to leave a comment.