# The activity log: who did what and when in your organisation — MijnEvent [Home](https://mijnevent.nl/en) / [Blog for event organizers](https://mijnevent.nl/en/blog) / The activity log: who did what and when in your organisation dashboard privacy security team # The activity log: who did what and when in your organisation Dashboard → Activity holds the complete logbook of your organisation: time, who, which action and which subject. Only the owner can reach it, and nobody can change anything in it afterwards. [Jasper Koers](https://mijnevent.nl/en/author/jasper-koers) · 29 June 2026 · 4 min read In short - Dashboard → Activity shows the complete logbook in four columns: Time, By, Action and Subject. - Only the owner of the organisation has access; the frontend and the server both check for it. - The log is append-only and hash-chained: entries are immutable, and corrections are made with a new entry. - 'E-mail address revealed' is recorded too, because requesting a masked address is itself a processing operation. Who published that event? Who refunded that order? And who looked up the e-mail address of that one complainant last week? With a single administrator those are easy questions. With a team of five it is guesswork — unless you write it down. MijnEvent writes it down. Your dashboard has the logbook of your entire organisation under **Activity**, with a subtitle that says precisely what it is about: who did what and when in this organisation. # For the owner only The activity log is the complete audit trail of your organisation, and that is sensitive information. That is why the page is restricted to the **owner**. If a team member clicks the URL anyway, the app sends them back to the dashboard. And that is not just a screen: the server checks the same rule once more and answers with "only the owner of this organisation has access to the full activity log". That does not mean the rest of your team is left in the dark. Privacy actions concerning one specific visitor also appear in the **Recent privacy actions** overview on the [page for GDPR requests](/en/blog/handling-gdpr-requests), and that one stays open to your whole dashboard team. # Four columns The table has exactly four columns, and you do not need any more than that: - **Time** — date and time, newest first. - **By** — the name of the team member who carried out the action. - **Action** — a readable label, not a technical code. - **Subject** — what the action was about: the event name, the visitor's e-mail address or the order number. You see the hundred most recent actions. If nothing has happened yet, it simply says "No activity yet". # What goes into it The log collects the actions that genuinely matter in a ticketing organisation. Around your programme you see *Event created*, *Event updated*, *Event published* and *Event deleted* — handy when you are wondering exactly when that price change went in. Around money and orders, *Order refunded* appears, with the order number as the subject. Around personal data there are *E-mail address revealed*, *Data exported* and *Data anonymised*. And around the security of your account, *2FA requirement changed* comes into view: the moment someone switched two-factor authentication on or off for the whole organisation. How that requirement works is covered in the article on [magic login and 2FA](/en/blog/magic-login-and-2fa). # Why "e-mail address revealed" is recorded too This is the line organisers most often pause at for a moment. Why log that someone looked at an e-mail address? Because e-mail addresses are shown [masked](/en/blog/privacy-email-masking) in the dashboard by default. You see enough to do your job, but no more than that. If you want to see the full address — to call a visitor about a wrong ticket, for instance — you request it explicitly. That request is itself a processing of personal data, and so the system records who requested which address and when. That sounds strict, but it works both ways. It protects your visitors from prying eyes, and it protects your team: if a question ever comes up about how an address ended up somewhere, you can show what happened instead of having to reconstruct it from memory. # Append-only: the log cannot be rewritten A logbook you can edit yourself is not a logbook. That is why the activity list runs on an **append-only ledger**. Every new line gets a hash calculated over the contents of that line *and* the hash of the previous line. That creates a chain: pull a link out of the middle or change one, and the rest no longer adds up. In practice that means entries are immutable. You cannot update a line and you cannot throw it away — the underlying model simply refuses. If something is not right, you correct it with a **new** line that complements the old picture. So the log only ever grows, and that is exactly what makes it usable as evidence. # What you do with it For most organisers the activity log is something you rarely open and are immediately glad exists when you do. Three moments where it does its job: 1. **Something went wrong.** An event was suddenly set to published, or an order was refunded. You see at a glance who did it and when, and you can have the conversation instead of speculating. 2. **Someone leaves your team.** Before you revoke an account, you can see what they were working on. 3. **A visitor asks a question about their data.** You can give a substantiated answer about what happened to their data — exported, revealed or anonymised — instead of "nothing as far as we know". The activity log costs you nothing and needs no setting up. It is simply there, from your very first event. Frequently asked questions ## Frequently asked questions ## Who can view the activity log? Only the owner of the organisation. A team member who tries to open the page directly is sent back to the dashboard and gets an error from the server. ## Can I delete a line from the log? No. The logbook is append-only: entries cannot be edited or deleted. A correction is always a new line, never a change to an old one. ## Why does 'E-mail address revealed' appear in the log? Because e-mail addresses are masked in the dashboard. Requesting the full address is a processing of personal data, so the system records who requested which address and when. ## How many lines do I see? The page shows the hundred most recent actions, newest first. [ Back to blog ](https://mijnevent.nl/en/blog) MijnEvent ## Read more [ ![](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/covers/automatic-membership-renewal-dutch-law.webp) memberships Jasper Koers · 27 July 2026 · 6 min read ## Automatic membership renewal: collecting fees within Dutch renewal law Automatic renewal saves your club a pile of chasing work, but the law has rules about cancelling. Here is how renewal works in MijnEvent, and how to keep it clean. ](https://mijnevent.nl/en/blog/automatic-membership-renewal-dutch-law) [ ![](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/covers/ontruimingsverslag-evenement-bewijsstuk.webp) safety MijnEvent · 27 July 2026 · 5 min read ## The evacuation record: why the day after your event matters for the next permit An evacuation — real or drilled — is only finished once it is on paper. What belongs in an evacuation record, why the municipality asks for it, and how to make the record write itself instead of reconstructing it afterwards? ](https://mijnevent.nl/en/blog/evacuation-record-event-evidence) [ ![](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/covers/knmi-weeralerts-veiligheidsplan.webp) safety MijnEvent · 27 July 2026 · 3 min read ## Weather monitoring in your safety plan: how KNMI warnings land in your alerts and logbook automatically Almost every safety-plan format has a 'weather monitoring' section — and almost nobody fills it in concretely. The Safety & Permit module pulls the KNMI warning code for your event location every hour and turns it into a demonstrable process. ](https://mijnevent.nl/en/blog/knmi-weather-alerts-event-safety-plan) MijnEvent ## Ready to get started? Create a free account and sell your first tickets today. [Start free](https://mijnevent.nl/registreer) [Pricing](https://mijnevent.nl/en/pricing)