Organization
Roles, invitations, environments, API tokens and the audit log of an organization.
Projects, members, alerts and integrations belong to an organization. You can belong to several; Settings → General → New organization creates another, with you as its owner.
Roles
| Role | Can |
|---|---|
| Member | See every project, its telemetry, releases and alerts. Change error status and create issues from errors. Choose which alerts email them. |
| Admin | Everything a member can, plus: create and edit projects, releases and alerts; connect integrations; create and revoke API tokens; turn on the MCP server; hide environments; edit the organization’s name, slug and logo; invite members and change roles. |
| Owner | Everything an admin can, plus: invite owners and change or remove them, manage webhooks, read the audit log and delete the organization. |
An organization can have several owners. The only owner can’t leave.
Members and invitations
Owners and admins invite people under Settings → Members → Invite with an email and a role. OpenPerf emails them a link.
- An invitation expires after 48 hours. Send email again sends it again and restarts the 48 hours.
- Copy invitation link copies the link to share yourself. Cancel invitation stops it from working.
- The link works only for the invited email. Signed in with another one, use Sign in with another email.
- Someone without an organization also sees their pending invitations when they sign in.
To change a role, pick it in the member’s row. Remove from organization ends their access at once. Leave organization, on your own row or under Settings → General, does the same for you; returning takes a new invitation.
Environments
An environment comes from the SDK’s environment option, sent as deployment.environment.name (see SDK).
Settings → Environments lists the environments reported in the last 30 days. Owners and admins turn one off to hide it, for everyone in the organization, from the Environment filter and the alert form. Its data stays, and still counts when no environment is selected.
API tokens
API tokens authenticate the openperf CLI and MCP clients that take a header.
- Under Settings → API, an owner or admin clicks New token and names it.
- Copy the token. It starts with
opt_and isn’t shown again.
A token acts for the organization, with full access to every project, and doesn’t expire. The list shows who created each token and when it was last used. Revoke stops it at once.
Audit log
Owners see Settings → Audit log: who changed what, from the app, the API and MCP. Events are kept for 90 days.
It records sign-ins and failed sign-ins, sessions, passkeys, API tokens, invitations and roles, organization and MCP settings, projects, environments, source maps, releases, alerts, integrations, webhooks, code mappings, error status changes and MCP tool calls.
Filter by Action, Source (App, API, MCP, Integration, System) and Time range, from the last 24 hours to 90 days. The history button on a row in Members or API tokens opens the log for that person or token. Open an event for its details.