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

# Teams and roles

> Organisation roles, team roles, invitations, and who can see assets and change integrations and alert settings in Expira.

## Organisation roles

| Role | Can |
| - | - |
| **Owner** | Everything an admin can. There is one owner, and ownership can be transferred. |
| **Admin** | See every asset, manage members and teams, add and change integrations, and change every team's alert settings. |
| **Standard User** | See their teams' assets and their own private assets, and manage their personal alert settings. |

## Team roles

| Role | Can |
| - | - |
| **Maintainer** | Edit the team and change its alert preferences and delivery channels. |
| **Guest** | See the team's assets and alert settings without changing them. |

## Who can do what

| Action | Who |
| - | - |
| See a team asset | Members of that team, and organisation owners and admins |
| See a private asset | Its owner, and organisation owners and admins |
| Add, edit or delete a team asset | That team's maintainers, and organisation owners and admins. Being a team asset's owner gives no extra rights |
| Add a private asset | Any member, for themselves |
| Edit or delete a private asset, or give it to someone else | Its owner can edit and delete it; organisation owners and admins can also hand it to another member |
| Invite, deactivate, remove members or change their role | Organisation owners and admins (never the owner, who can't be removed) |
| Make someone the owner | Only the current owner, by transferring ownership |
| Add someone to a team | Team maintainers, and organisation owners and admins; only active members of the organisation can join a team |
| Add, sync, pause or remove integrations | Organisation owners and admins |
| Change a team's alert preferences and channels | Team maintainers, and organisation owners and admins |
| Change personal alert preferences and channels | You, for your own |

Team assets alert the team's active members. See [How alerts work](https://docs.expira.dev/alerts/overview.md#who-receives-alerts).

## Invitations

Owners and admins invite people by email from **Settings → Organisation**. The invitation is for that email address only and lasts 7 days.

* The person opens the link, signs in with that address (a new address gets an account through the same magic link), and presses **Accept invitation**.
* A pending invitation counts as a seat on your plan, so inviting fails once members plus pending invitations reach the plan's member limit.
* Each email can have one pending invitation per organisation. Inviting the same address again shows the existing link instead of sending another email.
* An organisation can send at most 20 invitations a day.
* Someone who is already a member, or who was deactivated, can't be invited: reactivate them instead.

Deactivating someone keeps their account and team memberships but removes all access until they're reactivated, and cancels their pending invitations. Removing someone (or leaving) also takes them off every team.

If you belong to no workspace (for example an invitation expired before you accepted it), Expira asks you to create one, and lists any invitations still waiting for you.


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