The Dapple user activity log is in Organisation Settings → Data & Activity → View activity log. It records every action taken on the platform — who did what, when, on which submission. The log is immutable (you can't edit entries), can be filtered by action type and date, and exported as a CSV for compliance or audit purposes.
Why use the activity log?
Audit decisions — see who moved a submission, when, and to which stage.
Investigate issues — when something looks wrong, the log shows the chain of actions.
Compliance and reporting — keep a record of every user action for legal or contractual obligations.
Onboarding handoff — review recent activity when a new lead takes over a project.
How to view the activity log
Open Settings → Organisation Settings.
Click Data & Activity.
Select View activity log.
What's recorded?
Every action taken on the platform — submissions created, stages changed, assignments, tags applied, messages sent, exports generated, settings updated, users invited. Each entry shows the user, the action, the target (submission, project, user), and a timestamp.
Filtering the log
Use the filters at the top of the activity log view to narrow by:
Action type — Stage Change, Message Sent, Tag Applied, etc.
Date range — useful for compliance reporting or investigating a specific time period.
(More filters may be available — check the live UI.)
Exporting the log
Click Generate Report to export the filtered log as a CSV. Useful for handing off to legal, audit, or compliance teams.
FAQs
Question | Answer |
Is the activity log editable? | No. The log is immutable — entries can't be edited or deleted. This is intentional for audit integrity. |
Can I filter the log? | Yes — by action type and date range. |
Can I export the log? | Yes. Click Generate Report to export as CSV. |
Who can see the activity log? | Admin-permission users only. |
How far back does it go? | Since your organisation was created on Dapple. |
Best practice
Pull a periodic report (e.g. monthly) and store it with your records — it's your audit trail.
When investigating a problem, filter by date range first, then by user or action type.
Don't rely on the log for everyday workflow visibility — use Notifications and Saved Views for that. The log is for retrospectives and audits.