> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nexalytica.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Nexalytica Roles and Permissions: Complete Reference

> Understand every role in Nexalytica — from Org Owner to Dept Employee — plus sharing levels, the capability matrix, and how role caps work.

Nexalytica uses a layered role system to give the right people the right level of control without exposing sensitive data or settings to those who don't need them. Roles exist at two distinct levels — **Organisation** and **Department** — and a separate set of **sharing levels** governs what recipients can do with a specific resource. Understanding how these layers interact lets you delegate confidently and collaborate safely.

## Organisation Roles

Organisation roles apply across your entire Nexalytica Organisation. Every member of your Organisation holds exactly one organisation role.

<Accordion title="Org Owner">
  The Org Owner is the person who originally created the Organisation. This role is **permanent** — it cannot be transferred, removed, or demoted. The Owner holds every capability that an Org Admin holds, plus absolute control over the Organisation itself.
</Accordion>

<Accordion title="Org Admin">
  Org Admins manage the Organisation day-to-day. Assign this role to people who need to onboard new members, restructure Departments, oversee billing, or review resources across the Organisation using the audited Admin View. You can have multiple Org Admins.

  Key powers an Org Admin has that no other role holds:

  * Invite and remove Organisation members
  * Manage Departments
  * Manage billing and subscription settings
  * Use the **Admin View** to access any member's resources (every use is logged)
</Accordion>

<Accordion title="Member (default)">
  Every new person who joins your Organisation starts as a Member. Members create and own resources within the Departments they belong to. They have no Organisation-level admin powers — they cannot invite others, manage billing, or see colleagues' private resources.

  <Note>
    "Member" is the Organisation-level catch-all term. A Member also holds a Department role (Dept Admin, Manager, or Employee) that governs what they can do inside a specific Department.
  </Note>
</Accordion>

## Department Roles

Department roles apply within a single Department. A person can hold different Department roles in different Departments simultaneously. Department roles never grant Organisation-level powers.

<CardGroup cols={3}>
  <Card title="Dept Admin" icon="shield-halved">
    Full control over one Department's members and resources — add or remove members, edit Department settings, manage all resources scoped to that Department. Cannot access private resources of colleagues or perform any org-level actions.
  </Card>

  <Card title="Manager" icon="user-tie">
    Creates and owns resources; handles most everyday operational work inside the Department. Cannot manage Department membership (adding/removing people). Cannot view colleagues' private resources.
  </Card>

  <Card title="Employee" icon="user">
    The base working role. Creates and owns resources within the Department. No management authority over other members or Department settings.
  </Card>
</CardGroup>

<Info>
  The order of authority within a Department is: **Dept Admin > Manager > Employee**. Across the Organisation as a whole, the order is: **Org Owner > Org Admin > (Dept Admin / Manager / Employee)**.
</Info>

## Sharing Levels

When you share a resource with someone, you assign them one of three sharing levels. These levels are independent of the person's Organisation or Department role.

| Sharing Level | Read | Edit & Copy | Re-share                        | Delete / Transfer |
| ------------- | ---- | ----------- | ------------------------------- | ----------------- |
| **Viewer**    | ✅    | ❌           | ❌                               | ❌                 |
| **Editor**    | ✅    | ✅           | ✅ (at or below their own level) | ❌                 |
| **Owner**     | ✅    | ✅           | ✅                               | ✅                 |

<Warning>
  External recipients — people outside your Organisation who receive a shared link — are **always Viewers**. They cannot re-share the resource under any circumstances, regardless of what level you attempt to grant them.
</Warning>

## The Cap-at-Own-Level Rule

You can never grant someone more access than you yourself hold. If you are an **Editor** on a resource, you can share it with others as a Viewer or Editor — but you cannot elevate anyone to Owner. Only the resource Owner can grant Owner-level access.

This rule applies at every level of sharing:

* An Editor sharing with a colleague → max grant is **Editor**
* A Viewer cannot re-share at all
* An Owner sharing with anyone → can grant up to **Owner**

<Tip>
  If you need to give a colleague Owner-level control over a resource you only have Editor access to, ask the current Owner to transfer ownership or to share directly at the Owner level.
</Tip>

## Capability Matrix

The table below shows which actions each role can perform. "Yes" means the role always has this capability; "Dept Admin only" means only that specific Department role qualifies.

| Action                             | Org Owner | Org Admin |  Dept Admin  | Dept Manager |   Dept Employee   |
| ---------------------------------- | :-------: | :-------: | :----------: | :----------: | :---------------: |
| Manage org settings                |     ✅     |     ✅     |       ❌      |       ❌      |         ❌         |
| Toggle external sharing            |     ✅     |     ✅     |       ❌      |       ❌      |         ❌         |
| Invite / remove org members        |     ✅     |     ✅     |       ❌      |       ❌      |         ❌         |
| Manage billing                     |     ✅     |     ✅     |       ❌      |       ❌      |         ❌         |
| Use Admin View                     |     ✅     |     ✅     |       ❌      |       ❌      |         ❌         |
| Create resources                   |     ✅     |     ✅     |       ✅      |       ✅      | Must be in a dept |
| Own / share / delete own resources |     ✅     |     ✅     |       ✅      |       ✅      |         ✅         |
| Edit dept name & colour            |     ✅     |     ✅     | ✅ (own dept) |       ❌      |         ❌         |
| Add / remove dept members          |     ✅     |     ✅     | ✅ (own dept) |       ❌      |         ❌         |

<Note>
  Roles are **additive** and the **highest role always wins**. If you hold both a Manager role in one Department and a Dept Admin role in another, each role applies independently within its own Department. Your Organisation role always takes precedence over any Department role for Organisation-level actions.
</Note>

## Key Rules to Remember

<CardGroup cols={2}>
  <Card title="Highest role wins" icon="trophy">
    When a person holds multiple roles, their effective permissions are the union of all roles they hold. The strongest applicable role governs each action.
  </Card>

  <Card title="Admin View is audited" icon="eye">
    Only Org Owners and Org Admins can activate the Admin View. Every activation is logged in the Audit Log — there is no silent or untracked access to colleagues' private resources.
  </Card>

  <Card title="Dept roles are scoped" icon="building">
    A Dept Admin's power stops at their Department's boundary. They cannot manage other Departments, and they cannot see private resources even within their own Department.
  </Card>

  <Card title="External = Viewer only" icon="lock">
    Anyone outside your Organisation who receives a shared link is locked to Viewer access and cannot re-share the resource with others.
  </Card>
</CardGroup>
