Configuration only β the numbers live in the
Reports Centre.
Everything here is owner/administrator territory and every change is audited.
π§ Daily dashboard email β the morning envelope
The dashboard digest (sales, alerts with
owners, data quality) posts itself every morning. Enter the mail settings β
the password is stored on the server, written only, never shown again, and
redacted from the audit trail. Easiest source: create
reports@tirufresh.co.zw in DirectAdmin (E-mail Accounts) and use
mail.tirufresh.co.zw, port 587.
π Ask TIRU β help-article library
The approved 'how do I' procedures the
assistant answers from. The author of an article can never approve it; edits
create a new draft version; retired articles are never served. Articles only ever
show to users whose own permissions allow the screen they describe.
New / edit article (same code = new version)
A DIFFERENT person approves it before Ask TIRU will serve it.
β¨ Ask TIRU β the AI assistant's voice
The β¨ Ask TIRU button on the module screens
already answers from the system's own governed data β read-only, permission-scoped,
every question audited. Adding an Anthropic API key here gives those answers a
natural voice; without one (or if the model is ever down) the assistant still
answers deterministically. Create the key at console.anthropic.com β API keys.
It is stored on the server, write-only, and redacted from the audit trail.
The printer lives on the shop's network where
this cloud server cannot reach it, so a small print agent (one file,
deploy/print-agent.js, runs on any PC in the shop β instructions inside it)
collects jobs from here and feeds the printer. Give the printer a fixed IP, enter it
below with port 9100, tick Enabled, and start the agent with the key. Until then,
tills print through the browser dialog.