The audit log
Logs (/logs), under Knowledge & reports. Requires audit.view.
What is recorded
Section titled “What is recorded”Examples of operations with audit records:
| Area | Examples |
|---|---|
| Sign-in | Signed in with a password, a password sign-in refused, signed out, an authenticator app set up or removed, a person’s own password changed, signed in with a passkey, signed in with single sign-on |
| Sessions | A person signed out everywhere after a retired sign-in token was presented again, shown as Refresh token reuse detected |
| Tickets | Created, noted, transferred, handed to Security, merged, reopened |
| Problems and major incidents | A problem raised from tickets, incidents resolved with their problem, a major incident declared, tickets attached to it, the service it is about named or cleared, the major incident ended |
| Changes | Change records saved and moved on, approvals decided, a service named as affected, the change rules changed |
| Services | A service added, edited or deleted, a part linked or removed, a status set or cleared, its service levels or fleet changed, a review marked, a ticket filed under a service |
| Repairs | Lodged, status changed, technician assigned, outcome recorded, an attachment added or deleted, the damage photo setting changed |
| Ticket time | Time logged, edited or deleted, estimate changed, time tracking settings changed |
| Quick time | Logged, edited, deleted, turned into a ticket |
| Loans | Issued, returned, registered, bulk actions, a loan released after its erase, a loan group changed |
| Devices | MDM commands sent |
| Charges | Raised, approved, declined, waived |
| People sync | People synced, a student system claim applied, a creation or deactivation held back by a roster guard |
| Configuration | Modules, workflow, roles, users, campuses, connectors, the security policy, a Wonde school token collected |
| Backups | Restored, offsite backups brought back, managed backup defaults applied |
| Kiosks | Reserved, set up, revoked, a setup code issued again, and a device presenting a kiosk credential that matches no kiosk |
| Support access | Granted, ended, every support request, and every refused one |
| Set automatically | Changes the desk made by itself, such as triage, tidy-ups and merges |
The sign-in entries carry the IP address and browser. A refused sign-in records only the kind of reason; an address that matches no account is kept as a keyed hash, and at most one refusal a minute is recorded for each address and account. See audit and retention.
Time tracking records these actions:
| Action | Shown as |
|---|---|
ticket.timeLog | Ticket time logged |
ticket.timeEdit | Ticket time entry edited |
ticket.timeDelete | Ticket time entry deleted |
ticket.estimate | Ticket estimate changed |
ticket.timeSettings | Time tracking settings changed |
time.quickLog | Quick time logged |
time.quickEdit | Quick time edited |
time.quickDelete | Quick time deleted |
time.quickConvert | Quick time turned into a ticket |
An edit records the entry before and after. Starting, pausing and discarding a
timer is not recorded; logging one writes ticket.timeLog.
A security incident handed to Security is
recorded as ticket.handToSecurity, shown as Ticket handed to Security. The
entry names who or what handed it over, the ticket number, the departments it
went from and to, and whether it was raised, recategorised or handed over by an
automation. It never records the ticket’s subject or details, and the person
who handed it over cannot read the entry afterwards, because they can no longer
read the ticket. Choosing where security incidents go is recorded as Ticket
options updated.
Entries identify the actor, action, time and recorded details. Coverage varies by operation and version; see current gaps.
Sign-in and support actions
Section titled “Sign-in and support actions”| Action | Shown as |
|---|---|
auth.signIn | Signed in with a password |
auth.signInFailed | Password sign-in refused |
auth.signOut | Signed out |
auth.mfa.enrolled | Authenticator app set up |
auth.mfa.disabled | Authenticator app removed |
auth.password.changed | Own password changed |
passkey.signIn | Signed in with a passkey |
vendor.access.grant | Vendor support access granted |
vendor.access.end | Vendor support access ended |
vendor.access.refused | Vendor support request refused |
vendor.status.read | Deployment status read by vendor support |
vendor.admins.read | Administrator list read by vendor support |
vendor.backups.read | Backup list read by vendor support |
vendor.admin.reset | Administrator setup link requested by vendor support |
Refresh token reuse alerts
Section titled “Refresh token reuse alerts”An alert means a retired refresh token was presented outside the short grace window. The first detection ends that account’s live sessions and records how many were ended. No live sessions means there were none left at that moment; it does not identify why the token was presented. Check the account, time and other sign-in evidence, and ask the user about stale tabs or devices. Treat an unexpected first detection as a possible credential replay.
In versions before 0.22.1, the same stale browser could produce repeated alerts even after the account had no live sessions. From 0.22.1, each retired token produces at most one reuse alert. A new alert for another token still needs review. See session security and the 0.22.1 release note.
Append-only
Section titled “Append-only”The application has no interface to edit an entry or delete one by ID. Hosting and database administrators have separate authority; the restricted production Docker database role adds enforcement that demo/native owner connections do not. Within the product, entries leave when they fall outside the retention window, which cannot be set shorter than 90 days, and a purge writes its own entry saying who ran it and what it removed.
What is not recorded
Section titled “What is not recorded”Some access and write operations. API-key lifecycle, connector agents, backup runs and settings, and some configuration changes have coverage gaps; see what is not recorded. Do not infer that no action occurred merely because no event appears.
Secret values. Configuring a connector is logged; the token you pasted is not.
Read operations, mostly. Looking at a person’s profile is not logged. Changing it is. Support requests are the exception: every one is recorded, reads included.
Message bodies. That a ticket reply was sent is logged. The text lives on the ticket.
Using it
Section titled “Using it”The areas of what is loaded are tabs across the top, busiest first, each with its count: All, then areas such as Tickets, Repairs, People and Desk activity.
Filter by Person, Record type, Date and Action (several actions at once). Display groups the list by day, area or person.
Set automatically narrows the list to what the desk changed by itself: triage, tidy-ups and merges applied without a person, each of which can be undone on its record. Home’s Recent activity links straight to it. Entries made by the desk itself carry the Plugboard mark instead of a person’s initials.
Every entry opens. Its details name who performed it, the source, the action and when it was recorded, with Only this record and Only that person to narrow the list. Right-click an entry to open its record, copy a link or copy the event ID.
Export CSV downloads what the filters show.
What to use it for
Section titled “What to use it for”Accountability. Who closed this, who approved that charge, who sent that wipe.
Troubleshooting. “It stopped working on Tuesday” often turns out to be “somebody changed a connector on Tuesday”.
Reviewing access. Once a term, look at what a role has been used for. It is usually narrower than what people asked for, which gives you evidence for tightening permissions.
Answering a question from outside ICT. For example, trace a disputed charge to the recorded approval. For operations without audit coverage, use the related ticket and the provider’s own records too.
Retention
Section titled “Retention”Configurable. Longer is better for investigation and worse for disk and for privacy.
The audit log is the largest table on any mature install, so retention is also the main lever on database size. See audit and retention.
Some jurisdictions set a minimum retention for records of access to student data. Check before setting it short.
Support access
Section titled “Support access”On managed hosting, Plugboard support can reach your deployment only while an administrator has granted support access under Settings, Compliance. The grant and its end are recorded, every support request is recorded before it reads anything, with the operator’s name, and a request without a grant is recorded as refused. Support activity on the Compliance page lists the last 20 and opens them here. Direct hosting administration is not represented here, and the grant does not change it.
Permissions
Section titled “Permissions”| Permission | Allows |
|---|---|
audit.view | Read the log |
There is no permission to write to it, and none to delete from it, for anyone
including administrators. user.manage sets the retention window and can run the
purge, which is the only thing in the product that removes entries at all; both
ask for a fresh confirmation of who you are, and the purge records itself. See
audit and retention.