Who this is for: studio operators (admin panel) · Product: Podyx V2
The Audit tab is a ledger of everything that has changed in your CMS. Who did what, and when. It is the least glamorous tab in Podyx and the one you will be most grateful for on a bad day.
🎥 Watch the walkthrough
🔧 Where to find it
Admin Panel → Audit
👥 Settle questions about team activity
Especially useful once you have more than a couple of people with access. When there is uncertainty about whether a change was made, and by whom, the audit log answers it in seconds rather than turning into a conversation nobody enjoys.
📅 Session reschedules are logged
When a session is rescheduled from the CMS, the audit log records it — who moved the booking, and the old and new times. Useful for settling any confusion about whether a time change was intentional, and when exactly it happened.
🎯 The Outcome column
Every entry in the audit log now carries an Outcome, so you can see not just that a change was attempted, but whether it actually took effect. Previously a refused save appeared in the log looking exactly like one that went through, which made auditing harder than it should have been.
Applied. The change took effect.
Failed. The change was attempted but did not complete.
Denied. The change was refused, usually because the person did not have permission to make it.
Unknown. The outcome could not be determined.
When you are reviewing the log, read the Outcome column before you conclude that something was changed. An entry existing is not the same as a change landing.
💡 A run of Denied entries against one person is usually a permissions question rather than a mistake — check their role before assuming they were doing something they should not.
🐛 Trace what happened before something broke
When something starts behaving strangely, the first question worth asking is what changed. The audit history shows you exactly that, so you can tell the difference between a genuine bug and a setting someone adjusted this morning.
🤝 Speed up support
You can send audit details to our support team when you report a problem. A clear record of recent changes usually turns a long back-and-forth into a quick fix, and it is genuinely the most useful thing you can attach to a bug report.
🧠 Why it matters
No mysteries. Every change has a name and a timestamp against it.
Faster troubleshooting, because you start from evidence instead of guesswork.
Confidence to delegate, since nothing happens invisibly.
✅ Summary
The audit log records all CMS activity — including session reschedules. Use it to confirm who changed what, to work out what shifted just before a problem appeared, and to give support the context they need when you raise an issue. Check the Outcome column to confirm a change was applied rather than failed or denied.
Related: Roles & Permissions · Invite Your Team & Roles