Activity and audit log
Sqoura keeps one record of everything done in your organisation and shows it to you twice: a compliance view and an everyday one.
| View | Where | For |
|---|---|---|
| Audit Trail | Settings → Access & Security → Audit Trail | Investigating, proving and exporting. Every action, with who, what, where and whether it was allowed. |
| Activity Log | The main navigation, outside Settings | Reading at a glance. The same record, written in plain sentences with links through to the thing itself. |
Both are append-only. Nobody can edit an entry after the fact — not you, and not Sqoura.
What is recorded
Section titled “What is recorded”Every entry carries:
- Who acted — and, where a Sqoura support operator was acting as one of your users, who they were acting on behalf of.
- What they did, and what they did it to.
- How sensitive it was: low, normal or high.
- The outcome: allowed, denied, or an error. A refused attempt is recorded just as firmly as a successful one.
- The address and browser it came from, and the session and request it belonged to.
- When, shown as how long ago with the exact time on hover.
High-sensitivity rows carry a warning icon. Anything done during a support session carries an impersonation tag beside the actor.
Reading the Audit Trail
Section titled “Reading the Audit Trail”The columns are Action — a plain-English description with the underlying action name beneath it — then Actor, Sensitivity, Outcome, IP and When.
To narrow it down:
- Search actor, action, target… searches across all of those at once.
- Action prefix narrows to a whole family at a stroke. Typing
payment.gives you everything to do with payments. - Impersonations shows only what a support operator did while acting as one of your users.
- The Sensitivity and Outcome chips under the search row carry live counts for whatever is filtered now. Click one to apply it, click it again to drop it.
- Clear resets the lot.
Load more pages further back, and a line tells you how many events are loaded.
Saved views
Section titled “Saved views”A filter you will want again can be kept.
- Set the filters up as you want them.
- Press Save view — it only becomes available once a filter is active.
- Name it something you will recognise later, such as High-risk this month.
Saved views appear as chips under the heading. Click one to apply it, or its × to delete it.
Reading the Activity Log
Section titled “Reading the Activity Log”The Activity Log presents the same record for everyday use: an avatar, an icon coloured by what happened, and a sentence per row that links through to the entry, payment or tournament it describes.
It filters by category — All activity, Applications, Payments, Tournaments — and by date — All time, Today, Last 7 days, Last 30 days, Last 12 months — with a search box alongside.
Exporting
Section titled “Exporting”Both views export the same way, and both ask for a second factor.
- Press Export.
- Enter a code from your authenticator app. Exports are always gated on this.
- The button reads Generating… and the export is queued. You do not have to wait on the page — close it and carry on.
- When it is ready you get an in-app notification and an email, “Your audit export is ready”. Following the link creates a fresh, short-lived download and starts it. If the download does not begin by itself, the notification carries a Download button.
| What you see | What it means |
|---|---|
| Audit export failed | The export did not complete; the reason is given. Start it again. |
| Audit export expired — Please start a new export. | The download link was left too long. Links are deliberately short-lived; run a fresh export. |
A per-person view
Section titled “A per-person view”For your own account only — your sign-ins, password changes, two-factor changes and revoked sessions — there is Recent Security Activity on Account → Security. To see what one colleague has been doing, open the ⋯ menu on their row in Users & Roles and choose View activity.