Projects and Participants

Projects and participants form the core Roster data model.

Projects

A project is a logical container. It can map to a business process, enterprise project, customer workflow, regional operation, or another domain boundary.

Project owners can manage the projects they own. Admins can manage projects globally.

Participants

A participant is a business role that can handle workflow action. It should be named after responsibility, not after a single person.

Good participant names:

• Helios Finance Approvers
• Supplier Onboarding Approval Reviewers
• EMEA Legal Reviewers

Participants can include:

• description
• labels
• typed metadata
• direct user associations
• group associations
• org-unit or role associations
• external email associations

Labels

Labels are global routing tags. The resolver uses exact labels returned from the label set and should not invent new labels.

Use labels for broad routing dimensions:

• Finance
• Procurement
• Legal
• Renewal
• Vendor

Metadata

Use metadata for structured constraints that need exact or ordered matching:

{
  "approval_limit_eur": 75000,
  "region": "EMEA",
  "review_after": "2026-06-01T00:00:00.000Z"
}

Metadata filter operators are eq, ne, gt, gte, lt, and lte. Ordered comparisons use numbers when both sides are numeric, otherwise parseable datetime strings.

Member Associations

Associate participants to directory users or groups. For exact member management, search the directory first, then add the returned directory entry to the participant.

Participant member listings return direct associations only. They do not expand users inside associated groups.