A Role Assistant is a human-owned, role-scoped assistant that helps employees complete recurring business work through governed capabilities and trusted business context — not a generic chatbot, RPA bot, or autonomous service account.
End users see role-specific names: Sales Assistant, Project Assistant, Finance Assistant. Admins manage Role Assistants per business role and Activate for AI when a role is ready.
Architecture note (developers): The platform compiles a Digital Worker (
systemKind: digitalWorker) per role from published metadata. Customer UX never leads with "Digital Worker." See Platform architecture and Role Assistants pillar.
Why it matters
Role Assistants translate business roles (Sales Manager, Project Manager, Customer Success Manager) into AI-assisted work inside Operational Trust and Enterprise Knowledge. They reduce prompt chaos while keeping humans in authority for approvals and policy.
Enterprises adopt Role Assistants when they want repeatable assistance tied to roles and outcomes, not experimental chat with system access.
How it works
Business Role → Role Assistant → Task → Governed Capability → Outcome → Evidence
The active role is the operating boundary — it defines visible data, allowed capabilities, approvals, and audit context. The assistant persona (e.g. "Sales Assistant") is UX; the role is governance.
Assistants are derived from:
- Enterprise Knowledge — business metadata and relationships
- Governed capabilities — certified business actions integrators published
- Operational Trust — dimensions, policy, certification
- Evidence Fabrix — prior task outcomes and learning signals
Integrators make systems AI-ready in Build AI-ready systems; operators run assistants within that certified scope.
What a Role Assistant is not
| Not this | Why |
|---|---|
| Free-form agent with API keys | No structural trust path |
| Prompt-orchestration-first automation | Governance bolted on too late |
| Authority expansion at higher skill | Promotion improves visibility, not permissions |
| Replacement for enterprise IAM | Consumes roles; does not redefine them |
Limits
- Role Assistant behavior depends on certified capabilities, tenant policy, and channel configuration — not every CRM or ERP action is available on day one.
- This page describes the product model; channel-specific setup lives in Assistant channels and How role assistants are created.
Example
A Sales Manager opens a weekly pipeline review task. The Sales Assistant uses in-scope deals, customer context, and prior review evidence — then requests capabilities to draft follow-ups. It does not silently update CRM records outside certified capabilities.