coderabbit-enterprise-rbac
Configure CodeRabbit enterprise access control, seat management, and organization policies. Use when managing who gets AI reviews, configuring organization-level defaults, or implementing access policies for CodeRabbit across teams. Trigger with phrases like "coderabbit SSO", "coderabbit RBAC", "coderabbit enterprise", "coderabbit roles", "coderabbit permissions", "coderabbit seats". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill coderabbit-enterprise-rbac --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# CodeRabbit Enterprise RBAC ## Overview Manage CodeRabbit AI code review access across an enterprise organization. CodeRabbit inherits repository permissions from your Git provider -- if a developer has write access to a repo and opens a PR, CodeRabbit reviews it. Enterprise controls focus on seat management, repository scoping, organization-level configuration, and review policy enforcement. ## Prerequisites - CodeRabbit Pro or Enterprise plan - GitHub Organization admin or GitLab Group owner role - CodeRabbit GitHub App installed on the organization - Access to CodeRabbit dashboard at app.coderabbit.ai ## Access Control Model ``` GitHub/GitLab Org Permissions │ ▼ ┌─────────────────────────┐ │ CodeRabbit GitHub App │ │ Repository Access: │ │ ├── All repositories │ ← Reviews every PR in the org │ └── Select repos only │ ← Reviews only selected repos └─────────┬───────────────┘ │ ▼ ┌─────────────────────────┐ │ Seat Assignment │ │ ├── Active committers │ ← Auto-assigns seats to PR authors │ └── Manual assignment │ ← Admin picks who gets seats └─────────┬───────────────┘ │ ▼ ┌─────────────────────────┐ │ .coderabbit.yaml │ │ ├── Org-level defaults │ ← .github repo │ └── Repo-level o
- Overview
- Prerequisites
- Access Control Model
- Instructions
- Step 1: Control Repository Access
- Step 2: Configure Seat Management
- Step 3: Set Organization-Level Defaults
- Step 4: Team-Specific Repository Overrides
- Step 5: Audit Review Activity
- Step 6: Enterprise SSO and Compliance
- Output
- Error Handling
- Resources
- Next Steps
set -euo pipefail
echo "=== CodeRabbit Org-Wide Review Audit ==="
echo "Organization: $ORG"
echo ""
List repos with CodeRabbit installed
echo "--- Repos with CodeRabbit ---"
for REPO in $(gh repo list "$ORG" --limit 50 --json name --jq '.[].name'); do
if [ "$INSTALLED" = "coderabbitai" ]; then
head -5 | xargs -I{} gh api "repos/$ORG/$REPO/pulls/{}/reviews" \
awk '{sum+=$1} END {print sum+0}')What does the coderabbit-enterprise-rbac skill do?
Configure CodeRabbit enterprise access control, seat management, and organization policies. Use when managing who gets AI reviews, configuring organization-level defaults, or implementing access policies for CodeRabbit across teams. Trigger with phrases like "coderabbit SSO", "coderabbit RBAC", "coderabbit enterprise", "coderabbit roles", "coderabbit permissions", "coderabbit seats". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill coderabbit-enterprise-rbac --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.