Audit logs
A record of who changed what in your workspace, plus what visitors reported about your content. Use it for compliance, security reviews, and answering "when did this change?"
Reviewed 24 Oct 2026Available from the Business plan
What it records
Consequential changes to the workspace, each with who did it and when.
- Team: invitations sent and cancelled, members joining and being removed, role changes, ownership transfers.
- Billing: plan changes, cancellations, and payment-status events.
- API keys: keys created and revoked.
- Account: account deletion scheduled and cancelled.
- Custom domains: domains added and removed, the default changed, and the outcome of verification.
- Links: links created, edited, paused, resumed, deleted, and bulk actions on many at once.
- Analytics: CSV exports, with the range each one covered, and shared reports created or revoked.
- Plan limits: when a plan limit or a feature not on your plan stopped somebody doing something.
It is a change log, not a click log
Reports about your content
The same plan opens a second list on this page, below the trail: what visitors reported about your links and bio pages, and what we decided. It appears once a report has been reviewed: an open one is an unverified accusation, so it is not shown while it is in flight.
- What it was reported as: phishing, malware, spam, copyright, or a DMCA notice.
- What we did: removed, reviewed with no action taken, or removed and under appeal while we look at it again.
- Which link or bio page it was about, and the date.
Reporters are not identified
What it is for
| Situation | What the log gives you |
|---|---|
| A security questionnaire asks whether you track administrative changes | A yes, with evidence, and a tamper-evident record behind it. |
| Someone's access changed and nobody remembers doing it | The person and the timestamp. |
| A quarterly access review | Every role change in the period, in one place. |
| An API key needs to be traced | When it was created and by whom, and when it was revoked. |
Integrity
Entries are append-only, and each one is hash-chained to the entry before it. A scheduled job re-verifies the whole chain daily, so an entry altered or removed after it was written is detectable rather than invisible. Nothing edits a past entry. Entries are removed only when they age out, and personal details in them are redacted when an account is erased. That is the property that makes a log worth producing in a review at all.
Entries are retained on a rolling window. To keep records for longer, take a copy as you go: Export CSV writes every entry that matches the filters in force, not only the rows loaded on the page, so choose the category, actor and dates first and the file holds exactly that period. The export is itself recorded in the log, and you can take a limited number an hour.
Step by step
Run a quarterly access review
For: Workspace owners and admins on the Business plan
Before you start
- The Business plan.
- Somewhere to file the evidence.
Steps
Open Team and list the current members and their roles.
For each one, confirm they still need that level of access.
The usual finds are people who changed job internally and admins who should have been members all along.
Open Audit Logs and look at the period since the last review.
Check every role change and every ownership transfer against a request you can point to.
Anything unexplained is the finding: that is what the review is for.
Check API keys created in the period, and revoke any whose owner or purpose has gone.
Apply the changes on the Team page and the Developer page.
Record that you completed the review and file the date wherever you already track compliance evidence.
The record that the review happened is the deliverable. The tidying-up is a side effect.
What you should see
Access matches what people actually need, and you have a dated record showing the review happened.
How to check it worked
- Every current member's role has been explicitly confirmed.
- Every role change in the period is accounted for.
- The review date and outcome are filed with your compliance evidence.
Edge cases
- A change has no accompanying request.
- Treat it as a finding, not as noise. Establish who made it and why before you close the review.
- You need records older than the retention window.
- Export at each review rather than after the fact. Set the dates you want, then use Export CSV to take every entry in that period. Once entries age out of the window they are gone from the product, and the only copy is the one you took.
- You are not on Business.
- Everyone can still see their own activity on this page. The consolidated log across the workspace is a Business feature.
If something goes wrong
- You revoked an API key that was in use.
- Create a new key, deploy it to whatever was using the old one, and treat the outage as the cost of finding an undocumented integration. Keys cannot be un-revoked.