Agent Access as a Role Permission

This update adds agent access as a role permission that can be turned on or off for each role.

Members outside the admin role can now be given agent access at the role level. The object and property scope assigned to that role stays in effect throughout the conversation.

Why It Matters

When agent access depends solely on whether a role is the admin role, granting the analytics agent to a specific member requires assigning that admin role. The admin role is treated as having every permission enabled, so the moment it is assigned, any object and property scope narrowed for that member is released along with it. A role with a restricted data scope and agent access cannot stand together.

This update closes that gap so that agent access can be granted on its own, with the data scope left untouched.

Agent Access per Role

Agent access is now an entry in the permission catalog, so each role decides entry by turning it on or off.

• Role-level grant: Turning on agent access in the role permission settings lets members of that role open the agent without holding the admin role.
• Scope preserved: Granting agent access does not widen what a member can read, so the object and property scope assigned to the role still applies during the conversation.
• Paths outside the screen: Opening a conversation URL directly or calling the agent from outside the screen goes through the same permission check.

Roles with a narrowed data scope, such as department or field roles, can now be given the analytics agent and ask questions within the data each of them is allowed to see.

You can try it now in Deskroom Settings > Roles. The time spent reworking a permission structure just to grant agent access can go into reading data and making decisions.