Services

A Service is the unit of value buyers recognize: the repeatable thing your team delivers. Examples: an ancillary-benefits RFP, monthly close, contract review, claims triage.

What a service contains

• An ordered pipeline of Processes (stages owned by teams)
• Subject / engagement types and shared context
• Default stakeholder grant templates
• A service drive — the durable filesystem behind every workspace for that service
• A knowledge base that compounds across runs

Access

Services are born private to their creator. Opening one to the organization is an explicit grant on the service's Access tab. Org admins hold governance capabilities; they still use audited grants to enter someone else's private drive.

How operators see services

Executives and operators live on the service board: engagements across stages. Builders live in the process definitions. Verifiers mostly live in the Inbox and only drill into a service when context demands it.

See also: Processes & skills, Console boards.