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

# Organization management

> How organizations, members, and roles work — and how project access stays scoped to the people you add.

Your account lives in one **organization** — the billing and membership boundary. Credits are pooled across it, and everyone you invite shares it. Projects belong to the org, but access to each one is granted per project, not org-wide.

## Members and roles

An org **owner** or **admin** invites people by email; accepting the invite adds them to the org. Every member holds one role:

| Role       | Can                                                                                            |
| ---------- | ---------------------------------------------------------------------------------------------- |
| **Owner**  | Everything — edit org settings and billing, invite or remove members (any role), change roles. |
| **Admin**  | Invite members (member or admin) and revoke invites.                                           |
| **Member** | Belong to the org and to the projects they're added to.                                        |

<Note>
  **Where:** Platform → **Profile** → **Organization** — invite and manage org members.
</Note>

## Projects aren't shared by default

Adding someone to the org does **not** hand them your projects. Each project is private to the people explicitly added to it — so teammates in the same org can work on entirely different projects without seeing each other's.

To grant access to a specific project, its **owner** invites the person from **Project Settings → Members** — by email, or one-click for existing org members during the [project wizard](/guide/setup-project). Project roles are **owner** and **member**.

This keeps work compartmentalized: bring a contractor or teammate into just the one project they need, without exposing the rest of the org's. For work whose context must not even reach shared org memory, see [memory-isolated projects](/features/memory#isolated-projects).

## See also

* [Set up a project](/guide/setup-project) — invite teammates during setup