Admin
Permissions
How GitHub permissions map to CarbonRunner access.
CarbonRunner doesn't create a new permission model, it works directly with the roles and access levels you already have in GitHub. Team members sign in with their GitHub accounts, and CarbonRunner automatically recognises your organisation's structure.
Basics#
Here’s how GitHub access translates inside CarbonRunner:
- Org Admins have full control: they can adjust organisation-wide settings, manage billing, and access every repository.
- Repo Admin / Write / Read permissions flow through exactly as in GitHub, shaping what data a user can see and what actions they can take for each repository.
- No GitHub access = no CarbonRunner access. If someone can’t view a repo in GitHub, they won't see it in CarbonRunner either.
By design, CarbonRunner never grants more access than GitHub itself — it simply mirrors what's already there.
Permissions#
| Feature | Org Admin | Repo Admin | Repo Write | Repo Read | No Access |
|---|---|---|---|---|---|
| Organization Management | |||||
| View organization settings | ✓ | ✓ | ✓ | ✓ | ✗ |
| Modify organization settings (caching, ssh, etc) | ✓ | ✗ | ✗ | ✗ | ✗ |
| Access billing and payments | ✓ | ✗ | ✗ | ✗ | ✗ |
| Analytics & Monitoring | |||||
| View usage, runs, logs, and analytics | ✓ | ✓ | ✓ | ✓ | ✗ |
| Cache & Sticky Disk | |||||
| View entries and metrics | ✓ | ✓ | ✓ | ✓ | ✗ |
| Delete entries | ✓ | ✓ | ✓ | ✗ | ✗ |
| Repository Configuration | |||||
| Configure repository settings (PR comments, preferences) | ✓ | ✓ | ✗ | ✗ | ✗ |
| Use migration wizard | ✓ | ✓ | ✓ | ✗ | ✗ |