# Organizations

> Share balances, keys, limits and provider resources with a team, with roles that decide who can spend, fund and administer.

Source: https://0.0.0.0:3000/docs/account/organizations
Documentation index: https://0.0.0.0:3000/docs/llms.txt

An organization is a shared account with its own balances, API keys, spending limits, usage history and provider resources, separate from each member's personal account. Roles decide who can administer members, add funds, see every key and run provider endpoints. Every action is checked against current membership, so a role change or removal applies to the next request.

## Personal and organization accounts

When you first sign in, Numes creates a **personal account** for you, shown as **Personal**. You're its only user and can do everything in it. An **organization account** has members, and you can belong to several.

| | Personal account | Organization account |
| --- | --- | --- |
| Users | Only you | Every member |
| Balances, keys, limits, usage | Yours | Shared by the organization |
| Who can fund and administer | You | Owners and administrators |
| Provider resources | Yours | Managed by owners, administrators and provider operators |

## Switch accounts

The account switcher in the dashboard selects the active account. Balances, keys, spending limits, funding, Activity, Logs and providers all follow that choice. With your personal account active, [Organization](/dashboard/organization) lists your organizations, each with **Switch**.

An API key belongs to the account it was created in; there's no header to choose an account per request. Your profile, sign-in methods and [support tickets](/docs/account/support) belong to you as a person and stay the same in every account.

## Create an organization

Open [Organization](/dashboard/organization) and choose **Create organization** (or **New organization** once you belong to one). Enter a **Display name** (1–160 characters) and a **Handle**. The handle is suggested from the name, appears as `@handle` and can't be changed later. You become the first owner and can switch to the organization straight away.

A new organization starts with empty balances: add credits and create keys after switching to it.

## Roles

A member holds one or more roles.

| Role | For |
| --- | --- |
| **Owner** | People accountable for the organization. Full control, including over other owners |
| **Administrator** | Day-to-day administration: members, funding, every key |
| **Member** | People who build with the organization's balance using their own keys |
| **Provider operator** | People who run the organization's provider endpoints |

| Action | Owner | Administrator | Member | Provider operator |
| --- | --- | --- | --- | --- |
| View members | ✓ | ✓ | ✓ | ✓ |
| Create inference and management keys | ✓ | ✓ | ✓ | ✓ |
| See and manage keys | All | All | Own keys | Own keys |
| View Activity and Logs | All traffic | All traffic | Own keys' traffic | Own keys' traffic |
| Add credits, auto top-up, saved cards | ✓ | ✓ | — | — |
| Set account spending limits | ✓ | ✓ | — | — |
| Edit the [request policy](/docs/privacy/request-policy) | ✓ | ✓ | — | — |
| Invite members and revoke invitations | ✓ | ✓ | — | — |
| Change roles and remove members | ✓ | ✓, except owners | — | — |
| Grant the owner role | ✓ | — | — | — |
| Manage provider endpoints and offers | ✓ | ✓ | — | ✓ |
| Delete a provider | ✓ | ✓ | — | — |
| View and withdraw provider earnings | ✓ | ✓ | — | — |
| Leave the organization | ✓, unless the last owner | ✓ | ✓ | ✓ |

Two rules protect every organization:

- An administrator can't change or remove an owner, or make anyone an owner.
- The last owner can't be removed, lose the owner role or leave. Make someone else an owner first.

## Invite members

Owners and administrators invite people by email address. The person doesn't need an account yet.

:::steps
### Send the invitations

In [Organization](/dashboard/organization), choose **Invite people**. Enter up to 10 email addresses, separated by commas or spaces, choose the roles (**Member**, **Administrator** or **Provider operator**) and choose **Send invitation**. The owner role can't be granted by invitation; promote an existing member instead.

An address that already belongs to a member, or already has an open invitation, isn't invited again.

### The invitee opens the link

Each person receives an email with a **View invitation** link. If it doesn't arrive, choose **Copy link** next to a sent invitation and share it privately; the link is shown only then.

The link shows the organization, who sent the invitation, the role and a partly hidden version of the invited address. Someone without an account chooses **Create account**; someone with one chooses **Sign in**.

### The invitee joins

After signing in, the invitee chooses **Join**, **Not now** or **Decline**. Joining makes the organization their active account.
:::

An invitation works only for the email address it was sent to, and only once that address is verified. Signed in as someone else, the invitation page offers **Sign out and continue**.

Invitation links are sensitive. Don't paste them into tickets, logs or shared channels.

### Invitations you receive

Invitations to your verified email appear at the top of [Organization](/dashboard/organization), and the **Organization** item in the sidebar shows how many are waiting. Choose **Join** or **Decline**.

### Manage sent invitations

**Invitations** lists open invitations, with **Resend invitation** and **Revoke**, and declined ones, with **Invite again**. Invitations expire after 7 days.

- **Resending** sends a new link; earlier links for that invitation stop working. The expiry doesn't change. Resends are rate-limited, and the button shows when you can send again.
- **Revoking** stops the link from working.

## Keys in an organization

Every member can create keys in the organization, and they spend the organization's balance. Owners and administrators see every key and its usage and can edit, disable or delete any of them; other members see and manage only the keys they created.

A key, including a management key, acts with its creator's current role. It stops authenticating as soon as its creator leaves or is removed, or their identity is suspended or deleted. Have production keys created by a long-term owner or administrator. See [Management keys](/docs/account/management-keys#authority-follows-the-creator).

Everyone's keys draw on the same balance, so set [spending limits](/docs/account/credits#spending-limits) on the account and on individual keys to keep one project from using up the rest. See [Credits and payments](/docs/account/credits) and [Bitcoin payments](/docs/account/bitcoin).

## Shared models

Providers run by the organization can share a model with its members instead of publishing it to everyone. Shared models are listed under **Shared models** in [Organization](/dashboard/organization), are free for members, and use a model ID ending in `:org-<handle>`. See [Models](/docs/models).

## Manage members

**Members** lists everyone with their name, email address, roles and the date they joined. Every member can see it. Each member's **⋯** menu holds the actions you may take:

- **Change roles** replaces the member's roles immediately.
- **Remove from organization** ends their access to the organization, its keys and its resources immediately.

Before removing someone, replace keys they created that your applications depend on: those keys stop working at removal. Past usage stays in Activity.

## Leave an organization

Choose **Leave organization** from the **⋯** menu next to the organization's name, or from your own row in **Members**. You lose access immediately, keys you created there stop working, and your personal account becomes active. To return, someone has to invite you again.

You can't [delete your account](/docs/privacy/account-security#delete-your-account) while you're the only owner of an organization. Organizations keep their balances and history after a member leaves or deletes their account.

## Next steps

:::cards
- {key} [API keys](/docs/account/api-keys) Create keys and set per-key limits.
- {coins} [Credits and payments](/docs/account/credits) Fund the organization balance.
- {activity} [Activity and logs](/docs/account/activity) See usage by key, member and app.
- {server} [Become a provider](/docs/providers/overview) Serve models as an organization.
- {shield} [Account security](/docs/privacy/account-security) Protect the identities that can act on the organization.
:::