Business rules
Plain-language guardrails the assistant has to obey.
Rules are written the way you would say them to a new hire. Never quote a price without approval. Always use the client's legal entity name in contracts. Escalate anything involving PHI. Do not send external email after 6pm local. No policy language, no configuration syntax, no engineering ticket — you type the rule and it applies.
The boundaries are explicit, they are visible to everyone, and they are enforced consistently.
Rules apply organization-wide or per project, and they bind everything: chats, skills, apps, reports and forms all check them before acting. Some rules constrain tone and terminology so output stays on-brand; others are hard guardrails that stop an action and route it to a human instead. This is what makes it defensible to let AI touch real work — the boundaries are explicit, they are visible to everyone, and they are enforced consistently rather than depending on whoever happens to be reviewing that day.
Illustrative scenario data. Figures shown are product examples, not measured customer results or industry benchmarks.
See Business rules working in your own workspace
One shared workplace for your tools, your knowledge, and your team.