Software Development
Scenario Team Admin
Use when administering a Scenario team from an agent through MCP: restricting which models a team or project can run (model access control, allowlist, blocklist), inviting or removing team and project members, changing roles, capping a member's Creative Unit spend, creating or deleting projects, auditing API keys and their roles or scopes, or attributing consumption per user or model. Keywords: governance, model control, consumption cap, spend limit, API key hygiene, team admin, enterprise.
- Publisher / source
- scenario-labs/skills (found on skills.sh)
- Upstream record
- scenario-labs/skills
- Version
- Version 3
- Published
- Publication review
- Approved for publication · recorded passed scan 2026-11-02
- Content fingerprint
dcbab831a3de93af60723d7886a475f4885ac6d099d5de5bf099f68738e3e30c