# Team and roles

> Inviting people to a team, the four roles — owner, member, viewer, billing — and transferring a project to another account.

Source: https://livops.dev/en/docs/teams

Every account has its own team. Projects, databases, domains and billing belong to the team. One person can be in several teams; the cabinet has one open at a time.

## Roles

| Capability | owner | member | viewer | billing |
| --- | :-: | :-: | :-: | :-: |
| View projects, logs | ✓ | ✓ | ✓ | ✓ |
| Deploys, variables, domains, databases | ✓ | ✓ | — | — |
| Pay the bill | ✓ | — | — | ✓ |
| Invite people, change roles | ✓ | — | — | — |
| Create API tokens | ✓ | — | — | — |
| Delete or transfer a project | ✓ | — | — | — |
| Close the team | ✓ | — | — | — |

- **viewer** — view only.
- **billing** — views and pays, changes nothing else.
- The **owner** role can't be given to someone else.

## Invite

Under the team's **Settings → Members** (`/<team>/settings/members`), enter the person's email and choose a role — they are added to the team right away, and no email is sent. **You can only add someone who already has a Livops account** — they need to sign up first.

- The owner can remove any member (except themselves).
- A member can leave the team on their own.

## Limits

- One account can own at most **3** teams. Membership in other teams doesn't count.
- An empty team can be closed; you can't close your only team.
- New teams have no trial period.

## Transfer a project

You can give a project to another Livops account: the owner sends an invite and the recipient accepts. The project moves along with its variables, and the new owner's plan limits are checked on acceptance. A project can have only one open transfer invite at a time.

## Teams in the API

The `X-Team` header tells the API which team a request is about. An API token is bound to a single team — [API tokens](https://livops.dev/en/docs/api-tokens).
