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

# Organizations & members

> The organization is the billing entity; users are members.

Everything in Naive Managed Agents belongs to an **organization** — the billing entity that holds the credit balance and owns every agent, computer, skill, and identity. Users are **members**.

## Model

```
organization  (billing entity, owns everything)
├── members            users with a role: owner | admin | member
├── api keys           programmatic access, org-scoped
├── credit balance     real US dollars
├── agents             each with its own budget
├── computers
├── skills
├── files
└── identities
```

## Roles

| Role | Can do |
| - | - |
| `owner` | Everything, including billing, members, and deleting the org. |
| `admin` | Manage agents, computers, skills, keys, and view billing. |
| `member` | Create and run agents within the org's resources. |

## Managing an organization

```bash CLI theme={"system"}
vetta org create --name "Acme"
vetta org list
vetta org use <org_id>              # set the active org for subsequent commands
vetta org invite --email alice@acme.com --role admin
vetta org members                   # members are addressed by their usr_ id
vetta org set-role usr_... --role member
```

```typescript TypeScript theme={"system"}
const org = await vetta.orgs.create({ name: "Acme" });
await vetta.orgs.addMember(org.id, { email: "alice@acme.com", role: "admin" });
```

## API keys

Programmatic access uses org-scoped API keys. Keys can carry scopes to limit what they can do.

A company created by a signed-in customer is `live`, because customer onboarding continues directly
to subscription checkout — Standard with its 7-day free trial, or Pro ([Plans](https://vetta.sh/docs/platform/pricing.md#plans)). Keys created inside it therefore use the `sk_live_…` prefix. A company
created by an API key inherits that key's mode, so an `sk_test_…` credential cannot mint live access.

```bash CLI theme={"system"}
vetta keys create --name ci --scopes agents:write,sessions:write
vetta keys list
vetta keys revoke <key_id>
```

> [!WARNING]
>
> An API key is shown once at creation. Store it securely; it cannot be retrieved again.

## Compliance & tenancy

| Area | Today | Roadmap |
| - | - | - |
| **Tenancy** | Logical multi-tenancy: every organization's data is isolated per-org and scoped by org id on every request. | Dedicated single-tenant deployment is not offered yet. |
| **Data residency** | All organization data is stored in Managed Agents' primary region. | Region pinning is planned. |
| **Certifications** | None claimed yet. | SOC 2 Type II and related attestations are on the roadmap. |
| **Data handling** | Secrets are held in the [vault](https://vetta.sh/docs/identity/vault.md) and injected at the network boundary; transcripts and files are org-scoped and retained per plan. | Configurable retention windows. |

> [!NOTE]
>
> Roadmap items above are planned, not shipped — if one is a hard requirement for your deployment, contact us before building on it.

## Bootstrapping

Signing up creates your organization, adds you as `owner`, and opens a credit balance in one step. Default resources are created lazily on first use.

> [card] [Next: credits & billing](https://vetta.sh/docs/platform/billing.md)
>
> How real-dollar credits and billing work.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.