---
title: "Team members"
description: "Invite and manage organization members in the Metalhost dashboard — roles, invites, and access."
url: "https://metalhost.net/docs/dashboard/guides/members"
---

# Team members

Open the organization area from the org/project switcher, then choose *members*. This hub shows organization membership and each person's explicit project access.

## Roles

| Role | Can do |
| --- | --- |
| **viewer** | Read-only: compute, storage, networking, billing. |
| **editor** | Create, change, and delete VMs, disks, networks. Cannot change billing or invite members. |
| **admin** | Full control including billing, members, and org settings. |

## Members table

Organization admins can change another member's org role, remove them, and expand a person to grant or revoke access to individual projects. Project owners can manage grants for projects they own; other members see a read-only view.

- You cannot change your own role.
- You cannot demote or remove the **sole admin**.

## Invite someone

**invite member** opens a modal:

- Email (required)
- Display name (optional)
- Role (default: **editor**)

On success you get an `/accept-invite?token=…` link to copy. Share it directly — the UI does not send email automatically.

## Pending invites

Section above the members table when invites are outstanding. Columns: email, role, expiry, **revoke**. To resend: revoke and create a new invite (tokens aren't retrievable).

> **org-wide access**
>
> An organization role and explicit project grants are separate. A member can switch into projects they have permission for; organization admins have implicit access across the org. Project-scoped API keys are separate — see [API keys](https://metalhost.net/docs/dashboard/guides/api-keys.md).

## What's next

- [API keys](https://metalhost.net/docs/dashboard/guides/api-keys.md) — automation credentials per project or org-wide.
- [How it works](https://metalhost.net/docs/dashboard/overview.md) — orgs and projects.