Security & control
Locked down from the first line.
SwanBooks moves stock and money, so who can see what, what it trusts and what it records were designed in from the start.
Who sees what
Roles, checked on every request.
The server decides what each person can open. Hiding a button is never the only lock.
| Role | Can do |
|---|---|
| Admin | Everything, including connections, users and email settings |
| Manager | Sales, purchasing, stock and receivables across companies |
| Warehouse | Stock, counts and critical levels, without money screens |
| Production | Factory stock and shipments only |
| Single company | One company's stock and documents, nothing else |
Only signed messages are trusted
QuickBooks notifications are checked against a shared secret. Anything unsigned or altered is rejected and logged.
A strict browser policy
Pages run only SwanBooks' own code. Injected scripts and inline handlers don't execute.
Everything is logged
Stock changes, edits, voids and emails land in an audit log with the person's name and the time.
No surprise emails
Reminders and reports go to your own team. Only invoices and purchase orders you choose to send reach customers and vendors.
Backups every week
A full backup arrives by email every Friday with passwords and tokens removed, plus daily inventory snapshots.
Secrets stay on the server
Connection tokens and bot keys are never sent to the browser. Settings pages show that a key is set, not the key itself.
Questions from your IT team?
Book a call and bring them. We'll walk through how access and data are handled.