Authorization options
backlog
This post was marked as
backlog
M
Margot Maas
Hi Fleur,
- If I'm correct, these are our options:
- A support agent can view their own conversations.
- An administrator can view all conversations and manage all AI agents.
We need a rights group that can view all conversations, but not edit an AI agent.
We need a rights group that makes the management of AI agents more specific, so which AI agent can manage the employee.
- Someone who has a conversation with our chatbot and can't figure it out will contact us by phone. When this person refers to the conversation, it is nice if the KCC employee can read along. This requires administrator rights. However, that also immediately gives the entire KCC the rights to edit all AI agents. That is not desirable.
3.
The ability to read all conversations from the AI chatbot as a support agent/monitor all conversations and statistics without editing AI agents
Determining which AI agent an administrator can manage.
Fleur Nouwens
Great to hear your perspective, Margot Maas! I have a few more questions for you:
- What specific roles or permissions would you like to see added beyond 'beheerder' and 'support agent'?
- How important is it for your team to have the ability to read conversations without making changes?
- Are there any specific tasks or responsibilities that you feel are not covered by the current authorization options?
Fleur Nouwens
Merged in a post:
Authorization options
M
Margot Maas
It is now only possible to choose administrator or support agent when adding an agent. We would like more options for giving authorizations, for example:
- administrator of a specific chatbot
- ability to read conversations but not make changes to chatbots