Skip to main content
Control who can configure, who can see, and what stays private. CodeRabbit Agent for Slack uses both Slack-native admin status and CodeRabbit-specific roles. Everyone in the workspace can sign in, but elevated access is required for workspace-wide settings and some web app surfaces.

Global, automation and scope admins

Global admins

Global admins are the people who can manage the workspace as a whole. They include:
  • Native Slack admins
  • Slack workspace owners and primary owners
  • Users with the CodeRabbit cr_admin override

Automation admins

Automation admins are CodeRabbit Agent users who can help manage automations without receiving full workspace-admin access. CodeRabbit admins, members with the Admin role, assign the Automation admin role from the members list under Workspace management in the CodeRabbit web app. In the web app, Automation admins can manage other members’ automations created on the Automations page and automations in public channels, but not private-channel or DM automations. See Permissions. When automation creation is limited to Automation admins, Automation admins can also open the automation admin views in Slack and manage same-workspace automations there. They cannot manage the full workspace, reset workspace connections, manage users, or administer scopes unless they also have another role that grants those permissions. For who can create automations, see Who can create automations.

Scope admins

admins have read-only access to the named scopes assigned to them. They can’t edit scopes, Slack assignments, spend limits, or connections, and they can’t manage the full workspace or admin-only web surfaces such as Sandboxes or workspace user management. Like every member, they can use the Automations page and manage the automations they created; see Permissions.
Scope admins can’t see the Base Scope. Scopes, assignments, and spend limits are managed by organization admins.

What each role can do

Global admins have full access to all workspace actions and settings. Every action listed in the table below is always available to global admins regardless of any other configuration.

Account Settings and account removal

The Account Settings page is visible only to workspace (global) admins. Account Settings includes workspace-wide controls such as resetting the GitHub connection and permanently removing the CodeRabbit Agent account.
Only workspace admins can access the Danger Zone controls in Account Settings, including Delete account. If you need to remove the account, sign in as a workspace admin before opening that page.

Workspace activity visibility

Usage visibility is role-aware.

Knowledge Base privacy

Knowledge follows Slack privacy boundaries. Agent-authored Skills follow these same public and private conversation boundaries, so skills created in private channels, DMs, or group DMs stay isolated to that conversation. Private knowledge can reference shared knowledge, but it should not be silently treated as shared workspace memory.

Shared sandbox access

CodeRabbit Agent currently uses a shared workspace sandbox model rather than a private sandbox for every individual user. That makes workspace governance important:
  • Configuration changes affect the workspace environment
  • Saved state can be reused across runs
  • Admins should be deliberate about who can manage sandbox settings

Good rollout practices

  • Keep the Base Scope’s connections conservative at first
  • Assign narrower scopes only where needed
  • Review usage visibility before wider rollout
  • Treat private channels and DM knowledge as materially different from shared workspace memory

What’s next

Slack permissions

Review the Slack app and OAuth permissions CodeRabbit Agent requests and why they are needed.

Usage

See what activity global admins, scope admins, and other members can inspect after rollout.

Sandboxes

Understand the shared sandbox model and how workspace-level execution state is managed.