The organization audit log
Every administrative action in a Dropstone organization is recorded, with filters, ranges, and a CSV or JSON export. What is in it, who can read it, and why nobody can edit it.
Every administrative action in your organization is recorded: who did it, what they did, when, and whether it succeeded. The log is in Audit in the dashboard.
What is in it
- Who made the change, and when.
- What they changed: a member's role, a policy, a data setting, a memory shared or withdrawn, an archive read.
- How it ended: succeeded, refused, or failed.
The log also carries a risk marker and an outcome, so a security review can filter to the actions that deserve attention rather than reading everything.
Read it
Filter by action, by risk, and by outcome, and narrow the range to the last 24 hours, 7 days, 30 days, 90 days, or all time. Then export what you are looking at as CSV or JSON.
The export is the same rows you can see, which is what makes it usable as evidence rather than as a summary of evidence.
Nobody can edit it
The console states it plainly: there is no way to edit or delete a row from here, and there never will be. A mutable audit log is not an audit log.
That is also why the log is exempt from the organization's retention window. The window decides how long conversations, telemetry, and usage records are kept. The record of what happened is kept for the life of the agreement. See How an organization manages its data.
The reads are audited too
Two things worth knowing beyond the settings:
- Reading the conversation archive writes an entry naming the reader, what they filtered on, and what they searched for. Members can see that their conversations are being recorded, and that the record was read. See Read and export the conversation archive.
- Changing a data setting is recorded with the name of the person who changed it, and so is the acknowledgement when content logging is turned on.
Who can read it
The roles that administer the organization can read the log, and the auditor role exists for this: it reads everything in the dashboard and changes nothing, which is what an external reviewer or an internal controls team usually needs.
Related articles
- Roles and permissionsThe six roles in a Dropstone organization, what each one may do, why reading member conversations is deliberately not an administrator power, how administrators are appointed, and what the gold verified mark means.
- Your organization dashboardWhat each section of your organization dashboard holds, from members and teams to usage, billing, policies, the audit log, and the conversation archive. And who can see which part.
- How an organization manages its dataThe three settings an owner controls for an organization, what each one stores, who can read it, and the limits of the strongest setting. Content logging, product telemetry, and retention, in one place.
- Read and export the conversation archiveWho can read an organization's recorded conversations, how to search and filter them, what the archive never holds, and how to export it as JSONL.
- SCIM provisioningAutomate joiners, leavers, and team membership in Dropstone from your identity provider using SCIM 2.0. Users and groups are supported. Deprovisioning is a soft delete.
- How Dropstone handles your dataWhat Dropstone stores, for how long, who can see it, whether it is used to improve the models, and the commitments that apply to every account. A plain-language summary of Dropstone's data practices.