Who did what, and when.
All state-changing and privileged actions are written to an append-only audit trail. Append-only is enforced by the database: a row cannot be updated after it is written, and the platform proves that to itself at startup.
Enough to answer the question without opening the record.
Each row names the person, the action, what it was done to, and when. Where the action carries a figure — a filing charged to the wallet, an invoice issued — the figure is in the row.
The trail is scoped like everything else: a company administrator sees their company's, a partner administrator sees their partition's, and neither sees inside the other. It can be exported from the screen you are reading it on.
Declarly cannot reach your records as itself.
Support staff hold two permissions: start a support session, and read the platform audit trail. Neither of those lets anyone read a customer's filings. Reaching your workspace at all means opening a session against a named ticket, and a session is not a login — it is a narrowed one.
Read-only
Keeps only the permissions that read. Every request that would change something is refused before it reaches the application.
Assisted write
Drops approve and transmit. Support may draft alongside you; it may never conduct customs business.
Full override
The whole permission catalogue for that tier. It demands a permission of its own that ordinary support staff do not hold, and is refused without it.
A session is time-boxed and closes itself. Starting a new one supersedes the old. Everything done inside one is on the audit trail as having been done inside it, with the ticket it was opened against — so "support was in here" is a matter of record rather than of trust.
The narrowing is applied where the request is authorised, not in the screens. A support session cannot get a permission back by calling a different endpoint.
The two things support can never do.
Approve an entry, and file one.
Both are dropped from the permission set of an assisted-write session, by name, for the same reason the platform refuses an approval from the person who prepared the entry: approving and filing are customs business, and customs business belongs to your licensed broker. Support can help you build something. It cannot be the one who signs for it.
How to see it for yourself.
Open the live demo and look. Sign in as Declarly support and you get the support desk, which shows the sessions, their modes and how long each ran — and no way into a customer's records except through a ticket.
Then sign in as a company administrator and open the same events from the other side. The two views are the same rows.
Anything you find that these pages do not explain — hello@declarly.com.