Skip to content

Review the audit log

The audit log is one timeline of everything that happens in Pulse. Every registration, approval, payment, check-in, room change, and permission change is written to it with who did it and when. Use it to answer “who changed this?” without asking around.

Only super admins can open the audit log. If you need it but do not see it, ask your super admin.

Each entry is a plain-language event, not technical data. For example: Ahmad Zaki registered for Bengkel Taskforce · 2 tickets · Normal · RM 150.00 · payment unpaid.

The log covers the activities organisers and admins care about:

  • Registrations — who registered, was approved or rejected, cancelled, or did not show up.
  • Payments — who marked a payment as paid, who reverted it, and who uploaded payment proof.
  • Check-in — who checked a participant in, who checked them back out, and who scanned a ticket.
  • Accommodation — who assigned a room, changed a room, released a room, or requested a room change.
  • Access — who was granted admin access, whose role changed, and who was revoked.
  • Sign-in — who signed in, signed out, and when an account was created or deleted.
  • Events, tickets, content, and email — event edits and publishing, ticket changes, news and announcements, and notification sends.

Nothing is dropped silently. If an action does not fit a known type, Pulse still records it under a generic label.

  1. Sign in to the Pulse app. Go to https://pulse-ucare.my with your super admin account.
  2. Open the Admin Overview. This is the admin landing page.
  3. Choose Audit Log. The log opens as a live list of the most recent entries.

The list keeps itself up to date as new activity happens. You do not need to reload the page, and there is no waiting for a refresh.

The page loads the 200 most recent entries and lets you narrow them down:

  1. Search. Type a name, email, or event name to find related entries.
  2. Filter by category. Show only registrations, payments, check-ins, and so on.
  3. Filter by source list. Limit the results to one area, such as registrations or accommodation.
  4. Filter by actor. Show only what one person did.
  5. Filter by date range. Set a start and end date to review a specific period.
  6. Load older records. If you need to go further back than the first 200 entries, use the load-older option at the end of the list.

Open any entry to see the detail behind it:

  • The sentence. A one-line summary of what happened.
  • The actor. Who did it, and whether the change came from the app or from Pulse itself.
  • What changed. The fields that changed, with the value before and after each one.
  • Full record snapshots. The complete record as it looked before and after the change. For a deletion, the record as it was just before it was deleted.
  • Time and record. When it happened, which event it belongs to, and which record it refers to.
  • Session details. For sign-in and sign-out entries, the IP address and device used.

Sensitive values such as passwords, tokens, and access codes are never shown. They are replaced with a redacted marker before the entry is saved.

Most entries name the person responsible. Some say Not recorded, and that is deliberate:

  • Deletions show Not recorded. Pulse cannot prove who deleted a record, because the person who last edited it is not necessarily the person who removed it. Naming the wrong person is worse than admitting the gap. The last editor is still visible inside the before snapshot.
  • Some participant actions show no name. A few participant areas only accept a limited set of fields, so Pulse cannot attach a name without rejecting the write. The action is still recorded; only the name is missing.

An actor marked as coming from Pulse itself means the change was made by an automated process, not a person.

Use the export option on the audit log page to download the entries currently shown as a CSV file. The file opens in Excel or Google Sheets and is useful for reporting or for an external review.