Platform Administration
The Roster platform is the web UI for operating a deployment after the core project, participant, delegation, directory, and resolve model is in place.
Platform administration covers four areas:
| Area | Pages |
|---|---|
| Operations | Dashboard, Resolve Requests |
| Identity and access | Team Members, AI Agents, Service Accounts, API Keys, First Login |
| Configuration | Settings |
| Observability | Model Runs, Audit Events |
Most administration pages require the admin platform role. The Dashboard and
Resolve Requests pages are also useful for project owners and members, but the
visible data follows the user’s role and project access.
Access Model
Section titled “Access Model”- Admins can manage platform settings, identities, API keys, audit events, model runs, connectors, and all project data.
- Project owners can manage owned projects, participants, labels, delegations, and related resolve history.
- Members can sign in, use visible project context, and inspect their own resolve activity.
API keys and MCP/OAuth tokens never bypass these role and resource rules. See Authorization for the full access model.
API Coverage
Section titled “API Coverage”The REST API currently focuses on business-core data and resolve operations: Projects, Participants, Directory Records, Labels, Delegations, Resolve, and Resolve Requests.
The platform administration screens for identities, API keys, audit events, model runs, connectors, and settings do not currently have documented REST endpoint groups. Manage those areas through the web platform unless your deployment has a custom integration layer.