Recherches récentes
Pas de recherche récente

Brad Bazley
Adhésion le 22 oct. 2021
·
Dernière activité le 01 avr. 2022
Suivis
0
Abonnés
0
Activité totale
5
vote
1
Abonnements
2
APERÇU DES ACTIVITÉS
BADGES
ARTICLES
PUBLICATIONS
COMMENTAIRES DE LA COMMUNAUTÉ
COMMENTAIRES SUR L’ARTICLE
APERÇU DES ACTIVITÉS
Dernière activité effectuée par Brad Bazley
Brad Bazley a ajouté un commentaire,
Thanks for the clarification, Sam!
We're trying to limit visibility for signed-in users, so I understand your point re: groups only being relevant for Agents/Staff.
For Signed-in users, we'd ideally like to segment based on values contained in the User Fields. It doesn't look like these fields can create tags, so what would be the best option here?
If our only choice is to segment based on Organisation, is there any other automated means of associating a user to an Org (i.e. Org = Department, with users provisioned by SCIM to the relevant Org based on their "Department" attribute value from the source identity provider?
Afficher le commentaire · Publication le 01 avr. 2022 · Brad Bazley
0
Abonnés
0
Votes
0
Commentaire
Brad Bazley a ajouté un commentaire,
Is it possible to segment based on:
- Users' standard/custom fields?
- Users' group membership?
We're provisioning our end users to Zendesk via SCIM, so ideally we'd like to limit HC article visibility to a specific department or team, which can be determined either by the values in their standard/custom fields for Department, or an externally populated group provisioned to Zendesk.
We're unable to use organisation to distinguish between teams, as Org membership is determined by email domain, and all users share a common domain suffix.
Afficher le commentaire · Publication le 01 avr. 2022 · Brad Bazley
0
Abonnés
1
vote
0
Commentaire