Who did what on your account
When something changes on your account — a service cancelled, a contact added, a setting flipped — the useful question is not just “what changed” but “who did it, and when”. That is what an audit trail answers.
Accounts rarely have just one person on them, and memories are short. An audit trail — a record of significant actions, who took them and when — turns “I think someone cancelled that” into a plain fact. It is the difference between a mystery and an answer.
What gets recorded
- Logins and access to the account
- Changes to services — orders, cancellations, upgrades
- Changes to who can act on the account — see who may act on your account
- Changes to settings and billing details
Why it matters for security
If an account is ever misused, the trail is how you find out what happened and how far it went — which is exactly what you need to respond well. An unexplained change in the log is an early warning worth acting on; its absence is reassurance. It pairs directly with keeping your account secure and, if the worst happens, a compromised server.
It matters more with a team
The moment more than one person can touch an account, “who did this” stops being obvious. A shared login makes the trail useless — every action looks like the same person. Give each person their own access instead, so the log actually means something. See authorised contacts.
Reviewing it
It is worth a glance now and then, not just after something goes wrong — a quick scan for logins or changes you do not recognise catches problems early. Treat an entry you cannot explain as a question to answer, not a line to skim past.
Requesting a copy
If you need the record of actions on your account — for your own security review, or for an audit — ask us and we will provide what we hold for your account. For how this sits alongside the personal data we keep, see GDPR: who is responsible for what.
Keep your own side logged too
The audit trail covers actions on your account with us. What happens inside your server — who logged in, what they ran — is yours to record, and worth doing for the same reasons. See shipping logs off the machine and knowing when a file changed.
Still stuck? Mail support@novogara.com — an engineer answers, at any hour. Back to the knowledge base