Audit trail and account security
Review who did what, manage passkeys and keep your organisation secure.
Your organisation's audit trail#
Open Settings › Audit to review changes made in your organisation: who acted, what they did, to what, and when. Filter by person, target, the start of an action name (for example send. or user.) and a date range.
Each entry carries a sequence number and a hash linked to the previous entry. If anyone altered or deleted an entry, the chain would no longer verify. Actions by the Sauti platform team are kept in their own private operator audit.
Your own account#
Settings › My account shows your profile and sign-in methods. Settings › Passkeys lets you add, rename and remove passkeys. You are asked to confirm your identity again before changing them, you are notified when a passkey is added, and Sauti never lets you remove your last way to sign in.
Keeping the organisation secure#
- Use passkeys where you can. They cannot be phished.
- Never share accounts. The audit trail is only useful if each action belongs to one person.
- Review access monthly in Settings › Users, and disable anyone who has left.
- Watch for surprises: an unfamiliar login time, a send you did not expect or a changed setting. Check the audit trail and tell the Sauti team if something looks wrong.
- Do not paste supporters' details into notes, messages, task descriptions or incident reports. Sauti removes contact details it detects, but it is better not to type them.
Support access#
If you ask the Sauti team for help, a support colleague may open a read-only support view of your configuration. It needs a recorded reason and an approved grant, it ends automatically after 15 minutes or when the grant expires, and it is audited.