Audit logs - Lovable Documentation
Documentation Index Fetch the complete documentation index at: /llms.txt Use this file to discover all available pages before exploring further. Skip to main content Assistant Responses are generated using AI and may contain mistakes. Audit logs provide a searchable audit trail of activity in your workspace. They show who performed an action, when it happened, what changed, and which resource was affected. Use audit logs to review workspace settings and configuration changes, track access updates, and investigate unexpected behavior.
Audit logs can also support security and compliance workflows when needed. Available on: Enterprise plans Access: Workspace admins and owners Location: Audit logs ( Workspace settings → Security → Audit logs ) Enterprise organizations have their own Audit logs page in organization settings. That page shows organization-level actions and the audit events of every workspace in the organization, and you can filter by workspace.
See Review activity across the organization . Audit log events Workspace audit logs include events across categories such as: Category Example events Workspace membership Member added, removed, or role updated Workspace management Workspace settings updated Workspace ownership transferred Workspace deleted Publishing domain connected or disconnected Workspace groups Group created, updated, or deleted Group members added or removed Identity and access Verified domain added or removed SSO provider added, updated, or removed SCIM provisioning actions API key created, updated, or revoked Request refused by an API key’s IP allowlist Secrets and integrations GitHub or Slack app installed or removed on workspace Custom MCP server created or deleted Secrets changed Projects Project created, deleted, restored, published, unpublished, or moved Collaborators added, joined, removed, or their role updated Custom domains created or deleted Supabase project or Shopify store connected or disconnected Prompt sent Knowledge updated Database query executed Remix initiated Lovable Cloud Project auth settings updated Cloud auth users created, invited, or deleted Storage buckets created or deleted Cloud storage upload limit updated Disk configuration updated Database password rotated Authentication SSO workspace access SSO identity token issued or refreshed User logged out everywhere (all sessions revoked from account settings ) This table shows common examples.
The All actions filter on the audit logs page lists the full set of event types recorded for your workspace. Audit log table By default, the page shows logs for All actions , All actors , and the Last 90 days . The total number of matching logs appears in the top right of the table. The table is organized into four columns: Column Description Timestamp When the event occurred, such as 4 minutes ago or about 11 hours ago .
Hover to see the exact date and time. Actor The member who performed the action. Clicking the member’s name opens a popover showing their Email , User ID , the Client the event came from, IP Address , and User Agent . The Client line is left out when no client was recorded, and names are only clickable for events performed by a member. From this popover, you can copy these details or filter the table by that user. Action The type of activity, displayed as a label such as Prompt sent , Workspace updated , Member added , or Project created .
Resource The affected object, such as a project, workspace, or user. Some resources are clickable. For example, clicking a project name opens that project. Click any row to expand it and see structured JSON details describing the event. This includes the metadata associated with that action, such as message IDs for prompt activity or specific fields that were updated in a workspace setting. Events triggered through the Lovable API are also attributed to the access token that made the request.
The expanded JSON details include an api_key_id field alongside the acting user, so you can trace which token drove a given change. When a project is published, the publishing event ( Project published externally , Project published internally , or Project published from Slack ) also includes a commit_sha field. The field identifies the version of the project’s code that was published, so you can trace each published app back to its code.
Lovable records the field for every way to publish: the Publish dialog, the Lovable API, Lovable in Slack , and the project chat when you ask Lovable to publish. Publishing attempts that did not go through, and earlier publishing events, do not include it. Filtering audit logs You can combine the filters to focus on specific activity: All actions lets you select one or more action types, such as Member added , Member removed , Workspace updated , Project created , or Prompt sent .
The dropdown is searchable. All actors lets you select one or more workspace members using the searchable picker. Resources lets you search for projects and people and show only events that affected them. All clients lets you select one or more client platforms to show only events performed from those apps: Web , Desktop app , iOS app , Android app , or Unknown . Unknown covers events recorded before Lovable started tracking the client platform on August 24, 2026, and events that did not come from one of these apps, such as automated SCIM provisioning.
Time range includes presets for Last 7 days , Last 30 days , Last 90 days , This month , and Last month . Your filter selections are reflected in the page URL, so you can share a filtered view with another admin or reload the page without losing it. How to use audit logs A typical workflow: Set a relevant time range . Filter by actor to review activity from a specific member. Filter by action type to narrow results to a specific kind of change.
Expand entries to inspect the full JSON details. Open affected projects or jump to related messages to review context. Use the actor popover to copy details such as email, user ID, IP address, or user agent, or to check which client the event came from. Exporting audit logs Click Export in the top right of the page, then click Start new export . Lovable generates a JSONL file (one JSON event per line) of the audit logs matching your active action, actor, and time range filters, and packages it for download as audit_logs.jsonl.zip .
Finished exports stay available for download for 7 days, and each export is itself recorded in the audit log. Each exported event includes a client_platform field identifying the app the event came from, such as web , ios , android , or desktop-app . Exports created before client tracking was introduced do not include this field. Export is not available while a resource or client filter is active. Exports cannot yet filter by these, so the Export button is disabled with the reason shown as its hint.
Clear the Resources or client filter first. To send audit logs to a SIEM or your own storage on a schedule, set up a data export . Audit log data retention Logs are retained for 13 weeks, or approximately 90 days. Events older than that are automatically removed. To keep audit logs longer, export them to your own storage with data exports . Logs before February 26, 2026 may be incomplete. FAQ Who can access audit logs?
Audit logs are available on Enterprise plans and are visible to workspace owners and admins. How long are audit logs retained? Audit logs are retained for 13 weeks, or approximately 90 days. Events older than that are automatically removed. Can I export audit logs? Yes. Click Export in the top right of the audit logs page to download your audit logs as a JSONL file, packaged as audit_logs.jsonl.zip . The export matches your active action, actor, and time range filters, and finished exports stay available for download for 7 days.
Export is not available while a resource or client filter is active. To send audit logs to a SIEM or external storage on a schedule, use data export
The rest of this page is on the live site.