Possibility to manage rights per (human) agent
B
Burgundy Partridge
Not only have support and admin agent, but distinguish per agent what he/she can do/see.
For example:
- we'd like to add 'only read' option for agents to only be able to see the conversations in the Inbox and settings of the Agent, but not to change anything.
- have specific agents only see conversations/settings of a specific Agent in stead of all agents.
Fleur Nouwens
Merged in a post:
User rights to block access to payment methods
R
Rainy Stingray
It would be nice to be able to block rights to watermelon users to see payments.
Next to support agents there might also be people that can have rights to edit AI Agent data or prompts, but not see payments and change plans.
Fleur Nouwens
Merged in a post:
Authorization options
B
Burgundy Partridge
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
Fleur Nouwens
Merged in a post:
Control Conversation Access per AI Agent (User and Role Level)
S
Sunny Bird
You want to define which AI Agent(s) a support user can access within the Conversations dashboard. For example: a support user should be able to review and take over conversations from the commercial AI Agent, but not from the internal HR Agent.
Access should be configurable both per user and per role (e.g. support, admin). This ensures sensitive conversations stay protected and only the right people have visibility.
This feature enables scalable and secure access control, especially in setups with multiple teams or departments.
Fleur Nouwens
Hey Burgundy Partridge, thanks for your feedback! Following up on this:
- What specific roles or permissions would you like to define for different agents?
- Are there any specific scenarios or use cases where these differentiated permissions would be particularly beneficial?
- How critical is this feature to your current operations and what impact would it have on your workflow?
Fleur Nouwens
Great to hear your perspective, Burgundy Partridge! 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
B
Burgundy Partridge
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
Milou Wolsing
Merged in a post:
More user roles
I
Incarnadine Deer
I want to create users that have more rights than an agent, for instance the rights to change chatbot personality and/or create chatbots without making them admin. And a separate role for finance so that not everyone can see and change the financial part of the chatbot tenant.