domains / families / media / scenario-team-admin

scenario-team-admin

separate

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.

When to use

• restricting which models a team or project can run
• 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
• attributing consumption per user or model

When not to use

• switching model access mode from blocklist to allowlist

Skill page

Source