SkieWhat does the Skie audit log record?
The audit log records significant actions in your organisation, such as policy edits, restores, locks and releases, with who did them and when. It lets you answer who changed a rule, find the right backup to restore from, and review what happened after an incident. Access to it follows role permissions.
When something changes on hundreds of tablets, the next question is who did it. The audit log is the answer. It keeps a time-ordered record of actions taken in the dashboard, along with the person who took them.
It is useful in three everyday ways. First, to learn the cause of a change in behaviour: a class cannot open an app, and the log shows the app list was edited that morning. Second, to pick the right backup when you need to restore something, because you know the date of the edit. Third, to review actions with a principal or manager after an incident, such as a panic lock or a locate request.
Because roles define who can do what, the log makes the role design visible. If many people can change shared policies, you will see many names in the log. That is often the nudge to tighten access. See role-based access for school device management.
Some things are logged elsewhere in the product. The compliance history shows scores over time, and the breach centre shows alerts. The audit log is about actions people took. A printable compliance audit report is not available yet, although the scores and history are visible on the dashboard.
Skie does not publish a retention period for the log, and configurable retention is not available yet. Practical tip: if your trustees or management need regular accountability, set a monthly review where one person scans the log for surprises, which takes a few minutes and builds the habit of leaving good notes.