Skip to content
plugboard.appRequest a demo

Running the desk

The audit log

Logs (/logs), under Knowledge & reports. Requires audit.view.

Examples of operations with audit records:

AreaExamples
Sign-inSigned 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
SessionsA person signed out everywhere after a retired sign-in token was presented again, shown as Refresh token reuse detected
TicketsCreated, noted, transferred, handed to Security, merged, reopened
Problems and major incidentsA 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
ChangesChange records saved and moved on, approvals decided, a service named as affected, the change rules changed
ServicesA 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
RepairsLodged, status changed, technician assigned, outcome recorded, an attachment added or deleted, the damage photo setting changed
Ticket timeTime logged, edited or deleted, estimate changed, time tracking settings changed
Quick timeLogged, edited, deleted, turned into a ticket
LoansIssued, returned, registered, bulk actions, a loan released after its erase, a loan group changed
DevicesMDM commands sent
ChargesRaised, approved, declined, waived
People syncPeople synced, a student system claim applied, a creation or deactivation held back by a roster guard
ConfigurationModules, workflow, roles, users, campuses, connectors, the security policy, a Wonde school token collected
BackupsRestored, offsite backups brought back, managed backup defaults applied
KiosksReserved, set up, revoked, a setup code issued again, and a device presenting a kiosk credential that matches no kiosk
Support accessGranted, ended, every support request, and every refused one
Set automaticallyChanges 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:

ActionShown as
ticket.timeLogTicket time logged
ticket.timeEditTicket time entry edited
ticket.timeDeleteTicket time entry deleted
ticket.estimateTicket estimate changed
ticket.timeSettingsTime tracking settings changed
time.quickLogQuick time logged
time.quickEditQuick time edited
time.quickDeleteQuick time deleted
time.quickConvertQuick 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.

ActionShown as
auth.signInSigned in with a password
auth.signInFailedPassword sign-in refused
auth.signOutSigned out
auth.mfa.enrolledAuthenticator app set up
auth.mfa.disabledAuthenticator app removed
auth.password.changedOwn password changed
passkey.signInSigned in with a passkey
vendor.access.grantVendor support access granted
vendor.access.endVendor support access ended
vendor.access.refusedVendor support request refused
vendor.status.readDeployment status read by vendor support
vendor.admins.readAdministrator list read by vendor support
vendor.backups.readBackup list read by vendor support
vendor.admin.resetAdministrator setup link requested by vendor support

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.

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.

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.

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.

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.

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.

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.

PermissionAllows
audit.viewRead 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.