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

# Team Management

> Manage workspace members, roles, and permissions

Team management is where Admins and Owners control who has access to the organisation, what role they have, and how to onboard new members. Open it from **Management > Team** in the sidebar.

Everyone in the organisation can open the page and see the member list. Only Admins and Owners see the **Add user** button and the per-row actions menu.

## Roles

Odin has four roles: **Owner**, **Admin**, **Member**, and **Read only**, each with a different level of access. See [Roles & Permissions](/platform/roles-and-permissions) for a full breakdown of what each role can do.

<Note>
  Owners cannot be edited or removed from within Odin, by anyone. To change or remove an Owner, contact [mail@borghq.io](mailto:mail@borghq.io).
</Note>

## Inviting members

<Steps>
  <Step title="Open the Team page">
    Go to **Management > Team** in the sidebar.
  </Step>

  <Step title="Click Add user">
    The **Invite team members** dialog opens with one empty row.
  </Step>

  <Step title="Enter an email and role for each person">
    Add a row per person, up to 20 at a time, and pick a role for each one. The role list only offers roles below your own, so an Admin can invite Members and Read only users but not another Admin. The dialog rejects an email that appears twice in the same batch.
  </Step>

  <Step title="Confirm your identity">
    Inviting requires [step-up verification](/platform/step-up-verification), so you are asked to confirm who you are before the invitations go out.
  </Step>

  <Step title="Invitations sent">
    Each person receives an email telling them who invited them, to which organisation, and with what role, plus a link to the Odin sign-in page. They appear in the team table straight away with an **Invited** badge.
  </Step>
</Steps>

There is no separate acceptance step. The membership is created when you send the invitation, and the badge changes to a joined date the first time that person signs in.

<Info>
  If your plan has no seats left, the dialog stops on the first blocked row and shows a **Manage seats** link through to [Billing](/platform/billing). Invitations already sent in that batch still stand. Inviting someone who is already in the organisation is rejected rather than duplicated.
</Info>

## Searching and filtering

Above the team table you can:

* **Search** by name or email
* **Filter** by role (Owner, Admin, Member, Read only)

The table lists everyone matching your filters with their name, email, role, and the date they joined, shown as a relative time such as "3 months ago". People who have not signed in yet show an **Invited** badge in that column instead.

You can move through the rows with the [list navigation keys](/platform/command-palette). For Admins and Owners, **Enter** opens the edit dialog for the highlighted member.

## Changing a role or name

Click a member's row, or use the actions menu on the right and choose **Edit**, then change their role, first name, or last name. The row is only clickable for members you are allowed to manage. The rules the platform enforces:

* Only Admins and Owners can edit anyone
* You can only edit someone whose role is below your own, so an Admin cannot edit another Admin
* You can only assign roles below your own
* You cannot change your own role
* Nobody can edit an Owner

Everyone in the organisation gets a notification when a role changes.

## Removing a member

Choose **Remove** from the member's actions menu, or from inside their edit dialog, then confirm. You cannot remove yourself, you cannot remove an Owner, and you can only remove someone whose role is below your own. Removal requires [step-up verification](/platform/step-up-verification).

Removing someone frees their seat, and your subscription is updated to match the new member count.

## Resending an invitation

If someone has not signed in yet, open their actions menu and choose **Resend invite** to send the same email again. Once they have signed in at least once, resending is no longer available, since they already have access.

## Exporting the team list

Use the **Export** dropdown next to **Add user** to download the current list as CSV, Markdown, or JSON. The export covers whatever the filters are currently showing and includes name, email, role, status, and joined date. Every role can use it, so a Read only auditor can pull an access list without help.
