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

# Organizations

> Your agency's workspace: one org, all your clients, four roles.

An organization is your agency's workspace. Every client you track lives inside it as a project, and everything attached to that project (brands, topics, prompts, runs, reports) belongs to the org. Your teammates join the org once and get access to the projects you choose. Your clients can get read-only logins to just their own dashboard.

When you sign up, OpenLens sets up your organization automatically. You can invite teammates and clients into it, or join another organization if someone invites you.

## The four roles

| Role       | What it can do                                                                                    | Costs a seat?                                    |
| ---------- | ------------------------------------------------------------------------------------------------- | ------------------------------------------------ |
| **Owner**  | Everything. Manages members, billing, API keys, can delete the org.                               | Yes                                              |
| **Admin**  | Manages members, projects, and org API keys. Everything except deleting the org.                  | Yes                                              |
| **Member** | Works on the projects you assign. Manager access on a project means edit, viewer means read-only. | Only with manager access on at least one project |
| **Client** | Read-only login for your client. Scoped to the projects you pick, usually one.                    | Never. Free and unlimited                        |

Seats are explained honestly in [Teams and seats](/organizations/teams-and-seats): you pay for people who can edit, and nobody else.

## Per-project access

Owners and admins see every project in the org. Members start with zero. Each project assignment grants exactly one project at one of two levels:

* **Manager**: full edit. Run prompts, edit brands and topics, change settings.
* **Viewer**: read-only. Dashboards, topic performance, reports. No edits.

The same member can be manager on one project and viewer on another. The roles compose per project, so staffing maps directly onto your account assignments.

An agency owner has three clients (Acme, Beta, Gamma) and one staffer, Sarah:

1. Owner invites Sarah as a member, assigned to Acme as manager and Beta as viewer.
2. Sarah signs in and sees exactly two projects.
3. On Acme she runs prompts, edits competitors, changes the schedule. On Beta she can look but never touch.
4. Gamma never appears in her sidebar. She has no way to know it exists.

## Where you manage all this

* **Team** (in the sidebar, owners and admins only): invite teammates and clients, manage roles, see the full roster.
* **Access** (per project, owners and admins only): add or remove members on the project you have open, flip manager vs viewer.
* **Usage** (owners, admins, and members): the org's credit pool, per-project and per-member usage, and the named seat list.

<CardGroup cols={2}>
  <Card title="Teams and seats" icon="users" href="/organizations/teams-and-seats">
    Inviting teammates, what costs a seat, and what happens at the cap.
  </Card>

  <Card title="Client logins" icon="handshake" href="/organizations/client-access">
    Give every client a live dashboard instead of a monthly PDF.
  </Card>

  <Card title="API keys and MCP" icon="key" href="/organizations/api-keys-and-mcp">
    Org-scoped service keys that survive employee turnover.
  </Card>
</CardGroup>
