Skip to main content
Exalt Reserve

Access control

People sign in through your own identity provider and reach Exalt Reserve only from your private network. Your admin decides what each person can see.

How access works, and who sets it.

  • Sign-in

    People sign in with your own identity provider, such as Microsoft, Okta or Google. Your team decides who has an account there.

  • Where people connect from

    Users reach Exalt Reserve only from your private network. There is no public endpoint.

  • Access policy

    Network, identity and access policy stay under your control, in your own cloud account.

  • Credentials

    Credentials stay in your environment, with your data, models and vector stores.

  • Roles

    Each person has a role. Your admin manages accounts and roles.

  • Uploaded documents

    Who may read an uploaded document is set by the person who approves it in Exalt Ledger.

  • Connected sources

    Connected sources keep the permissions set in the source system.

  • Team scoping and custom rules

    Your admin can narrow a connected source by team, or with custom rules per source or folder.

  • Record

    Questions, answers, the sources shown and admin actions are recorded with who and when, in your own cloud account.

Where the line is.

  • Access to Exalt Reserve follows your identity decisions. It does not replace your identity policy.

Put local AI to work where it matters most.

Bring your own review questions to the consultation. We answer them against this page.