Skip to main content

​
Access modes

Airia Agent supports two access modes. You set this in Settings → Airia Agent → Access & Privacy.

​
All users

Every member of your tenant can use Airia Agent. This is the default mode when you first enable the feature. Choose this when:
  • You want immediate, broad rollout without managing individual permissions
  • Your tenant is small and every user should have the same experience

​
Specific users and groups

Only users or groups you explicitly grant access to can use Airia Agent. Everyone else is routed to the fallback agent you configure (see below). Choose this when:
  • You are rolling out gradually — for example, to a pilot group first
  • Different user populations should have different default experiences
  • You want to reserve Airia Agent for users who need its extended capabilities
Access mode changes take effect immediately. Users who lose access can still view their existing conversation history but cannot send new messages through Airia Agent. Their next new conversation opens with the fallback agent instead.

​
Grant access to specific users or groups

1

Set mode to restricted

In the Access & Privacy tab, select Specific users and groups.
2

Add users or groups

Use the search field to find users or groups by name, then add them. You can add as many as needed.
3

Save

Click Save. The selected users and groups now have access to Airia Agent.

​
Fallback agent

When access is restricted, users without the Airia Agent permission need somewhere to go. The fallback agent is the catalog deployment they see in Chat instead.
1

Open the fallback agent picker

In the Access & Privacy tab, find the Fallback Agent section.
2

Select a catalog deployment

Choose any published catalog deployment from the dropdown. Only deployments marked as available in the Airia Catalog appear here.
3

Save

Click Save. Users without Airia Agent access now see the selected fallback agent in their Chat sidebar.
If no fallback agent is configured and access is restricted, users without access will see an empty Chat sidebar. Always set a fallback agent before restricting access.

​
Privacy settings

If your tenant has the end-user privacy feature enabled, a Privacy section appears on this tab with a single End-User Privacy toggle. When this toggle is on, the content of every Airia Agent conversation — prompts, responses, and execution step details — is hidden from administrators. Only the user who had the conversation can see its full content. Admins viewing conversation history or execution logs see redacted placeholders rather than the actual messages. Users whose conversations are private see a shield badge in the Chat interface confirming their messages are not visible to admins.
End-User Privacy is a strong, platform-enforced control. Once enabled, there is no admin override to view the hidden content — not through conversation history, the execution feed, or the API. The setting change is audited at high severity each time it is toggled.
If the Privacy section is not visible and you need it for compliance or data governance requirements, contact your Airia account team to have the feature enabled for your tenant.