User segments
This guide covers how to create, edit, and manage Zendesk help center user segments at GitLab. Administrators should review the Administrator tasks section.
Technical Details
- Deployment type:
Standard - Sync repos
Note: This is closely tied to Management permissions groups
Understanding user segments
What are user segments
As per Zendesk:
A user segment is a collection of end users and/or agents, defined by a specific set of attributes, used to determine access to help center content.
Essentially, the use cases of user segments are:
- Restricting article visibility to specific teams
- Controlling who can edit/publish articles (via management permissions)
- Creating team-specific content sections
Note: You can belong to multiple user segments.
How we manage user segments
While Zendesk offers a full way to manage user segments via the UI, we turn to a more version controlled methodology. This allows for a set review process, the ability to perform rollbacks as needed, etc.
That being the case, we utilize sync repos.
Creating a user segment as a non-admin
For the creation of a user segment, please create a Feature Request issue (as it will require manual intervention by the Customer Support Operations team).
Editing a user segment as a non-admin
For the modification of a user segment, please create a Feature Request issue (as it will require manual intervention by the Customer Support Operations team).
Deleting a user segment as a non-admin
For the deletion of a user segment, please create a Feature Request issue (as it will require manual intervention by the Customer Support Operations team).
Current user segments
Zendesk Global
| User segment | Tag filters | Organization filters | Group filters | Individual users | System built-in |
|---|---|---|---|---|---|
| Signed-in users | N/A | N/A | N/A | N/A | Y |
| Agents and admins | N/A | N/A | N/A | N/A | Y |
| Support Editors | article_editor |
None | Support AMER Support APAC Support EMEA |
None | N |
| Support Publishers | article_publisher |
None | Support AMER Support APAC Support EMEA |
None | N |
Zendesk US Government
| User segment | Tag filters | Organization filters | Group filters | Individual users | System built-in |
|---|---|---|---|---|---|
| Signed-in users | N/A | N/A | N/A | N/A | Y |
| Agents and admins | N/A | N/A | N/A | N/A | Y |
| Support Editors | article_editor |
None | None | None | N |
| Support Publishers | article_publisher |
None | None | None | N |
Administrator tasks
Note
- All sections in this section require
Administratorlevel access to Zendesk.
Viewing user segments
To see the current user segments in Zendesk:
- Access the knowledge center
- Click the
User permissions contenticon on the left side:
Creating a user segment
Warning
- This should only be done if there is a corresponding request issue (Feature Request, Administrative, Bug, etc.). If one does not exist, you should first create one (and let it go through the standard process before working it).
For the creation of a user segment, you will need to create a MR in the sync repo. The exact changes being made will depend on the request itself.
Note: It will be very rare to use the attributes added_user_ids, or_tags, and organization_ids, so it is likely you will use the value of [] for them when you create a user segment.
A starting template you can use would be:
---
name: 'Your user segment name here'
previous_name: 'Your user segment name here'
added_user_ids: # Individual user emails to include
- user_email@example.com
- user_email@example.com
group_ids: # Zendesk group names to include
- Group Name 1
- Group Name 2
or_tags: # Tags where ANY match includes the user (OR logic)
- tag_for_filter_1
- tag_for_filter_2
organization_ids: # Organization Salesforce IDs to include
- salesforce_id_value_1
- salesforce_id_value_2
tags: # Tags where ALL must match (AND logic)
- tag_for_filter_1
- tag_for_filter_2
user_type: 'staff' # All custom user segments should use 'staff'
After a peer reviews and approves your MR, you can merge the MR. When the next deployment occurs, it will be synced to Zendesk.
Editing a user segment
Warning
- This should only be done if there is a corresponding request issue (Feature Request, Administrative, Bug, etc.). If one does not exist, you should first create one (and let it go through the standard process before working it).
- This can dramatically impact other teams’ abilities to manage articles. Exercise caution when proceeding.
To edit a user segment, you will need to create a MR in the sync repo. The exact changes being made will depend on the request itself.
After a peer reviews and approves your MR, you can merge the MR. When the next deployment occurs, it will be synced to Zendesk.
Changing the name of a user segment
If you need to change the title of a user segment, copy the current value into the previous_name attribute and then change the name attribute. This allows the sync to still locate the user segment in question to update.
Deleting a user segment
Warning
- This should only be done if there is a corresponding request issue (Feature Request, Administrative, Bug, etc.). If one does not exist, you should first create one (and let it go through the standard process before working it).
- This can dramatically impact other teams’ abilities to manage articles. Exercise caution when proceeding.
As the sync repos do not perform deletions, you will have to do 2 actions to delete a group.
First, you must delete the corresponding file from the sync repo. After a peer reviews and approves your MR, you can merge the MR.
After that is done, you then must delete it from Zendesk itself.
To delete a user segment from Zendesk:
- Navigate to the User segments page
- Click the three vertical dots to the right of the name of the user segment you wish to delete
- Click
Delete - Click
Deleteto confirm the changes
Performing an exception deployment
To perform an exception deployment for user segments, navigate to the user segments sync project in question, go to the scheduled pipelines page, and click the play button for the sync item. This will trigger a sync job for the user segments.
Common issues and troubleshooting
Not seeing user segment changes after a merge
As user segments follow the Standard deployment type, they would only be deployed during a normal deployment cycle (or when an exception deployment has been done)
User not matching expected segment
This would normally indicate you do not meet the criteria defined in the user segment in question. Please speak with the Customer Support Operations team for assistance in this matter.
f895738e)
