Concepts
Roster models workflow routing around projects, participants, and delegations. These concepts stay separate from authentication accounts and provider records so the platform can resolve business responsibility without becoming an identity provider, HRIS, or BPM system.
Concept Map
Section titled “Concept Map”| Concept | Purpose |
|---|---|
| Project | Logical container for a process, enterprise project, customer workflow, or domain boundary. |
| Participant | Business role that can handle workflow action. |
| Delegation | Runtime coverage overlay from one active user to another. |
| Directory record | Materialized user, group, organization unit, role, or external email from an external provider. |
| Label | Reusable global category for grouping participants and resolve request history. |
| Identity | Roster actor used for authorization, ownership, API keys, and audit. |
How They Work Together
Section titled “How They Work Together”- A project defines the routing context.
- Participants describe the business roles inside that context.
- Labels and metadata make participant matching deterministic.
- Directory records attach users or groups to participants.
- Delegations add temporary or open-ended coverage without changing upstream provider data.
When a client calls resolve, Roster selects participants first, then returns
the users who are currently able to act for those participants.