# Members

The workspace **Members** page shows who has access to the workspace and what each person can do. Owners and admins invite people here and change their roles.

## Before you start [#before-you-start]

- To open the page, go to the workspace **Settings** and click **Members** in the **Workspace Settings** sidebar. See [Settings](/workspace/settings).
- Every role can open the **Members** page. Only owners and admins can invite, change roles and remove people.
- To invite people, the workspace needs a paid plan. The Free plan is for one person.

## Roles [#roles]

Each person in a workspace has one role. The role shows as a chip next to the name: **Owner**, **Admin** or **Member**. Each workspace has one owner.

| What a person can do | Owner | Admin | Member |
|----------------------|-------|-------|--------|
| See all domains and their data | Yes | Yes | Yes, read-only |
| Add, change and delete domains | Yes | Yes | No |
| Set up alerts, reports and module settings | Yes | Yes | No |
| Rename the workspace | Yes | Yes | No |
| Invite people, change roles, remove people | Yes | Yes | No |
| Connect Google accounts, Slack and webhooks | Yes | Yes | No |
| Create API keys | Yes | Yes | No |
| See every row of the data access log | Yes | Yes | Only their own rows |
| Open Billing and change the plan | Yes | No | No |
| Set API credit caps for members | Yes | No | No |
| Transfer ownership and delete the workspace | Yes | No | No |

### What a member sees [#what-a-member-sees]

A member sees the domain pages in read-only mode. A member can read every report, chart and table, but cannot change settings, add domains or create alerts. The Dashboard does not show the **Add a domain** button to a member. The workspace sidebar does not show **Billing** to a member.

On the [API credits](/workspace/api-credits) and [Data access log](/workspace/data-access-log) pages, a member sees only the requests from their own API keys and connected apps.

## Team members list [#team-members-list]

The **Team members** card lists each person in the workspace. Each row shows:

- The avatar and the name, or the email address if the person has no name.
- The role chip: **Owner**, **Admin** or **Member**.
- The chip **You** on your own row.
- The email address below the name.

Owners and admins see a menu (three dots) at the end of each row, except the owner row. The owner also sees the API credits of each person. See [Credit caps for members](#credit-caps-for-members).

## Invite a member [#invite-a-member]

Owners and admins can invite people on a paid plan.

1. Click **Invite member** at the top right of the **Members** page.
2. In **Email address**, enter the email of the person.
3. In **Role**, select **Member – view only** or **Admin – can manage domains and members**.
4. Click **Send invitation**.

The message **Invitation sent successfully** confirms it. The person gets an email with a link to join. If the email address is not valid, the form shows **Enter a valid email address**.

### Accept an invitation [#accept-an-invitation]

The invited person clicks the link in the email and signs in, or creates an account. If they already have an account, the Dashboard shows a banner with **Accept** and **Decline**. See [Dashboard](/workspace/dashboard#workspace-invitations).

### Invite button on the Free plan [#invite-button-on-the-free-plan]

On the Free plan, the **Invite member** button does not show. Owners and admins see the message **Inviting teammates needs a paid plan**. The owner reads "The Free plan is for one person. Upgrade your workspace to invite teammates." and sees a **Compare plans** button that opens [Billing](/workspace/billing). An admin reads "The Free plan is for one person. Ask the workspace owner to upgrade the plan to invite teammates."

## Pending invitations [#pending-invitations]

The **Pending invitations** card shows invitations that nobody accepted yet. Only owners and admins see it. Each row shows the email address, the role and the expiry date, for example "Invited as member · Expires Nov 2, 2026".

- To send the email again, click the refresh icon (**Resend invitation email**). The message **Invitation email resent** confirms it.
- To cancel an invitation, click the X icon (**Cancel invitation**). The message **Invitation canceled** confirms it.

## Change a role [#change-a-role]

Owners and admins can change the role of an admin or a member.

1. Click the menu (three dots) at the end of the row.
2. Click **Make admin** or **Make member**.

The message **Role updated successfully** confirms the change. The new role applies immediately.

## Transfer ownership [#transfer-ownership]

Only the owner can transfer ownership, and only to a person who is already in the workspace.

<Callout type="warn">
  After the transfer, you become an admin. The new owner gets full control of the workspace, which includes billing, settings and the right to remove you.
</Callout>

1. Click the menu (three dots) on the row of the new owner.
2. Click **Transfer ownership**.
3. Read the message and click **Transfer ownership**.

The message **Ownership transferred successfully** confirms the transfer.

## Remove a member [#remove-a-member]

Owners and admins can remove an admin or a member. You cannot remove the owner.

<Callout type="warn">
  The person loses access to this workspace and everything in it immediately. To give access again, send a new invitation.
</Callout>

1. Click the menu (three dots) at the end of the row.
2. Click **Remove**.
3. Click **Remove** in the confirmation dialog.

The message **Member removed successfully** confirms it.

## Credit caps for members [#credit-caps-for-members]

A credit cap limits how many API credits one person can spend in each billing cycle. API credits pay for requests from API keys and connected apps, such as AI assistants. Only the owner sees the credits and the caps.

Each row shows the credits the person spent, for example "120 credits spent". A chip shows the cap, for example **Cap 500**, or **Blocked** for a cap of 0. A person without a cap has no chip. The chip **None left** shows when the person cannot spend more credits. Hover over the credits to see **Spent this cycle**, **Cap** and **Left to spend**.

### Set a credit cap [#set-a-credit-cap]

1. On the row of the person, click **Set cap** or **Edit cap**.
2. In **Cap per cycle**, enter a whole number of credits.
3. Click **Save cap**.

Leave **Cap per cycle** empty for no cap. Enter 0 to block the person from the API and MCP. The cap applies to every cycle and starts again when the allowance refills. A cap does not add credits.

The dialog shows what the person can spend right now. A person can spend the smaller amount: what is left of their cap, or what is left of the workspace balance. See [API credits](/workspace/api-credits).

## Troubleshooting [#troubleshooting]

### Why can I not invite a member? [#why-can-i-not-invite-a-member]

If the workspace is on the Free plan, the **Invite member** button does not show. Upgrade to a paid plan on the [Billing](/workspace/billing) page. If you are a member, ask an owner or admin to send the invitation.

### Why did the invitation email not arrive? [#why-did-the-invitation-email-not-arrive]

Ask the person to look in their spam folder. Make sure that the email address is correct. Then click **Resend invitation email** in the **Pending invitations** card.

### Why can I not change settings on a domain? [#why-can-i-not-change-settings-on-a-domain]

If your role is **Member**, you see domain pages read-only. Ask an owner or admin to make you an admin.

### Why can I not remove the owner? [#why-can-i-not-remove-the-owner]

A workspace always has one owner. The owner must first transfer ownership to another person. Then the new owner can remove the old owner, who is now an admin.

## Related [#related]

- [Settings](/workspace/settings) - the workspace summary, rename and delete
- [API credits](/workspace/api-credits) - the credit balance of the workspace
- [Billing](/workspace/billing) - upgrade to invite teammates
- [Plans and limits](/workspace/plans-and-limits#domains-and-team) - the team size of each plan
