# Teams & membership
Source: https://docs.aden.space/docs/help/work-together/teams

The workspace unit in Aden. A group of collaborators who share tracks, projects and settings, with role-based access and plan-based seat limits.
{/* Generated by `bun docs:publish` from docs/features/teams.md: edit the spec, not this file. */}

## What it is [#what-it-is]

A **team** is your workspace in Aden. Everything you create: tracks, albums,
sessions, release plans, contacts. Lives inside a team. You can belong to
multiple teams and switch between them at any time.

Teams can be just you, or a group of collaborators: a band, a production duo,
or an artist managed by a label. Each member has a **role** that controls what
they can see and do.

## Using it [#using-it]

**Create a team.** Go to **New team** from the team switcher or the
`/app/teams/create` page. Give your team a name, a slug (the short URL
identifier), and optionally a timezone. Your account is automatically added as
the admin: you don't need to do anything else for yourself.

**Invite collaborators.** From your team's settings, go to the **Members** tab
and enter an email address. The person receives an invitation email with a
link. They can accept or decline from the link or from the **Invites** page in
the app. An invitation expires after a configurable number of days (default 7).
You can also invite from any people dropdown (task and milestone assignees,
signer pickers): when the person you're looking for isn't listed, the dropdown
offers **Invite "\<what you typed>" to the team** instead of dead-ending on "no
results".

**Collaborators tab.** `/app/teams/[teamId]/members/collaborators` lists the
people credited on the team's tracks who aren't on the roster, sorted by how
many of its tracks they are credited on. Each person is a card: avatar, name,
email, credit count, and a menu holding view profile, message, copy email, and
invite to the team (the last only with `team:invite`). Someone credited by name
or email alone, with no Aden account, is marked "No account" and can only be
copied or invited.

A pending invite for a team you already belong to never shows: the pending
list excludes your active memberships, and adding someone directly from admin
marks their open invite for that team as accepted. Team and organisation admins
get the member-joined notification on a direct add too, with "was added"
instead of "accepted their invitation".

**Decide the access before they join.** The invite dialog sets what the seat is
worth: the **role** (what they can do), the **feature access** (which parts of
the workspace they see, either everything minus some features or only the ones
you grant) and an optional **expiry**. So a designer can get media and the
calendar for one month, and nothing else, without inviting them to everything
first and locking it down afterwards. Custom feature scopes and expiry need the
plan that unlocks custom permissions; picking a role does not.
How many people you can invite depends on your plan, unless an organisation
manages your team, in which case it covers your members and no seat limit
applies.

**Manage roles.** Each member is either an **Admin** or a **Member**. Admins
can invite and remove people, change team settings, and manage billing. Members
can work on content but cannot change who else has access. You can also set a
display **title** for each member (e.g. "Producer", "A\&R") and flag them as an
**artist**: artist-flagged members can be auto-added as collaborators on new
tracks if the team has that setting enabled.

**Deactivate or remove someone.** Deactivating a member soft-deletes their
access (`deactivated_at` is set) without removing the row, so their history is
preserved. They can be reactivated later. Removing permanently ends the
membership. You can also **leave** a team yourself as long as at least one
admin remains.

**Switch the active team.** The active team is stored in a cookie and drives
the sidebar and all team-scoped queries. Use the team switcher in the top-left
or navigate directly to a team URL. Deleting the active team clears that cookie
and returns you to your Personal workspace, so the switcher never lingers on a
team that no longer exists.