Skip to content
This page was generated and translated with the assistance of AI. If you spot any inaccuracies, feel free to help improve it. Edit on GitHub

Members & Permissions

OpenPR uses role-based access control (RBAC) scoped to workspaces. Each workspace member has a role that determines their permissions.

Roles

RoleDescriptionPermissions
OwnerWorkspace creator or promoted ownerFull access: delete workspace, manage all settings, promote/demote members
AdminWorkspace administratorManage projects, members (except owners), settings, governance config
MemberRegular team memberCreate and manage issues, comments, labels; participate in governance

Inviting Members

Navigate to Workspace Settings > Members > Invite:

  1. Enter the user's email address.
  2. Select a role (Owner, Admin, or Member).
  3. Click Invite.

The invited user must have an OpenPR account. If they don't have one, they need to register first.

Managing Members

From the members list, you can:

  • Change role -- Promote or demote members (admins cannot change owner roles).
  • Remove -- Remove a member from the workspace.

User Types

OpenPR supports two entity types:

TypeDescriptionCreated By
humanRegular human usersUser registration
botBot/AI accountsBot token creation

Bot users are created automatically when a bot token is generated. They appear in activity feeds and audit logs with their display name.

Bot Tokens

Bot tokens enable AI assistants and external tools to authenticate with the MCP server and API. Each token:

  • Has an opr_ prefix.
  • Is scoped to one workspace.
  • Creates a corresponding bot_mcp user entity.
  • Supports all read/write operations available to workspace members.

Creating a Bot Token

Navigate to Workspace Settings > Bot Tokens > Create:

  1. Enter a display name (e.g., "Claude Assistant").
  2. Click Create.
  3. Copy the token immediately -- it will not be shown again.

Using Bot Tokens

Bot tokens are used in MCP server configuration:

bash
# Environment variable
OPENPR_BOT_TOKEN=opr_your_token_here

Or in API requests:

bash
curl -H "Authorization: Bearer opr_your_token_here" \
  http://localhost:8080/api/workspaces/<workspace_id>/projects

API Reference

bash
# List workspace members
curl -H "Authorization: Bearer <token>" \
  http://localhost:8080/api/workspaces/<workspace_id>/members

# List bot tokens
curl -H "Authorization: Bearer <token>" \
  http://localhost:8080/api/workspaces/<workspace_id>/bots

MCP Tools

ToolDescription
members.listList all workspace members and their roles

Next Steps

Released under the Apache-2.0 License.