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.
The people closest to the process know who should act
Central administrators can manage infrastructure and access, but they do not always know who approves a specific project, which team handles a customer, who owns a regional process, which reviewer covers a particular risk, who should act during an absence, or when a responsibility has changed.
Roster lets authorized project owners maintain that operational context directly.
Model responsibility around the way work happens
Create a clear operating boundary for a process, customer workflow, business domain, or enterprise initiative — Atlas vendor onboarding, Acme customer implementation, European procurement, and so on.
Define the business responsibilities that can act in the project: project owner, security reviewer, finance approver, release manager, customer escalation owner, regional operations contact.
Associate participants with users, groups, roles, organizational units, agents, service accounts, or external contacts.
Add temporary or ongoing coverage when the normal participant is unavailable.
Describe responsibilities using reusable categories and business-specific attributes.
From project knowledge to an answer agents can use
You define the project, the participant, its members, and its metadata. An agent asks Roster a business-language question, and Roster resolves the relevant participant and active members — including any applicable delegation.
Decentralized control with governed boundaries
Project owners can manage the projects and participants they are authorized to own. They do not need global access to every Roster project, platform configuration, other business domains, every directory record, model-provider credentials, or global identity administration.
This lets operational teams manage their routing context without turning every change into a central-administration request.
Keep responsibilities stable while people change
A good participant model separates the responsibility from the individual. Instead of defining “Approver = Jordan Smith”, define “Participant = Regional Procurement Approver”, then associate the current user or group.
When people move or coverage changes, update the membership or delegation without rewriting every workflow that uses the participant.
Common project-owner workflows
- Add or replace a project approver
- Associate a directory group with a responsibility
- Add a project-specific external contact
- Set regional or threshold metadata
- Delegate responsibility during leave
- Test a Resolve query before going live
- Review previous Resolve requests
- Archive a completed project
- Manage a customer-specific routing model