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. On Pro and Enterprise, an Admin can also set up single sign-on, so people at your company's domain sign in through your identity provider.

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, including the review comments on each case and who wrote them, 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. 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.

Email

Inbox notices and weekly reports use the sender name Perfloop.

Email can name repos, Case or PR titles, the action and measured results with their proof level. It carries no code, diffs, file paths or finding text. An Admin can turn on Minimal email in Setup, under Workspace, Email. This applies to everyone in the workspace: Inbox notices name only the kind of work, and any weekly report keeps its counts and settled Usage without repos, titles or measured results. Minimal email does not turn email on for anyone.

An Inbox email or Slack notice that asks to open a pull request or handle PR feedback offers Don't ask again for this repo. It opens that request in Inbox, where an Admin can confirm that Perfloop acts without asking next time for that repository. The request itself still waits for a decision. A summary email offers Set up automatic work, which opens Setup, Automatic work.

Inbox email starts on for new users. Existing users keep their saved choice. Email goes only to your verified sign-in address, and turning it off leaves the work in Inbox.

An Inbox email's unsubscribe applies only to that workspace and the address used when it was sent. Other workspaces and weekly reports are unchanged. A weekly email's unsubscribe stops weekly reports to that address across all workspaces. Saved email choices do not reverse that unsubscribe. Inbox notices stay separate.

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.

In Setup, 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. Setup cannot remove the last Admin.

If your identity provider removes or demotes every Admin, contact Perfloop to restore Admin control with a replacement your organization authorizes. Work already approved in the workspace continues.

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.

Single sign-on

Single sign-on is included on Pro and Enterprise. An Admin sets it up on Setup's Members page, under Single sign-on. Choose Verify a domain to prove your company owns its email domain, then Connect an identity provider to connect yours, such as Okta or Microsoft Entra ID. Each one opens a setup page in the same tab; its link works for 5 minutes, and the page brings you back to Setup when you finish.

Once a connection is active, people at a verified domain sign in through your identity provider. From then on, sign-in through the identity provider is required for that domain. Each new person still needs an invitation from Members, and their role changes there.

Removing someone still ends their access at once. A removed person cannot come back through single sign-on; only Perfloop support can restore them.

Also in this section: Quickstart, Performance, Bugs, Security, The loop, Case states, Pull requests, Steering and learning, Initiatives, Autonomy and limits, The MCP server, and Events.

Questions: hello@perfloop.ai