Búsquedas recientes
No hay búsquedas recientes

Brad Bazley
Incorporación 22 oct 2021
·
Última actividad 01 abr 2022
Seguimientos
0
Seguidores
0
Actividad total
5
Voto
1
Suscripciones
2
RESUMEN DE LA ACTIVIDAD
INSIGNIAS
ARTÍCULOS
PUBLICACIONES
COMENTARIOS DE LA COMUNIDAD
COMENTARIOS DE ARTÍCULOS
RESUMEN DE LA ACTIVIDAD
Última actividad de Brad Bazley
Brad Bazley hizo un comentario,
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?
Ver comentario · Publicado 01 abr 2022 · Brad Bazley
0
Seguidores
0
Votos
0
Comentarios
Brad Bazley hizo un comentario,
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.
Ver comentario · Publicado 01 abr 2022 · Brad Bazley
0
Seguidores
1
Voto
0
Comentarios