Pesquisas recentes
Sem pesquisas recentes

Brad Bazley
Entrou em 22 de out. de 2021
·
Última atividade em 01 de abr. de 2022
Seguindo
0
Seguidores
0
Atividade total
5
Votos
1
Assinaturas
2
VISÃO GERAL DA ATIVIDADE
MEDALHAS
ARTIGOS
PUBLICAÇÕES
COMENTÁRIOS NA COMUNIDADE
COMENTÁRIOS EM ARTIGOS
VISÃO GERAL DA ATIVIDADE
Atividade mais recente por Brad Bazley
Brad Bazley comentou,
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?
Exibir comentário · Publicado 01 de abr. de 2022 · Brad Bazley
0
Seguidores
0
Votos
0
Comentários
Brad Bazley comentou,
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.
Exibir comentário · Publicado 01 de abr. de 2022 · Brad Bazley
0
Seguidores
1
Votos
0
Comentários