# Role-Based Onboarding Paths

Use this page to onboard new users by responsibility. Each path focuses on the highest-value actions first.

## How to use this page

* Pick the path that matches the user's current role.
* Complete Day 1 tasks first.
* Complete Week 1 tasks to finish baseline onboarding.
* Link directly to task guides during live onboarding.

## 1) Member Path

Members primarily book space and manage their own preferences.

### Day 1

* Sign in and join your organization.
* Open `/app` and review Home widgets.
* Complete one booking in Locus.
* Enable push notifications.

### Week 1

* Set profile, security, and appearance preferences in user settings.
* Save favorite resources for faster booking.
* Replay tutorials if any page feels unclear.

### Recommended docs

* [Quick start](/axon/getting-started/quick-start.md)
* [Book a space in Locus](/axon/task-guides/book-a-space-in-locus.md)
* [Enable notifications and test push](/axon/task-guides/enable-notifications-and-test-push.md)
* [Report an issue and track support](/axon/task-guides/report-an-issue-and-track-support.md)

## 2) Team Lead Path

Team leads coordinate people, schedules, and team-level planning.

### Day 1

* Confirm team membership and leadership assignment.
* Review team composition in Dashboard.
* Create or review one recurring schedule in Orbis.

### Week 1

* Validate weekly attendance plan and booking coverage.
* Review override behavior and conflict handling in Orbis.
* Keep team membership current.
* Process pending Civitas requests if your role includes Civitas access.

### Recommended docs

* [People and teams](/axon/dashboard/people-and-teams.md)
* [Create a recurring schedule in Orbis](/axon/task-guides/create-a-recurring-schedule-in-orbis.md)
* [Create a team and assign members](/axon/task-guides/create-a-team-and-assign-members.md)
* [Report an issue and track support](/axon/task-guides/report-an-issue-and-track-support.md)

## 3) Organization Admin Path

Organization admins manage access, policy, module readiness, and billing.

### Day 1

* Verify role model and default invite role.
* Invite one user and validate access.
* Review organization security policy (MFA mode).
* Confirm billing visibility and plan status.

### Week 1

* Validate Atlas HQ/floor setup and publish readiness.
* Validate Locus/Orbis/Civitas organization settings.
* Review audit log filters and export behavior.
* Confirm support/onboarding docs are shared with leads.

### Recommended docs

* [Organization settings](/axon/dashboard/organization-settings.md)
* [Billing](/axon/dashboard/billing.md)
* [Invite and onboard a user](/axon/task-guides/invite-and-onboard-a-user.md)
* [Publish a floorplan in Atlas](/axon/task-guides/publish-a-floorplan-in-atlas.md)
* [Process Civitas tickets](/axon/task-guides/process-civitas-tickets.md)
* [Support](/axon/dashboard/support.md)

## Operational tip

When responsibilities overlap, start with the stricter path (usually Org Admin), then assign the user a smaller steady-state path once setup is complete.


---

# 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/role-based-onboarding.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.