Access Control
Users, roles, groups, and multi-tenant isolation control who can access which knowledge and guardrails
AskRAI's access control model determines who can access which knowledge and what safety rules apply to their interactions. The model is built on four layers — users, roles, groups, and tenants — that combine to provide fine-grained, scalable access management without per-user configuration.
Two kinds of access
AskRAI separates administering the tenant from using its content, and the word "role" means something different on each side. Keep them apart:
| Tenant role | Resource-access role | |
|---|---|---|
| Question it answers | Who may change how AskRAI is configured? | Which knowledge and guardrails apply to this interaction? |
| Values | Platform Admin, Auditor, Member, and roles you build from permissions | Roles you define, e.g. Employee, Public Kiosk |
| Granted to | A directory user or group, on the Access page | Groups, via mapping rules |
| Effect | Unlocks areas of Admin, or reaches every organization and project | Grants knowledge packs and guardrails |
A Platform Admin can open Admin and reconfigure the tenant. A Member cannot, apart from Admin → Organizations once they are Admin on an organization: they see only the organizations and projects shared with them, work in each at the level it is shared at, and use every console page but Guardrails, which, like Admin, is reserved for the people whose roles grant it. A role you build grants the areas of Admin you choose, and a person holding several roles holds all they grant. An Auditor has what a Member has, and can also open Admin to read its Change Log, the record of who changed what there; no other Admin page, and no change, is open to them. Inside a project, Read opens it and changes nothing; Write sends its messages, writes its brief, works its tasks, starts and stops its team, decides its agents' proposals, and changes its team, its agents and its files; Admin also shares it, changes an agent's autonomy, edits, resets and deletes the project, and deletes its agents. These are levels a project's Admins grant from its Share dialog (see Sharing & Access), and someone holding none does not see the project at all. An organization is shared the same way: Write on it creates projects in it, and Admin on it is Admin on every project in it, while Read or Write on it reaches none of them. A tenant starts closed: someone with no grant and no role reaching every organization or project sees no organization and no project until one is shared with them. Three tenant permissions reach past the grants: Administer every organization and Administer every project give Admin on every project, and View every organization and project gives Read on every one; a Platform Admin holds all three. Tenant roles and access levels alike are separate questions from what content anyone can see — that is decided by groups and resource-access roles, described below, and applies to admins and members alike.
The access hierarchy
| Layer | What it represents | How it's managed |
|---|---|---|
| Users | Real people synced from your identity provider over SCIM 2.0, or pulled from Google Workspace | Automatic sync — admins can block/unblock |
| Roles | Usage patterns that classify interactions by how the request arrived — its channel, authentication, and caller or credential type | Defined by admins with automatic mapping rules |
| Groups | Permission containers that bundle users and roles together | Created by admins, members added manually or automatically |
| Knowledge Packs | Content collections a group can search | Assigned to groups |
| Guardrails | Safety rules applied to a group's interactions | Assigned to groups |
Users
Users are real people in your organization. They are synced automatically from your identity provider — you do not create user accounts manually in AskRAI. Every synced user is a Member until an admin grants them a tenant role on the Access page — with one exception: the very first user to sign in to a brand-new tenant is automatically promoted to Platform Admin, so there is always someone who can open Admin and grant roles to everyone else. Administrators can:
- View user details (name, department, job title, email address)
- Block or unblock user accounts
Users gain access to knowledge and guardrails through their group memberships, never directly.
Roles
The roles in this section are resource-access roles — the ones that decide which knowledge and guardrails an interaction gets. They are unrelated to the tenant roles (Platform Admin, Auditor, Member and the ones you build on the Access page) that unlock Admin.
Roles represent usage patterns rather than individual people. Each role defines mapping rules — conditions that automatically classify incoming interactions based on properties like:
| Rule type | Example |
|---|---|
| Channel | Teams, Web Chat, API |
| Authentication | Authenticated vs. Unauthenticated |
| Caller type | Human, Application, Agent |
| Credential type | Which class of credential made the call |
Those four are the whole list. A role can still hold a rule of another kind — Device, Referrer, Location or Time — and none of them can be evaluated against a request: no caller reports a device or a referrer, and a location or time rule names nothing a request carries. AskRAI holds such a rule aside, and the role matches no request at all rather than matching on its other rules. The role's editor lists those rules read-only and lets you remove them, after which the role matches on its remaining rules — see Rules of a kind that is not offered.
When a user sends a message, the system evaluates mapping rules to determine which roles apply. Every rule on a role must match for that role to apply, and a user receives the combined access of every role that does — there is no ordering between roles. Roles are assigned to groups, so matching a role grants the user that group's knowledge packs and guardrails.
Roles enable dynamic access control without per-user configuration. For example, you can create a "Public Kiosk" role that matches unauthenticated web chat requests, and a separate "Employee" role that matches authenticated Teams messages — each with different knowledge packs and safety rules.
Groups
Groups are the central connection point in the access model. A group bundles together:
- Members — users and roles that belong to the group
- Knowledge packs — content collections the group can access
- Guardrails — safety rules that apply to the group's interactions
A user's effective access is the union of all knowledge packs and guardrails from every group they belong to. If a user belongs to Group A (with packs 1 and 2) and Group B (with packs 2 and 3), they can search packs 1, 2, and 3. A group either grants a pack or it does not, and a grant from any one group is enough: no group takes away a pack another grants.
Group types
| Type | How members are assigned |
|---|---|
| Manual | Administrators add and remove users and roles individually |
| Automatic | Declared on the API, but not reachable: the console creates every group as Manual, and automatic assignment is not evaluated for a person asking a question. Use roles to grant group access by rule instead. |
Multi-tenant isolation
AskRAI is a multi-tenant platform. Each tenant operates in complete isolation — data, configuration, users, knowledge, and guardrails are fully separated between tenants.
From a product perspective, this means:
- Each organization gets its own independent AskRAI environment
- Users in one tenant can never see or search content from another tenant
- Configuration changes in one tenant have no effect on others
- Administrative actions (creating groups, editing guardrails, managing users) are scoped entirely to the current tenant
Tenant isolation is enforced at every layer of the platform. No tenant administrator can see or reach another tenant's data or configuration, and no configuration option shares content between tenants — every record of your data, and every query against it, is scoped to a single tenant.
Multi-channel support
AskRAI supports multiple communication channels through the same access control model. Roles with channel-based mapping rules allow you to:
- Serve different content to different channels (e.g. a narrow public-facing set for API callers, internal policies on Teams)
- Apply stricter guardrails to public-facing channels
- Track usage and confidence metrics per channel in the Dashboard
Next steps
- Access — build tenant roles from permissions, and grant them and the built-in Platform Admin, Auditor and Member roles that decide who can reach Admin
- Users, Roles & Groups — manage users, create roles, and configure groups
- Knowledge Packs — create content collections to assign to groups
- Guardrails — author the safety rules a group or policy carries
- Governance & Audit — learn how access control ties into audit and compliance