Creating user segments for help center user permissions


A user segment is a collection of end users and agents, defined by a specific set of attributes and used to determine access to help center content. User segments are the building blocks for both viewing and management user permissions.


What's my plan?






All Suites

Growth, Professional, Enterprise, or Enterprise Plus









Support with

Knowledge Professional or Enterprise






Summary: ◀▼
You can create user segments to control access to help center content by defining groups based on tags, organizations, groups, or individual users. User segments determine who can view or manage articles and community topics. There are built-in segments for signed-in users and staff, and you can customize segments to refine permissions for internal and external users. Knowledge admins have full access regardless of segments.


A user segment is a collection of end users and agents, defined by a specific set of attributes
and used to determine access to help center content. User segments are the building blocks for
both viewing and management user permissions.



Viewing permissions: You can apply:
One user segment to each community topic to define viewing access for those
resources. Users must belong to the specified user segment in order to have
access.
Up to 10 user segments to each article in your knowledge base. Any user who belongs
to at least one of the applied user segments will be able to view that article.



Management permissions: You can apply user segments when building management
permissions for articles. After they're built, you can apply management permissions to knowledge
base articles to define who has permission to edit and publish those articles.


There are two built-in user segments by default:



Signed-in users, includes users who are signed-in to your help center

Agents and admins, includes all agents (including light 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 Admin
Center and can be based on tags, organizations, individual users, or all of them
combined.

Staff (internal). These segments are created in Admin Center and are based on
tags, groups, individual users, or all of them combined.


Knowledge admins have access to all content, regardless of any user segments they belong to.
Because Knowledge admins have access to all content, their user profiles will display all custom
user segments. You must be a Knowledge admin to create user segments.
This article covers the following topics:
Understanding access restrictions for user segments
Creating user segments




Understanding access restrictions for user segments

Every user segment starts with a base user type of signed-in users or staff (agents and
admins). From there, you can create a subset of users based on tags, organizations, groups,
and individual users as follows:

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.
Knowledge 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



Table 1.










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), are created in Admin Center. These
segments are based on tags, organizations, individual users, or a combination of all
three.

Staff (internal), are created in Admin Center. 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.
Knowledge admins have access to all content, regardless of the user segments they belong
to.

To create a user segment
In Knowledge admin, click User permissions
( ) 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 Knowledge
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 additional individual users, regardless of the number of users in the group,
tag, or organization filters you've specified. 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:

Set view permissions on knowledge base articles
Create management permissions to define agent
editing and publishing rights
Set view access for community topics






{
"@context": "https://schema.org",
"@type": "TechArticle",
"@id": "https://support.zendesk.com/hc/en-us/articles/4408837707290-Creating-user-segments-for-help-center-user-permissions",
"url": "https://support.zendesk.com/hc/en-us/articles/4408837707290-Creating-user-segments-for-help-center-user-permissions",
"headline": "Creating user segments for help center user permissions",
"description": "You can create and manage user segments based on tags, organizations, groups, and individual users to control viewing and management permissions for help center content.",
"articleSection": "Setting roles and permissions for help center access",
"datePublished": "2021-10-16T05:15:19+00:00",
"dateModified": "2026-03-27T18:39:44.044858+00:00",
"inLanguage": "en-US",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://support.zendesk.com/hc/en-us/articles/4408837707290-Creating-user-segments-for-help-center-user-permissions"
},
"author": {
"@type": "Organization",
"name": "Zendesk",
"url": "https://www.zendesk.com"
},
"publisher": {
"@type": "Organization",
"name": "Zendesk"
},
"isPartOf": {
"@type": "WebSite",
"name": "Zendesk Help",
"url": "https://support.zendesk.com/hc/en-us"
},
"about": {
"@type": "SoftwareApplication",
"name": "Zendesk"
}
}
//
const ai_summary_style = document.createElement('style');
ai_summary_style.innerHTML = `#styled-article-body{padding:0 0 0}#article-body #docs-ai-summary{background-color:#f3f3f3;border:1px solid #d3d3d3;padding:10px 10px 6px;margin-bottom:16px}#article-body #docs-ai-summary #docs-ai-summary-toggle{font-size:.9em;font-weight:700;margin-bottom:4px;cursor:pointer;display:flex;justify-content:space-between;align-items:center}#article-body #docs-ai-summary #docs-ai-summary-toggle #up-triangle{margin-left:auto;padding-right:10px;display:none}#article-body #docs-ai-summary #docs-ai-summary-toggle #down-triangle{margin-left:auto;padding-right:10px}#article-body #docs-ai-summary #docs-ai-summary-content{font-size:.9em;padding-left:25px;padding-right:25px;margin-bottom:12px}`;
document.head.appendChild(ai_summary_style);

const toggleAISummary = () => {
const summary = document.getElementById("docs-ai-summary-content");
const upTriangle = document.getElementById("up-triangle");
const downTriangle = document.getElementById("down-triangle");
if (summary.style.display === "none") {
summary.style.display = "block";
upTriangle.style.display = "none";
downTriangle.style.display = "inline";
} else {
summary.style.display = "none";
upTriangle.style.display = "inline";
downTriangle.style.display = "none";
}
};

document.getElementById("docs-ai-summary-toggle").addEventListener("click", toggleAISummary);
//

