# Members.

Who can use a workspace and what each role can do. An Admin invites people, changes a role, or removes someone in Setup, under Members.

Updated 7 October 2026.

## Roles

- **Admin.** Everything a member can do, plus Setup: code hosts and repos, telemetry, network access, relay tokens, members, and deleting the workspace.
- **Member.** The work itself: submit ideas, start and stop work, review and close cases, and approve or reject what waits in Inbox.
- **Viewer.** Reads the workspace and changes nothing.

A person has one role in a workspace. Someone in two workspaces can hold a different role in each.

## The member list

Setup lists everyone who has signed in to the workspace, Admins first and then by most recent sign-in. Each row shows the person's name and email, their role, how they sign in (single sign-on, Google, password, and so on), and when they last signed in. Hold the pointer on the time to see the exact time. How someone signs in shows after their next sign-in. Use **Find a person** to narrow the list by name or email.

An Admin who has never signed in is marked **Never signed in**, because they may not be able to act for the workspace. Perfloop records sign-ins, not activity, so the list has no last-active time.

## Invite people

Choose **Invite people**, enter an email, pick a role (Member unless you choose another), and send. The person gets an email that names you; they join with that role when they accept it and sign in. Until then the invitation waits under **Pending invitations**, where you can **Resend** or **Revoke** it.

You cannot invite someone who is already a member, or who already has a pending invitation (resend that one). You cannot invite someone removed from the workspace: only Perfloop support can bring them back.

## Change a role

Pick Admin, Member, or Viewer in a person's **Role**. The change saves at once and applies from that person's next request. Changing an Admin's role asks first, because they lose Setup.

A workspace always keeps at least one Admin, so the only Admin's role cannot change. An Admin who leaves Admin can no longer change Setup.

## Remove someone

**Remove from workspace**, in the **⋯** menu at the end of a person's row, asks first. Once you confirm, the person loses access to the workspace at once: their browser, their coding agent's MCP connection, and their Slack conversations with Perfloop stop on their next request, and they cannot sign in to this workspace again. Their other workspaces are not affected. The last Admin cannot be removed.

Relay tokens and API keys belong to the workspace, not to a person, so removing someone revokes none of them. Revoke a relay token the person knew in Setup, under Telemetry. For another API key, write to Perfloop.

A removed person can come back to the workspace only through Perfloop support.

Also in this section: [The loop](https://perfloop.ai/docs/work), [Case states](https://perfloop.ai/docs/work/states), [Steering and learning](https://perfloop.ai/docs/work/steering), [Initiatives](https://perfloop.ai/docs/work/initiatives), [Autonomy and limits](https://perfloop.ai/docs/work/autonomy), and [The MCP server](https://perfloop.ai/docs/work/mcp).

Questions: [hello@perfloop.ai](mailto:hello@perfloop.ai?subject=Perfloop%20docs)