osFoundry / Platform
Audit log
Who did what, when. Filter by user, action, resource. Export for compliance.
What it is
The audit log is osFoundry's record of activity across your workspace: a time-stamped trail of who did what, when, and to which resource. Every meaningful action leaves an entry — a chat run, an agent execution, a change to an app or a file, an update to a data source or a knowledge item, a membership or settings change. Instead of reconstructing events from memory or scattered histories, you get one chronological source of truth for the whole workspace.
Inside osFoundry the log lives where the work happens: on your device, in the same local-first desktop workspace that holds your chats, agents, apps, code, knowledge, and data. Because osFoundry is bring-your-own-key, the record covers your team's actions in your workspace rather than being scattered across separate vendor consoles. You filter the trail three ways that match how questions actually get asked — by user (what did this person do), by action (show every delete, every export, every settings change), and by resource (everything that touched this file, app, or data source) — and combine them to narrow to the exact window you care about. When someone outside the workspace needs proof, you export the filtered results for compliance, reviews, or incident write-ups.
This matters because an AI workspace touches sensitive things: keys, connected data, knowledge bases, and automated agents that act on their own. When a result looks wrong, a resource changes unexpectedly, or an auditor asks "who approved this," the answer should take seconds, not an afternoon of guessing. A clear, filterable, exportable trail turns those questions into lookups — and it does so without per-seat fees and without shipping your activity history to a third party you don't control.
Key capabilities
- Records who did what, when, and to which resource across the whole workspace in one chronological trail
- Filter by user to see everything a single person did, then narrow by time window
- Filter by action to isolate specific event types — deletes, exports, settings and membership changes
- Filter by resource to trace every event that touched a given file, app, agent, or data source
- Export the filtered log for compliance reviews, audits, and incident write-ups
Use cases
- Compliance lead: pull an exportable trail of exports and permission changes for the last quarter to satisfy an audit request
- Workspace admin: investigate an unexpected change by filtering to the affected resource and reading who touched it and when
- Team lead: review a teammate's activity by user filter to confirm which agents and apps they ran during an incident window
Frequently asked questions
What actions does the audit log capture?
Meaningful activity across the workspace — chat and agent runs, changes to apps, code, files, knowledge, and data sources, plus membership and settings changes. Each entry records the user, the action, the affected resource, and a timestamp so you can answer who did what, when.
Can I export the audit log for compliance?
Yes. Apply the filters you need — by user, action, or resource — and export the resulting trail. That gives you a self-contained record to attach to a compliance review, an audit response, or an incident report.
Where is the audit data stored?
osFoundry is a local-first, bring-your-own-key desktop workspace, so your activity record stays within the workspace you control rather than being spread across separate vendor dashboards. You keep the trail for your own team's actions instead of handing it to a reseller.