Business rules & validations
A consolidated reference of the rules Copilot enforces, useful during blueprint discussions when a customer asks "what guardrails are built in?"
| Rule | Behaviour |
|---|---|
| Confirmation before changes | Create, update, and submit always produce a draft and wait for explicit user confirmation. |
| Read-only advanced queries | Advanced data queries can only read. Any attempt to insert, update, delete, or alter is rejected. |
| Balanced journal entries | Total debits must equal total credits within 0.01, with at least two lines. |
| Duplicate protection | Creating a customer, supplier, or item checks for an existing match and warns before proceeding. |
| Submitted-only analytics | Revenue, margin, and outstanding figures count submitted transactions only. Credit notes are excluded from revenue. |
| Scheduled-task timing | Once needs a date; Weekly needs a weekday; Monthly day must be 1 to 28. |
| Fuzzy matching | Customer, supplier, item, lead, asset, project, task, and issue lookups match in stages and offer close matches when unsure. |
| Sensitive data excluded | Employee lookups omit bank and sensitive personal fields; passwords and tokens are never returned. |
| List size caps | Everyday lists default to 20 rows and cap at 100; report tables show up to 50 to 100 rows. |
| Self-service defaults | HR lookups default to the requesting user's own record unless a permitted user names someone else. |
Last updated 8 hours ago
Was this helpful?