Users, Roles & Groups
Manage user accounts, define routing roles with mapping rules including caller and credential types, and organize access through groups
User Management is your central hub for access management. Users represent real people in your organization, routing roles define usage patterns with automatic mapping rules, and groups tie users and routing roles together with access to specific knowledge packs and guardrails. Find it under Admin → Users.

The Users tab displays all user accounts with their status, department, and group memberships.
User Management lives in Admin, so it opens to the holders of View users & groups or Manage users & groups, Platform Admins among them — see Access. The older /users link still works and redirects here.
What this page does not control
Everything on this page — groups, routing roles, mapping rules — decides which knowledge and guardrails apply to an interaction. It does not decide who may administer AskRAI. That is a separate, tenant-level question answered on the Access page, which grants the Platform Admin and Member roles. Adding someone to an "Admin Access" group here does not let them into Admin.
Users tab
The Users tab shows all user accounts provisioned through Directory Sync — whether your identity provider pushes them over SCIM 2.0 or AskRAI pulls them from Google Workspace. Each user card displays the person's name, job title, department, email address, status, and group memberships.
If your directory deletes an account and later creates a new one with the same email address, the Users tab lists that person once, as the new account. So does every place you pick a user: adding group members, granting an Access role, or adding someone to a project team. The old account still appears on the Directory tab, tagged Deprovisioned. Nothing moves to the new account. The old account keeps its groups, its Access role, its organization and project grants and its project teams, and none of them gives anyone access. A block on the old account does not carry over either. Give the new account the groups and roles it should have, share with it the organizations and projects it should see, and block it if it should be blocked.
User status
Users have one of two statuses:
| Status | Description |
|---|---|
| Active | The user can access the system normally |
| Blocked | AskRAI refuses every question the user asks, and everything they do in the admin console |
To block a user, open their details drawer, choose Block user beside their account status, and confirm. Their questions are refused at once, and their use of the admin console within 30 seconds. A blocked user's drawer offers Unblock user instead, which gives them back the access their groups grant, on the same timing. You cannot block your own account.
Blocking or unblocking someone takes away or gives back every role they hold, so it needs every permission their roles grant, and only a Platform Admin blocks or unblocks a Platform Admin. The tenant's last Platform Admin assigned directly to a user who can sign in cannot be blocked: one already blocked, or deprovisioned by your directory, does not count. When one of these rules stops you, AskRAI says why.
A user your directory has deprovisioned shows no status, only the Deprovisioned tag: AskRAI refuses their queries. If you blocked them, they still show Blocked beside the tag.
User details drawer
Click any user row to open the details drawer. Its header shows the user's ID, which you can copy, and it has these tabs:
- Details — name, job title, department, account status with Block user or Unblock user, and email address
- Groups — lists all groups the user belongs to, with member counts and knowledge pack access
- Access — every role the user holds, assigned to them directly or through a group, and each permission those roles grant, by section, with the roles it comes from: "From Project leads; Tool keepers, via Finance analysts". A group a role comes through opens on the Groups tab. Below them, the user's grants: each organization and then each project shared with them, with its level, and whether it was shared with them, with a group they are in, which it names, or with everyone in the tenant. It lists only the organizations and projects you can see yourself, so it may hold fewer grants than the user has. Only someone who can view roles and assignments sees this tab

The Access tab says where each of a person's permissions comes from.
Filtering Users
Use the search bar and the Status dropdown to narrow the list:
| Filter | Options | Description |
|---|---|---|
| Search | Free text | Matches user names, display names, email addresses, and departments |
| Status | All, Active, Blocked | Filter by account status. Active leaves out deprovisioned users |
The list cannot be filtered by group. A user's groups are shown on each user row and in the details drawer, and a group's members are listed when you open the group on the Groups tab.
Groups tab
Groups are permission containers that connect users and routing roles to knowledge packs and guardrails. A user's access to knowledge base content is determined by their group memberships.

Each group card shows its users, its routing roles, its roles, its knowledge packs and its guardrails.
A group card's Routing roles are the routing roles in the group, described under Routing roles tab. Its Roles are the roles the group is assigned on the Access page, which its members hold while the group is active. Only someone who can view roles and assignments sees them. Anyone else is told which permission reading them needs.
The Filters button narrows the list to the groups holding every routing role, knowledge pack and guardrail you pick.
Creating a group
Open the Create Dialog
Switch to the Groups tab and click Add Group in the top-right corner.

A native group created here can carry guardrails and knowledge packs exactly like a synced one — the difference is only where its membership comes from.
Enter Group Details
Type a group name (required) and an optional description. Click Create to save.
Configure the Group
After creation, the group details modal opens automatically. Use its six tabs to configure the group:
- Members — add users and routing roles to the group. Toggle between Users, Routing roles, or Both views, search, and click the + icon to add them. A programmable-access credential created in this group is listed as a member with a key icon. It cannot be removed here, because its membership is what applies the group's knowledge packs and guardrails to it. It leaves the group when it is revoked or deleted on the Programmable Access page. A group's members hold the tenant roles assigned to it, so adding or removing one needs every permission those roles grant, and only a Platform Admin changes who is in a group holding Platform Admin. Its members also hold the group's organization and project grants, so changing them needs Admin on every organization and project the group is shared with.
- Knowledge Packs — select which knowledge packs this group can access. Search and add packs from the available list.
- Guardrails — assign the guardrails that apply to this group's members. An active Input or Output guardrail applies to every member's query. A Tool call guardrail checks an agent's tool calls, and a member's query makes none, so it does not apply here. Naming a group's guardrails and policies takes View policies, guardrails and egress, and changing them Manage policies, guardrails and egress.
- Policies — attach governance policies to the group. On every member's query, a policy applies its status and its Input and Output guardrails, and its egress allowlist only as the list a Link domain guardrail checks links against. Its ceilings, its approval requirements and its Tool call guardrails govern an agent's beats, so they do not apply to the group's members. See A policy on a group.
- Credentials — a read-only list of the programmable-access credentials mapped to this group, each with its type and an Active, Interface off, Expired or Revoked status. Credentials themselves are issued and managed on the Programmable Access page.
- Directory — link this group to a directory group so its membership is provisioned from your identity provider. Search the directory groups by name: the list shows the first 50 that match, and says so when there are more. While linked, the tab names the directory group this group follows, members are synced from the directory and managed there, and unlinking returns the group to manual membership. If the tab says the link did not finish, the group names the directory group but has none of its members yet: click Link again to finish it. When the directory group is deleted in your identity provider or Google Workspace, AskRAI unlinks this group for you as soon as it learns of it, which for Google Workspace is the next sync. Everyone the directory group gave it leaves, including anyone you had also added by hand, the other members you added stay, and you manage the group here from then on. No notification is sent, and a directory group created again under the same name is a new one to link to. If the tab instead says the directory no longer holds the group this one follows, as it can for a directory group deleted before AskRAI unlinked groups on its own, nothing syncs its members until you unlink it. This requires directory groups provisioned through Directory Sync. Linking hands the group's membership to the directory, so it needs every permission the group's tenant roles grant, and Admin on every organization and project the group is shared with.
Deleting a group
Open the group and click Delete, then confirm. You cannot delete a group while it governs an active programmable-access credential. The refusal names those credentials. Revoke or delete each one on the Programmable Access page, then delete the group. Without this rule, the credentials would go on working with none of the group's knowledge packs or guardrails.
Group types
| Type | Description |
|---|---|
| Manual | Members are added and removed by administrators |
| Automatic | Members are assigned automatically from user attributes. Not yet functional — the console creates only Manual groups, and automatic assignment is not evaluated at query time |
Group fields
| Field | Description | Required |
|---|---|---|
| Name | Display name for the group | Yes |
| Description | Explains the group's purpose | No |
| Type | Every group created here is Manual. The API accepts Automatic, but the console offers no control for it | Set for you |
| Members | Users and routing roles in this group | No |
| Knowledge Packs | Content collections this group can access | No |
| Guardrails | Safety policies applied to this group | No |
Routing roles tab
Routing roles represent usage patterns rather than individual people. They are not the roles that open areas of Admin. Each role defines mapping rules that automatically classify incoming interactions — for example, so that requests arriving on a specific channel get the knowledge packs and guardrails meant for them.

Each role card displays its mapping rules, its access category, the date it was last updated, and its enabled/disabled status.
The Access filter narrows the list to the roles of one category.
Role properties
| Field | Description | Required |
|---|---|---|
| Name | Display name for the role | Yes |
| Description | Explains what the role represents | No |
| Category | Access classification: Public Access, Employee Access, Admin Access, API Access, or System Access | Yes |
| Status | Enabled or Disabled | Yes |
| Mapping Rules | Conditions that trigger this role | No |
Mapping rules
Mapping rules define when a role applies based on interaction properties:
| Rule Type | Description | Values |
|---|---|---|
| Channel | Communication channel | Teams, Web Chat, Mobile App, WhatsApp, SMS, Phone, Email, API, CLI, MCP |
| Authentication | Authentication method | Authenticated, Unauthenticated, API Key, Executive SSO, Service Credential |
| Caller Type | Who initiated the request | Human, Application, Agent |
| Credential Type | How the caller authenticated | Personal Token, Service Account, Agent Credential, Scoped API Key |
All of a role's rules must match for the role to apply, and a user receives the combined access of every role that matches — there is no ordering between roles and no first-wins. A role with no rules matches no request.
Values a rule can hold
The values above are each kind's complete list, and a rule is saved only with values from its kind's list: any other value is refused, and the refusal lists the values its kind accepts. A rule with no value, or an IN rule with nothing selected, is refused too.
A role saved before AskRAI checked these values can still hold one that no option names. The role opens as it was saved, and its editor shows such a value in an IN rule as Unrecognised, with a button to remove it. The role is refused on save while it holds one, so remove the value, then select Save changes.
A rule stored with the NOT IN operator, which the editor does not offer for a new rule, opens with its operator named.
Rules of a kind that is not offered
A role can hold rules of a kind the editor does not offer, such as Device or Referrer. No caller reports a device or a referrer, so a rule of either kind can never be satisfied, and because every rule must match, a role holding one matches no request. Its groups grant none of their knowledge packs and apply none of their guardrails through it.
The console shows you such a role:
- Its card is marked Withdrawn rules: matches no request.
- Its editor lists them read-only under Withdrawn rules, apart from its other rules, and says that the role matches no request while it holds them.
- Saving keeps them. Change the role's details or its other rules and select Save changes, and the role still holds them.
- Removing them is a choice you make in the editor. Select Remove these rules when saving, then Save changes, and the role matches on its remaining rules.
Removing these rules can widen who the role reaches. A role holding a Channel rule beside a Device rule matches nothing; once the Device rule is gone, it matches every request on that channel, and the knowledge packs and guardrails of every group it belongs to start applying to those callers. Review the remaining rules, and the groups the role is in, before you remove them. If you no longer want the role at all, delete it instead.
Caller Type and Credential Type rules are designed for programmable traffic. Pair them with the Programmable Access page to declaratively route machine callers — for example, map every Agent credential to a read-only role, or give Service Accounts a higher-privilege role that Personal Tokens do not receive.
Routing roles are added to groups, not to users. To give a routing role access to knowledge packs or guardrails, add it to a group with the appropriate configuration.
Creating a role
Switch to the Routing roles tab and click Add Role. Enter a name, optionally add a description, and choose its Category and status. The category starts at Employee Access. After creation, open the role to configure mapping rules.
To change a role's category, open the role, choose another Category, and select Save changes. A routing rule on Role Category applies to every request that matches a role of that category, so moving a role to another category changes which of those rules apply to its requests.
You cannot delete a role that is assigned to any group. Remove the role from all groups first, then delete it.
Directory tab
The Directory tab is a read-only view of the identities provisioned through Directory Sync, shown separately from the native groups and routing roles you manage in AskRAI. Use it to confirm that a sync took effect and that the right people and groups arrived.

The Directory tab lists the synced users and groups, each tagged Synced from directory.
The tab is split into two sections:
- Directory Users — the synced people, with their name, email, and a Synced from directory badge. A user suspended or removed in the source directory is tagged Deprovisioned.
- Directory Groups — the synced groups, with their member count and source badge.
Each heading counts every user or group the search matches. Each list shows the first 50 of them, and says so when there are more.
Use the Search directory box to find users by name, email or department, and groups by name. If no source is enabled yet, the tab prompts you to configure Directory Sync; if a source is enabled but the first sync hasn't completed, it shows an "awaiting first sync" state.
The Directory tab reflects exactly what your identity provider sent. To change who appears here, manage users in your IdP or Google Workspace — not in AskRAI. Native Groups and Routing roles (the other tabs) remain yours to configure and can be linked to synced identities.
How access control works
The access control model follows this hierarchy:
- Users are real people synced from your identity provider
- Routing roles classify interactions automatically via mapping rules
- Groups bundle users and routing roles together
- Groups grant access to knowledge packs and guardrails
A user's effective access is the union of all knowledge packs and guardrails from every group they belong to. A group either grants a knowledge pack or it does not: a pack granted by any one of a user's groups is theirs to search, and nothing on another group takes it away. Nor does an item's Sensitivity, which is a classification label: a Secret item in a granted pack is found for the same callers as a Public one.
Administrative access runs on a separate track: a user's tenant roles — Platform Admin, Auditor, Member or one you build — are granted on the Access page and decide which areas of Admin they can open, with Organizations also open to an organization's Admins. The two are independent, so a Member can still hold rich content access through their groups, and a Platform Admin has no extra knowledge access just for being an admin.
Related pages
- Access — grant the Platform Admin, Auditor and Member tenant roles to the users and groups managed here
- Directory Sync — provision the users and groups shown on the Directory tab from SCIM 2.0 or Google Workspace
- Knowledge Packs — content collections that groups can access
- Guardrails — safety policies assigned to groups
- Programmable Access — issue credentials whose Caller Type and Credential Type are matched by the role rules described above
- Sandbox — test how a credential resolves to a role and group before pointing live traffic at it
- Admin — configure system-wide settings and escalation rules