Création de segments d’utilisateurs pour les permissions utilisateur Guide



image avatar

Jennifer Rowe

Zendesk Documentation Team

Modification le 01 mai 2025


6

3

52 commentaire

Hi Chris,
 
To ensure we can address your concern, I've gone ahead and opened a support ticket for you. We may continue our conversation in the ticket and collaborate on resolving the issue. Please keep an eye on your email inbox for further communications and updates from me. Thank you!
 
 

0


I tried this on another user, and the user segment was removed after 5 - 10 min. Unfortunately for this first example, the user segment is still on the user's account.

0


1263082103229 See prior post. Can you help? Recap below.

  • The user segment requires 1 of 2 tags
  • On the user record in Support, the tags have been removed (both had been on the user record)
  • The user is no longer listed as a member of the segment
  • Yet the user record still lists the user segment despite the tags being removed
    (see screenshot above)
  • Using the user_segment API, it returns the 2 tags as part of the record (though deleted and not displayed on the user record) and therefore the user segment as part of the user record [GET /api/v2/help_center/users/{user_id}/user_segments]

How come the user segment isn't removed from the user record? What step have I missed?

 

 

0


I have 2 User segments defined for Signed-in users, each are based on having ANY of 2 different tags.

I added the appropriate Tags to my User record in Zendesk, and in a short time, the 2 User segments showed on my User record, as expected.

I've since removed those tags, and it has been over 24 hrs, yet the User segments aren't removed from my User record. I checked the Matching users within each of the 2 segments, and I'm no longer listed. I queried the User Segment API for my ID, and I also am returned with those 2 User segments.

How do I get the User segments to drop from my User record?

0


Hi Colleen,
 
Thank you for sharing your feedback about our help center articles! I will make sure to pass this along to our internal team for review.

0


Is it possible to restrict access to articles by a user's domain as shown in their email address? That is, I'd like everyone whose login address has the @acme qualifier. So next time someone with an email address such as joe@acme.com creates a login, this person is automatically granted access to the restricted content.

0


Reviewing your help desk articles on a Macbook Pro (Sonoma 14.4.1) and the various styles appear in Chrome very differently than they do in Safari. I generally use Chrome and the font sizes/styles are inconsistent in size and appearance as compared to Safari - see attached example.  Chrome is just plain odd while Safari is what I expected to see. Just wanted to make a note of it for the tech writing team or whomever controls the CSS/styles for your site.

0


5637229719578 An approach you could explore would be using javascript to hide articles rather than permissioning the content with the proper user segment memberships.

You could add a custom Organization field (checkbox) called something like "hide content". When the checkbox is checked it would set a tag like hide_content on the Organization. Or set a user tag but it would probably be easier to do this at the Org level if possible.

Then you'd add a function to the script.js file of your help center. The function would check the HelpCenter object looking for the specified Org tag (or user tag) hide_content. If it finds that tag in the current user's HelpCenter object you can then hide the URL of the articles based on a partial string match of the article URL using jQuery hide method.

Here's an article that goes into some of this in more detail: https://www.screensteps.com/articles/customizing-your-help-center-with-javascript

It's a bit more of a workaround than a proper solution but it works and once it's setup it's really not very hard to maintain.

Edit - I just realized that article is quite old but I've successfully used this approach in Zendesks for the past 10 years in various forms. I don't think this configuration is "officially supported" by Zendesk but sometimes it has been the only way to accomplish certain things.

 

0


I am in the same situation as Kreg Sherbine. I have an article that should be visible to any logged-in person who is not in one of the specific TAGs. Ideally, there should be the possibility to define segments with logic for exclusion and inclusion of TAGs, organizations, and users

0


4462655406234 - thankyou . Using tags we were able to overcome the limitation of 50 orgs per user segment. 

0


Vous connecter pour laisser un commentaire.