Business rules & logic
A consolidated reference to the rules, validations, and calculation logic that govern the gateway. Useful for blueprint discussions.
Access and permission rules
-
A user needs an assistant role and the Assistant Access flag enabled.
-
Tools run under the user's own permissions. The assistant never escalates access.
-
A tool is available only if its pack is on, the tool is enabled, and the user's role is allowed.
-
The read-only query tool and the analysis sandbox are restricted to administrators or trusted roles.
Document validation rules
-
Required fields must be provided, or creation fails with a clear message.
-
Unique fields reject duplicates.
-
Submittable documents are created as drafts unless submission is explicitly requested.
-
Submitted documents cannot be edited directly. They move through approval actions instead.
-
Calculated and read-only fields cannot be set by hand; the system computes them.
-
Records with links to other records cannot be deleted unless forced, and submitted records must be cancelled before deletion.
Report and calculation logic
-
The assistant runs your existing reports; it does not compute figures independently.
-
Totals, margins, ageing, and stock values come from the system's own report logic.
-
An empty result signals incorrect filters, prompting the assistant to re-check requirements.
-
Heavy reports run in the background with a sensible wait, and completed results are reused.
Analysis and code rules
-
The read-only query tool accepts only reads, blocks multiple statements, and caps rows.
-
The analysis sandbox blocks data changes, file access, network access, and charting.
-
Code execution is bounded by time, memory, and processor limits set in Settings.
Recording and privacy rules
-
Every action is logged against a named user with its outcome.
-
Sensitive values are redacted from the log automatically.
-
Logs are retained for a configurable period and cleaned up automatically.