Members, roles, and permissions
Understand what OWNER, ADMIN, DEVELOPER, QA, and VIEWER can each do in your BugMojo workspace.
Every person and AI agent in your workspace holds one role. That role decides what they can see and change across your Companies, Projects, Boards, and Issues. This reference lists BugMojo's five roles and the permissions each one grants.
OWNER
The OWNER has full control of the workspace. There is one OWNER at a time, set when the workspace is created. An OWNER can do everything an ADMIN can, plus manage the plan and billing and transfer ownership to another member. Use Set up your workspace to review workspace-level settings.
ADMIN
ADMIN is full administrative access without billing ownership. Admins can invite or remove members and AI agents, change roles, create Companies and Projects, and edit workspace settings. Grant ADMIN to team leads who need to manage people and structure. See Invite your team and agents.
DEVELOPER and QA
DEVELOPER and QA are the working roles. Both can open bugs, watch session replays, read console and network logs, comment, change status and priority, apply labels, and assign bugs to a teammate or an AI agent. They cannot manage members, roles, or billing. The two roles share the same permissions today. The distinction records who owns a bug at each stage of your workflow.
VIEWER
VIEWER is read-only. A viewer can open the bug detail page, watch replays, and read logs and repro steps, but cannot edit, assign, comment, or change status. Use it for stakeholders who need visibility without touching the workflow.
Common questions
Can a workspace have more than one OWNER?
There is a single OWNER at a time, but you can transfer ownership to another member. Grant ADMIN to anyone else who needs full administrative control.
Which roles can invite new members?
OWNER and ADMIN can invite people and AI agents, change roles, and manage billing. DEVELOPER, QA, and VIEWER cannot manage members.
What can a VIEWER do?
A VIEWER has read-only access. They can open bugs, watch session replays, and read console and network logs, but cannot edit, assign, or comment.
Related articles
- Invite your team (and your AI agents)Add teammates by email with the right role, and learn how AI agents work as assignees too.
- Set up your workspaceCreate a company, a project, and a board so your team has a home for every bug report.
- Assign bugs to teammates or to AI agentsRoute any bug to the right owner (a teammate or an AI coding agent) from the same assignee control.
- Agent access, tokens, and the security modelUnderstand how an AI agent's access is scoped, what it inherits from you, and the guardrails that keep it in bounds.

