# Team and roles

> Invite members to a DigitSpace organisation, choose their roles, set their budgets and access rules, and organise them in teams.

Source: https://digitspace.ai/docs/dashboard/team · Last checked: 2026-10-31

Owners and admins manage people under **Team**.

## Roles

| Role              |                                                                                                                            |
| ----------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **Owner**         | Everything. Only owners add, change or remove owners and delete projects. An organisation always keeps at least one owner. |
| **Admin**         | Billing, team, provider keys, guardrails and settings, across all projects.                                                |
| **Project admin** | Manages the projects assigned to them: settings, routing and every key in them.                                            |
| **Developer**     | Uses the projects assigned to them, with their own keys, within a budget.                                                  |

Assigning project admins and developers to particular projects is part of Enterprise.

## Invite someone

Choose **Invite a member**, enter their email and role (and projects, for the two project roles). They get an email with a link; people who already have an account are added straight away. Pending invitations can be revoked.

## A member's menu

- **Role and projects**
- **Budget:** the most they may spend, in total and per period, and how many API keys they may have. See [Budgets](/docs/control/budgets#on-a-member).
- **Move to team**
- **Access rules:** models, providers, prices and IP addresses they may use. See [Access rules](/docs/control/access-rules).
- **Usage details:** their spend, requests, tokens, error rate and top models.
- **Remove:** their API keys stop working.

## Teams (Enterprise)

A team groups developers with a **per-developer budget**, projects and **team access rules**. One team can be the default that new developers join. With SSO, groups in your identity provider can place people in teams.