Stop hard-coding approvers into every workflow.
Use Roster to resolve the right user, group, role, or delegate at runtime — then let your existing workflow platform deliver and manage the task.
Build routing logic once and reuse it across automation systems, agentic workflows, and business processes.
Workflow engines know what happens next — not always who should do it
Automation platforms are good at moving data, calling applications, pausing for approvals, assigning tasks, sending notifications, and managing workflow state.
But participant selection is often reduced to a fixed email address, a manually selected manager, a group name, a condition tree, a copied organizational table, or a custom directory lookup.
That logic becomes stale when someone changes roles, a team reorganizes, a project has a different owner, an approver is absent, responsibility depends on region or threshold, or several workflows need the same routing rule.
Roster separates participant resolution from workflow orchestration.
Resolve before you assign
A workflow sends Roster a business-language question:
What Roster evaluates
- Project context
- Participant responsibilities
- Labels and metadata
- Users and groups
- Current memberships
- Active delegations
- Caller authorization
Use Roster with the tools you already operate
Call Resolve from n8n, Workato, Power Automate, Camunda, ServiceNow, WorkflowGen, or a custom application through an HTTP step.
Give an agent-driven workflow natural-language access to Resolve and exact participant tools.
Use participant resolution in scheduled scripts, jobs, and operational automation.
Let project owners model responsibilities without editing every workflow.
Common workflow use cases
Resolve the appropriate procurement, finance, security, or legal approver based on project and request context.
Route work to the current account owner, implementation lead, regional team, or delegated contact.
Determine which participant should review a policy exception, access request, vendor, or data-processing action.
Use directory or Workday context to route HR, payroll, management, or employee-service requests.
Resolve release approvers, service owners, change reviewers, and escalation contacts.
Let an agent determine which human should review or approve before it executes a sensitive action.
Delegation without rebuilding the workflow
Roster models delegation as a runtime coverage layer. When an active participant delegates responsibility, the workflow definition does not change, the source directory does not need to be modified, and the participant responsibility remains stable.
Roster routes to the active delegate, and the resolution remains attributable and reviewable — especially useful for leave, temporary coverage, regional backup, and planned operational handoff.