What the audit log records
Every significant action in your organization is automatically recorded in the audit log. This creates an immutable trail of who did what and when, giving you full visibility into your organization's activity on The Taurus.
The audit log is not something you need to set up or configure. It runs automatically from the moment your organization is created. Every action that changes the state of your notices, membership, or settings is captured without any manual effort.
Accessing the audit log
Organization audit log
Navigate to your organization and open the Audit section. Here you will see a chronological list of all logged actions for your organization. The most recent actions appear first.
Every entry in the log shows three pieces of information:
- Who performed the action -- the name and role of the team member.
- What changed -- a description of the action and the affected resource.
- When it happened -- a timestamp for the action.
Platform-wide audit log (admins only)
If you are a platform administrator, you have access to a separate audit log at the admin level. This log spans all organizations on the platform and is used for platform governance and support purposes. Regular organization members do not have access to this view.
What actions are tracked
The audit log captures a broad range of actions across your organization. Here are the main categories:
Notice lifecycle
- Notice created -- A new transparency notice draft was started.
- Notice edited -- Changes were made to a draft or published notice.
- Notice published -- A draft notice was published and became publicly accessible.
- Notice archived -- A published notice was moved to the archive.
These entries let you trace the full history of every notice from creation through publication. If a question arises about when a notice was changed or who approved its publication, the audit log has the answer.
Team membership
- Member invited -- A new user was invited to join the organization.
- Role changed -- A member's role was updated (for example, from editor to admin).
- Member removed -- A user was removed from the organization.
Tracking membership changes is important for security and accountability. If access needs to be reviewed -- for example, after a team member leaves the organization -- the audit log shows exactly when their access was granted and revoked.
Chapters and publishers
- Chapter created or modified -- Changes to the organization's chapter structure.
- Publisher linked or unlinked -- Changes to publisher relationships.
These entries are relevant for organizations that manage multiple chapters or work with external publishers. They document the organizational structure over time.
Settings and billing
- Settings changed -- Modifications to organization-level settings, such as default notice fields or notification preferences.
- Billing actions -- Subscription changes, plan upgrades or downgrades, and payment events.
Using the audit log for compliance
Internal reviews
Conduct periodic reviews of the audit log to ensure that your team is following established processes. For example, you might check that notices are being reviewed before publication or that role assignments align with your organization's access policies.
Regulatory inquiries
If a regulator asks about your transparency practices, the audit log serves as evidence that your organization has documented processes and accountability. You can show when notices were created and published, who was responsible, and how changes were handled.
Complaint investigations
When you receive a complaint about a transparency notice, the audit log helps you investigate. You can trace the history of the notice in question -- when it was created, who edited it, what changes were made, and when it was published. This context is essential for responding to complaints accurately.
Access audits
Periodically review the membership entries in the audit log to verify that only authorized individuals have access to your organization. This is especially important for larger teams or after organizational changes.
What the audit log does not cover
The audit log tracks actions within The Taurus platform. It does not:
- Record actions taken outside the platform (for example, printing QR codes or placing advertisements)
- Track individual page views or login sessions (these are not considered significant actions)
- Store the full content of every change (it records that a change happened, not necessarily a detailed diff of every field)
For a detailed record of notice content at specific points in time, the published notice itself and its version history serve that purpose.
Retention and access
Audit log entries are retained for the lifetime of your organization. They cannot be edited or deleted by organization members, which ensures the integrity of the trail. Only platform administrators can access logs across organizations, and they do so for platform governance purposes only.
All members of your organization can view the organization's audit log, but only actions relevant to the organization are shown. Individual members cannot see logs from other organizations they do not belong to.
How the audit log fits into your workflow
The audit log works best as a background safeguard. You do not need to check it every day, but it is there when you need it:
- After a complaint, to trace the history of a notice
- During an internal review, to verify team compliance with processes
- Before a regulatory inquiry, to prepare documentation
- After a security concern, to check who had access and what they did
Combined with the TTPA Check, the complaint mechanism, and the compliance profile, the audit log rounds out The Taurus's compliance toolkit -- giving you not just the tools to create transparent advertising, but the records to prove you did it right.