Team Config Wizard
The team config wizard helps you create and edit team-config.json files for team-managed teams.
Quick Start
Section titled “Quick Start”/scc-wizard:teamWhen Do I Need a Team Config?
Section titled “When Do I Need a Team Config?”You Need a Team Config When:
Section titled “You Need a Team Config When:”- The org config has a
config_sourceentry for your team - You want to independently manage your team’s plugin list
You Don’t Need a Team Config When:
Section titled “You Don’t Need a Team Config When:”- Your team is org-managed (no
config_source) - The org admin manages your plugins in
profiles.<team>.additional_plugins
Creating a Team Config
Section titled “Creating a Team Config”- Run
/scc-wizard:team - Select “Create new team config”
- Provide team context (name, available marketplaces)
- Add plugins to enable
- Optionally add plugins to disable
- Add team marketplaces (if trusted by org)
- Review and save
Example Output
Section titled “Example Output”{ "$schema": "https://scc-cli.dev/schemas/team-config.v1.json", "schema_version": "1.0.0", "enabled_plugins": [ "changelog-generator@sandboxed-code-official", "code-review@sandboxed-code-official" ], "disabled_plugins": [ "legacy-tool@*" ]}Plugin References
Section titled “Plugin References”Always use the plugin@marketplace format:
{ "enabled_plugins": [ "scc-safety-net@sandboxed-code-official", "java-analyzer@internal" ]}Disabling Plugins
Section titled “Disabling Plugins”Use disabled_plugins to remove plugins from org defaults:
{ "disabled_plugins": [ "legacy-tool@*", "*-deprecated" ]}This removes matching plugins from the org’s defaults.enabled_plugins.
Team Marketplaces
Section titled “Team Marketplaces”If your org grants marketplace trust (trust.allow_additional_marketplaces: true), you can define team-specific marketplaces:
{ "marketplaces": { "team-plugins": { "source": "github", "owner": "your-org", "repo": "team-plugins" } }, "enabled_plugins": [ "custom-tool@team-plugins" ]}Trust Settings in Org Config
Section titled “Trust Settings in Org Config”For a team to add marketplaces, the org must grant trust:
{ "profiles": { "ai-team": { "config_source": { ... }, "trust": { "inherit_org_marketplaces": true, "allow_additional_marketplaces": true, "marketplace_source_patterns": ["https://github.com/your-org/*"] } } }}Edit Mode
Section titled “Edit Mode”To update an existing team config:
- Run
/scc-wizard:team - Select “Edit existing team config”
- Provide the file path
- Choose what to modify:
- Add/remove enabled plugins
- Add/remove disabled patterns
- Add/remove/edit marketplaces
- Save changes
Team-managed Checklist
Section titled “Team-managed Checklist”After creating your team config, complete this checklist:
- Host the file at the path specified in org config’s
config_source - Ensure URL is accessible (for private repos, configure auth)
- Verify org config has matching
config_sourceentry - Test with:
scc team validate --file path/to/team-config.json
Common Issues
Section titled “Common Issues””Changes not taking effect”
Section titled “”Changes not taking effect””- Is your team actually team-managed? Check for
config_sourcein org config - Is the
config_sourceURL correct and accessible? - Has the cache expired? Run
scc update --force - Are plugins formatted correctly (
plugin@marketplace)? - Does the referenced marketplace exist?
”Cannot add marketplaces”
Section titled “”Cannot add marketplaces””Your org profile has allow_additional_marketplaces: false. Contact your org admin to request marketplace trust.
”Plugin denied at runtime”
Section titled “”Plugin denied at runtime””The plugin is probably not in the org’s allowlist. Check:
defaults.allowed_pluginspatternsdelegation.teams.allow_additional_pluginslist