Single Team Setup
The Configuration
Section titled “The Configuration”{ "schema_version": "1.0.0", "organization": { "name": "Acme Corp", "id": "acme" }, "marketplaces": { "sandboxed-code-official": { "source": "github", "owner": "CCimen", "repo": "sandboxed-code-plugins" } }, "security": { "blocked_plugins": ["*experimental*", "*untrusted*"], "blocked_base_images": ["*:latest"], "allow_stdio_mcp": false }, "defaults": { "enabled_plugins": [ "scc-safety-net@sandboxed-code-official" ], "session": { "timeout_hours": 12, "auto_resume": true } }, "profiles": { "engineering": { "description": "Engineering team", "delegation": { "allow_project_overrides": true } } }}Key Features
Section titled “Key Features”| Feature | Effect |
|---|---|
| Safety Net | Git protection enabled for all users |
| Session Timeout | 12-hour sessions with auto-resume |
| Project Overrides | Developers can add .scc.yaml |
| Basic Security | Blocks experimental/untrusted plugins |
How to Use
Section titled “How to Use”-
Copy and customize
Update
organization.nameandorganization.id -
Validate
Terminal window scc org validate org-config.json -
Host the file
Terminal window # GitHub examplegit add org-config.jsongit commit -m "Add SCC config"git push -
Get the raw URL
https://raw.githubusercontent.com/acme/scc-config/main/org-config.json -
Distribute to developers
Terminal window scc setup --org https://raw.githubusercontent.com/acme/scc-config/main/org-config.json --team engineering
Verification
Section titled “Verification”# Confirm safety net is activescc audit plugins# Should show: scc-safety-net@sandboxed-code-official
# Check effective configscc config explain
# Test sessionscc start ~/projectNext Steps
Section titled “Next Steps”- Multi-Team Setup - Add more teams
- Strict Security - Tighter controls
- Safety Net Guide - Customize protection