Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

Brad Bazley
Beigetreten 22. Okt. 2021
·
Letzte Aktivität 01. Apr. 2022
Folge ich
0
Follower
0
Gesamtaktivitäten
5
Stimme
1
Abonnements
2
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von Brad Bazley
Brad Bazley hat einen Kommentar hinterlassen
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?
Kommentar anzeigen · Gepostet 01. Apr. 2022 · Brad Bazley
0
Follower
0
Stimmen
0
Kommentare
Brad Bazley hat einen Kommentar hinterlassen
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.
Kommentar anzeigen · Gepostet 01. Apr. 2022 · Brad Bazley
0
Follower
1
Stimme
0
Kommentare