# Access And Permissions

Axon visibility is role and plan aware. If something is missing from your navigation, it is usually due to permissions, module flags, or plan constraints.

## App module access (`/app`)

* `Home`: available to signed-in users.
* `Locus`: available in the app shell for organization members.
* `Orbis`: requires the `Access Orbis` permission and an enabled Orbis module.
* `Atlas`: requires the `Access Atlas` permission and an enabled Atlas module.
* `Civitas`: availability depends on module/plan conditions; organization processing flows require `Access Civitas` or `Manage Civitas`.

## Dashboard access (`/dashboard`)

* `Overview`, `Teams`, `Notifications`, `Support`, `User settings`: generally available to signed-in users.
* `Users`: permission-scoped behavior:
  * `Invite new users`: invite panel + user list
  * `Manage users`: user list + access-management profile actions
  * `Manage Civitas`: full user profile people-ops sections
* `Billing`: requires billing view/manage permissions.
* `Organization settings`: requires organization settings edit permission.

## Public support access (`/support`)

* Public support intake can be used without sign-in.
* This route is intended for account-access issues or pre-login support needs.

## Key permission labels in Axon

* Manage users
* Invite new users
* Manage teams
* Manage Orbis schedules
* Access Orbis
* Access Civitas
* Manage Civitas
* Access Atlas
* Manage billing/subscription
* View billing
* Edit organization settings

## Why access can differ between users

* Users can have multiple roles.
* Effective permissions are additive across roles.
* Organization module flags can disable a module even if a permission exists.
* Billing/plan restrictions can hide or block some capabilities.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://xdbx.gitbook.io/axon/getting-started/access-and-permissions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.