Manage who acts in your workflows — without opening an IT ticket.
Define project responsibilities, connect the right users and groups, and manage temporary delegations from one governed platform.
Give agents and workflows current answers while keeping operational ownership close to the teams that understand the work.
Responsibilities stay. People change. The workflow doesn't care.
A Roster project separates a responsibility from the individual doing it right now. The ember rail on the left is the responsibility — that's what workflows call. The card on the right is the person, group, or account currently assigned. Swap the card, keep the rail.
Five layers, one operational model
Each layer answers a different question about the work. Together they describe how responsibility flows through a project without hard-coding names anywhere.
A clear operating boundary for a process, customer workflow, business domain, or enterprise initiative.
The business responsibilities that can act inside the project — always described as roles, never as names.
The users, groups, roles, org units, agents, service accounts, or external contacts currently filling each participant.
Temporary or ongoing coverage layered on top of a participant — no directory changes required.
Reusable categories and business-specific attributes that let workflows disambiguate by region, threshold, or context.
Central IT owns access. Project owners own the work.
Two different questions, two different surfaces. Roster gives each side the reach it actually needs — and stops there.
Infrastructure, identity, and platform reach
Directory connectors, model providers, global identity administration, and platform-wide configuration stay with the teams responsible for them.
- Configure directory and model connectors
- Manage global roles and platform policy
- Rotate credentials and audit access
- Approve new project creation
Participants, members, and operational context
Authorized project owners maintain the responsibilities they understand — inside the projects they own, and nowhere else.
- Add or replace project participants and members
- Set project-specific metadata and labels
- Delegate a responsibility during coverage
- Test a Resolve query before going live
Define the model once. Every connected agent gets the answer.
You maintain the project, its participants, and their members. Agents and workflows ask business-language questions. Roster resolves the current participant — including any active delegation — without editing a single automation.
Common project-owner actions
The everyday moves that used to require an IT ticket now sit in the project owner's hands — with the same audit trail as any other platform change.