> For the complete documentation index, see [llms.txt](https://sonic-ai-works.gitbook.io/sonic-networks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/application-and-website/dashboard-and-role-based-applications.md).

# Dashboard & role-based applications

Canonical SONIC v1.0.0 role-based dashboard architecture for Creator, Developer, Finance, Admin, Owner, Moderator, Member and Viewer experiences with server-authoritative access decisions.

The SONIC dashboard is one application shell with role-, permission-, entitlement- and policy-aware modules. Browser visibility is not authorization.

## Canonical roles

```
OWNER · ADMIN · CREATOR · DEVELOPER · FINANCE · MODERATOR · MEMBER · VIEWER
```

## Bootstrap

```
Clerk session
→ SONIC Auth Context
→ workspace membership
→ Access Context
→ role grants + explicit grants/denies
→ entitlements
→ AAL / session freshness / risk
→ allowed modules
```

## Developer dashboard

When access permits, Developer receives:

* API keys
* signed webhooks
* usage and logs
* OpenAPI / Swagger / Postman
* provider connection visibility
* test/live environment separation

`DEVELOPER` does not imply Billing Manage, Treasury Manage, Owner/Admin grants or wallet-signing authority.

## UI states

```
LOADING
ALLOWED
DENIED
ENTITLEMENT_REQUIRED
REVERIFICATION_REQUIRED
REQUIRES_REVIEW
UNAVAILABLE
```

Do not render a fake empty dashboard when the real state is missing permission or entitlement.

## Sensitive actions

Role changes and live API-key changes require fresh AAL2. Payout wallet changes and destructive account/organization actions can require AAL3/contextual authorization.

The last active Owner cannot be demoted. Cross-workspace role mutations fail closed and successful mutations create audit evidence.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/application-and-website/dashboard-and-role-based-applications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.