Guides

Use these guides to model workflow routing data and operate the platform. For foundational definitions, start with Concepts, Integration, and Authentication.

Core Concepts

• Project: logical container for participants. A project can represent a process, enterprise project, or domain-specific workflow.
• Participant: business role that can handle workflow action. Participants can have labels, metadata, and associations to users, groups, org units, roles, or external emails.
• Delegation: runtime overlay that lets a user delegate participant membership to another active user.
• Provider connector: integration that refreshes directory records from an external source into the Roster database.
• Resolve request: natural-language routing question processed through MCP or REST.
• PII controls: platform settings that minimize stored and returned personal data across resolve, audit, directory, diagnostics, logs, and journals.

Guides

• Projects and participants
• Delegations
• Provider connectors
• Privacy and data retention
• Deployment

Typical Flow

1. Create a project.
2. Add labels that represent routing dimensions such as department, region, function, or review type.
3. Create participants with descriptions and metadata that define their authority.
4. Associate users or groups through directory records.
5. Configure privacy and retention settings for the data you intend to store.
6. Use MCP, REST, CLI, or the platform to resolve routing questions.