# Team management

> Invite team members and manage roles and permissions.

**Category:** Collaboration | **Tab:** features

---

Black Ice supports collaborative terminology management with role-based access. Invite team members and control what each person can do. Access rules are enforced by the backend, not only hidden in the interface.

## Roles

Every workspace has exactly **one Owner**. Everyone else is an Admin, Editor or Viewer.

| Role | In short |
|------|----------|
| **Owner** | Full control, including billing, GitHub Sync and transferring ownership |
| **Admin** | Runs the team and workspace settings, and edits all ontology data |
| **Editor** | Creates and edits ontology data and reviews candidates |
| **Viewer** | Read-only access to the workspace's ontology |

## Who can do what

| Action | Owner | Admin | Editor | Viewer |
|---|:-:|:-:|:-:|:-:|
| View concepts, terms, markets, relationships, activity | Yes | Yes | Yes | Yes |
| Create, edit and delete concepts, terms, classes, relationships | Yes | Yes | Yes | — |
| Import and bulk-edit (CSV/Excel, batch availability) | Yes | Yes | Yes | — |
| Send terms for approval | Yes | Yes | Yes | — |
| Review candidates (approve, merge, reject) | Yes | Yes | Yes | — |
| Create and revoke API keys | Yes | Yes | Yes | — |
| Edit the Market Definition template | Yes | Yes | — | — |
| Allow AI assistants to suggest candidates | Yes | Yes | — | — |
| Invite, remove and change roles of members | Yes | Yes | — | — |
| Documents & Compliance (Pro and Builder) | Yes | Yes | — | — |
| Set up GitHub Sync | Yes | — | — | — |
| Billing and plan changes | Yes | — | — | — |
| Transfer ownership | Yes | — | — | — |

Editors and viewers can still *see* the Market Definition template and the AI suggestions switch; they just can't change them.

## Inviting team members

1. Go to **Settings → Team Management**.
2. Click **Invite Member**.
3. Enter the person's email and pick a role.
4. Click **Send Invite**.

The invitee gets an email with a link to accept. If they don't have a Black Ice account yet, they create one first, using the same email address.

## Invitation lifecycle

- Invitations expire after **7 days**.
- A pending invitation can be **resent**. Resending keeps the same link and gives it a fresh 7 days.
- You can **cancel** a pending invitation at any time.
- If sending the email fails, you see an error straight away instead of a silent failure.
- Once accepted, the person appears in the workspace with their role.

## Changing roles

Owners and Admins can change a member's role at any time from Team Management. The Owner role can't be given this way; use ownership transfer instead.

## Transferring ownership

A workspace has one Owner. To hand it over:

1. Make sure the new owner has **joined** the workspace and is an **Admin**.
2. The current Owner opens **Settings → Team Management** and chooses to transfer ownership to that Admin.

The new owner gets full control. The previous owner becomes an Admin and loses owner-only rights, such as billing and GitHub Sync.

## Plan shown to members

Everyone in a workspace works under the **workspace's plan**, which is the Owner's plan. Invited members see that plan's badge and limits, not their own. Billing pages still show each person's personal plan.

## Removing members

Owners and Admins can remove members. Access ends straight away, and the person gets an email saying they were removed. Their contributions (concepts, terms, approvals, history) stay in the workspace.

## Viewer experience

Viewers see a **View only** banner. Create, edit, delete, import and relationship actions are hidden. Opening a create or import page directly sends them back to the concepts list. The backend refuses viewer changes even if someone gets around the interface.

## Plan limits

Team members are available on the **Builder** plan, with up to **10 members** per workspace.

See also: [Permissions & data visibility](/docs/features/permissions-and-data-visibility), [Approval workflows](/docs/features/approval-workflows), [Candidate review workflow](/docs/features/candidate-review-workflow).