Roles and permissions

1Built-in roles

Six roles come ready to use. They can't be edited, but you can copy one into a custom role.

• Owner: everything. Only owners change the plan, cancel, buy packs, delete a project or the workspace, and make or change owners. Deleting a project or the workspace needs a code emailed to the owner, plus the authenticator or backup code when two-factor is on.
• Admin: everything else, including projects, keys, alerts, integrations, monitors, status pages, on-call, members, sign-in rules and guest access.
• Developer: sees every technical area and personal data, works on issues and bug reports, acknowledges incidents; can't change settings, alerts or members.
• Service desk agent: only bug reports and the service desk: view, triage, reply to reporters (with their contact details), see each report's screenshots, recordings, voice notes, attached files and console and network details, and the service desk report. Nothing else: no issues, events, logs, session replays or security data.
• Viewer: read-only on issues, logs, Pulse, workflows, uptime, on-call and the other technical areas, with personal data hidden; no session replays and no settings.
• Billing: only Billing and Usage, including billing details and invoices.

2Custom roles

Members, Roles, New role: start from a built-in role, name it, then tick View, Edit or Manage for each area and the extra rights (run AI fixes, reply to reporters, see report screenshots and recordings, respond to on-call). Edit includes View, and Manage includes both. A role in use can't be deleted until its members have another role.

3Project access

For each member choose All projects or only some projects. Someone limited to some projects sees issues, events, logs, Pulse, replays, bug reports, releases, AI fixes and live counts for those projects only, everywhere in the dashboard. A project created later is visible only to people with All projects. Owners always see every project.

4Sensitive data

Personal data is a separate permission with a warning when you turn it on. Without it, Blipit removes these before the page is sent to the browser:

• Request bodies, headers and cookies, the affected user's email and IP, breadcrumbs and local variables in errors
• Log message bodies and attribute values, span details and query strings in traces
• Session replays
• Reporter name and email on bug reports, screenshots, recordings and voice notes (agents who can reply still see the reporter's contact; Service desk agents and roles with See report screenshots and recordings still see the screenshots, recordings, voice notes and console and network details of reports in their projects, never the session replay)
• The account and IP address on security issues

5Preview as this role

On Members, Preview as this role shows the menu and the list of pages a role and project choice would see, and which personal data it would see. It is a preview only: nothing is opened or changed as that person.

Good to know

• Developer, Viewer and Billing are on every plan with more than one seat (Solo and up). Service desk agent is on Team and Scale. Custom roles and project access are on Scale.
• Role, project access and custom role changes are recorded in the audit log with who made them, the old value and the new one.
• A workspace always keeps at least one owner: the last owner can't be removed or given another role.
• If a workspace moves to a smaller plan, people keep their current role and project limits; new ones can't be given until the plan allows them.