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

# Organization Role Matrix

> Compare conceptual Starfire AI organization roles and use least privilege when assigning membership access.

# Organization role matrix

Organizations need predictable separation between ownership, administration, development work, and normal membership.

The active Organizations 3.0 implementation is the source of truth for exact role names and permissions. This page documents the intended responsibility model.

| Capability                              | Owner |        Admin |    Developer |  Member |
| --------------------------------------- | ----: | -----------: | -----------: | ------: |
| View organization                       |     ✓ |            ✓ |            ✓ |       ✓ |
| Invite members                          |     ✓ |            ✓ |            — |       — |
| Change normal member roles              |     ✓ |            ✓ |            — |       — |
| Change owner-level access               |     ✓ |      limited |            — |       — |
| Manage projects                         |     ✓ |            ✓ |            ✓ | limited |
| Manage Knowledge                        |     ✓ |            ✓ |            ✓ | limited |
| Create organization developer resources |     ✓ |            ✓ |            ✓ |       — |
| View usage                              |     ✓ |            ✓ | configurable | limited |
| View billing                            |     ✓ | configurable |            — |       — |
| Change plan/seats                       |     ✓ | configurable |            — |       — |
| Change organization policy              |     ✓ |            ✓ |            — |       — |
| Delete/transfer organization            |     ✓ |            — |            — |       — |

## Owner

Use the owner role for the people ultimately responsible for the organization, including ownership transfer and highest-impact organization actions.

## Admin

Admins run normal organization operations without necessarily receiving every owner-only destructive or transfer capability.

## Developer

A developer role can manage technical project and developer resources without automatically receiving organization billing or membership authority.

## Member

A member receives normal team participation and the specific project/resource access granted by organization policy.

## Resource permissions still apply

A broad organization role does not need to imply access to every project or Knowledge source. Resource-level permissions can create smaller collaboration boundaries.

<Warning>
  Do not use the owner role as a convenient fix for a missing project permission. Identify the actual permission layer first.
</Warning>

<Card title="Permission model reference" icon="shield-check" href="/reference/permissions-matrix">Compare organization roles with resource, developer, and Control Center permissions.</Card>