Playground
Playground is the web UI for testing roster.resolve behavior from the
platform before the same question is used through MCP, REST, or CLI automation.
Each run creates a normal resolve request with the roster_playground surface,
so the result is visible in Resolve Requests
according to the current history and PII settings.
Access
Section titled “Access”Playground access requires an admin or project_owner platform role.
Admins can run against all resolvable live and test projects. Project owners can run against live projects they can read and test projects they own. Members cannot use Playground.
Query Scope
Section titled “Query Scope”The form accepts a natural-language resolve query up to 1,000 characters. Queries use the same resolver and model provider configuration as other resolve surfaces.
Choose a mode before running:
| Mode | Scope options |
|---|---|
live | All live projects, or one live project visible to the actor. |
test | All test projects the actor can resolve, or one test project the actor can resolve. |
draft and archived projects are excluded from resolve runs. Use test mode
for pre-production validation, sample data, and project-owner checks that should
not be treated as production workflow traffic.
Result Detail
Section titled “Result Detail”After a run, Playground shows:
- the resolved answer and raw JSON response
- matched participants
- resolved users
- caveats returned by the resolver
- request status, resolution status, confidence, project, latency, timestamps, provider, model, effort, and request identifiers
Use the JSON response when comparing platform output with REST, MCP, or CLI clients. Use the participants, users, and caveats tabs to verify that project data, labels, directory associations, and delegations are being applied as expected.
History
Section titled “History”Playground runs are stored in resolve history and can be reviewed from
Resolve Requests. The history entry uses the
Roster Playground surface label, the selected mode, and the actor identity
from the signed-in user.
If resolve-request PII settings redact query text, actor details, credential details, or result fields, Playground history follows those settings the same way API, MCP, and CLI resolve history does.