@devries-cameron20 / composio-1 / commits / 01a6b015b
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

docs(security): add an audit logs page (#5247)

## Summary Adds a docs page for audit logs, which organization admins open in **Organization Settings > Audit logs**. The page covers how to view and filter events, what each event shows, what audit logs record and don't record, and how far back they go on each plan. ## Changes - `security/audit-logs.mdx` is the new page. - `security/meta.json` adds the page to **Security and data**, after the overview. `tests/static/product-navigation.test.ts` pins the new sidebar order. - `security/overview.mdx` links to the page from **Isolation and access control**. - `changelog/11-05-26-audit-logs.mdx` is the launch entry. ## Type of change - [x] Documentation ## How has this been tested? - `bun test tests/static/` gives 822 pass and 5 fail. All 5 failures are in `content-freshness.test.ts`, and they fail the same way on a clean `next` checkout on my machine. - `bun scripts/validate-links.ts` reports 0 errors. - I rendered the page with `next dev` at desktop width and at 375px, with no sideways scroll, and checked its `.md` output. The dashboard link uses the `/~/org` go-link with UTM parameters. ## Before merging - [ ] The audit logs page is available to every organization in the dashboard. - [ ] The dashboard limits Hobby organizations to the last 30 days of events. - [ ] Rename the changelog file and set its `date` to the release date. Co-authored-by: Alberto Schiabel <jkomyno@users.noreply.github.com>

Shubham Mehta committed Nov 9, 2026 at 03:07 UTC 01a6b015b84298fb879999ffda3a5d0e464250ca
5 files changed +78
docs/content/changelog/11-05-26-audit-logs.mdx new
+16
@@ -0,0 +1,16 @@
1 +---
2 +title: "See who changed your organization in audit logs"
3 +description: "Organization admins can review changes to members, projects, API keys, webhook subscriptions, and session configs in Organization Settings > Audit logs."
4 +date: "2026-11-05"
5 +---
6 +
7 +Organization admins can now see who changed their organization and when in **Organization Settings > Audit logs**. Each event names the member who made the change, describes it in one sentence, and shows the IP address and source of the request, such as the dashboard, an API key, or the CLI.
8 +
9 +### What's new
10 +
11 +- Audit logs record changes to the organization, its members and invites, projects and project settings, API keys, webhook subscriptions, and session configs.
12 +- Changes that Composio makes, such as a plan change by Composio support, appear with **Composio** as the member.
13 +- You can filter events by time range, member, and event type.
14 +- On the Hobby plan, audit logs cover the last 30 days. On paid plans, they cover the last 12 months.
15 +
16 +See [Audit logs](/docs/security/audit-logs) for what audit logs record and what they don't.
docs/content/docs/security/audit-logs.mdx new
+59
@@ -0,0 +1,59 @@
1 +---
2 +title: Audit logs
3 +description: See who changed your organization's members, projects, API keys, webhook subscriptions, and session configs, and when.
4 +keywords: [audit logs, audit trail, activity log, change history, organization admin, compliance, security, retention]
5 +---
6 +
7 +Audit logs show who changed your organization and when. Composio records an event each time someone changes your organization or its members, projects, API keys, webhook subscriptions, or session configs. It records changes made in the dashboard, through the API, and with the CLI.
8 +
9 +Use audit logs to find out who revoked an API key, who turned off two-factor authentication for a project, or what a member changed before they left your team.
10 +
11 +<Callout type="info">
12 +Only organization admins can view audit logs.
13 +</Callout>
14 +
15 +## View audit logs
16 +
17 +1. In the dashboard, open [**Organization Settings > Audit logs**](https://dashboard.composio.dev/~/org/settings/audit-logs?utm_source=docs&utm_medium=content&utm_campaign=docs-audit-logs).
18 +2. Choose a time range. The page opens on the last 7 days, with the newest events first.
19 +3. To narrow the list, filter by member or by event.
20 +
21 +For example, filter by one member to see everything they changed. Filter by **Member removed** to see who removed people from your organization.
22 +
23 +## What each event shows
24 +
25 +| Column | What it shows |
26 +| --- | --- |
27 +| **Time** | When the change happened. |
28 +| **Member** | The current email of the member who made the change. A change made with an API key shows the member the key belongs to. |
29 +| **Event** | What changed, in one sentence, such as "Revoked API key ci-deploy" or "Renamed project to support-bot". |
30 +| **IP** | The IP address the request came from, when Composio has one. |
31 +| **Source** | How the change was made, such as **Dashboard**, **Project API key**, **Org API key**, **User API key**, or **CLI**. |
32 +
33 +Changes that Composio makes, such as a plan change by Composio support, show **Composio** as the member and no IP address. If a member's account was deleted, their events show **Deleted member**. When someone reports a leaked API key through the [key revocation endpoint](/reference/api-reference/api-keys/postApiKeyRevocation), Composio revokes the key, and the event shows **Leaked key report** as the member and the source.
34 +
35 +When one change revokes several keys, the log shows a single summary event next to it. For example, removing a member who owns three project API keys records the removal and a second event, "Revoked 3 API keys".
36 +
37 +## What audit logs record
38 +
39 +| Area | Recorded changes |
40 +| --- | --- |
41 +| Organization | Creating, renaming, deleting, or restoring the organization, and plan changes made by Composio support |
42 +| Members and invites | Creating or revoking an invite, a member joining, changing a member's role, and removing a member |
43 +| Projects | Creating, renaming, or deleting a project, and changing its settings, such as two-factor authentication, Zero Data Retention, Instant, or triggers |
44 +| API keys | Creating or revoking project API keys and changing their allowed IPs. Regenerating or revoking organization API keys. Creating or revoking user API keys, and approving a CLI login |
45 +| Webhook subscriptions | Creating, updating, or deleting a subscription, and rotating its secret |
46 +| Session configs | Creating, updating, archiving, or restoring a session config |
47 +
48 +## What audit logs don't record
49 +
50 +Audit logs cover changes to how your organization is set up, so they don't record the following.
51 +
52 +- Tool calls, sessions, and trigger events. These appear in your project's logs, which you can also [stream to a SIEM](/docs/poc-to-prod/stream-logs-to-a-siem).
53 +- Changes to connected accounts, auth configs, and triggers.
54 +- Sign-ins, and requests that fail or change nothing.
55 +- Plan changes you make in **Organization Settings > Billing**.
56 +
57 +## How far back audit logs go
58 +
59 +On the Hobby plan, audit logs cover the last 30 days. On paid plans, they cover the last 12 months.
docs/content/docs/security/meta.json
+1
@@ -3,6 +3,7 @@
3 "defaultOpen": false,
4 "pages": [
5 "overview",
6 + "audit-logs",
7 "token-custody",
8 "data-retention",
9 "zero-data-retention"
docs/content/docs/security/overview.mdx
+1
@@ -16,6 +16,7 @@ Composio is SOC 2 Type II compliant. For our latest reports and certifications (
16 - API keys are scoped, support per-key IP allowlisting, and can opt in to capabilities such as Proxy Execute at creation.
17 - Scoped project API keys separate **Session management** (creating, viewing, configuring, and deleting sessions) from **Session tool execution** (search, tool execution, proxy execution, and session-linked MCP access). See [API key permissions](/reference/authenticating-to-composio/project-api-key-permissions) to configure access.
18 - Multi-factor authentication (MFA) is available for Dashboard sign-in and can be enforced by an organization admin.
19 +- Organization admins can see who changed members, projects, API keys, and other settings in [audit logs](/docs/security/audit-logs).
20
21 ## Credential protection
22
docs/tests/static/product-navigation.test.ts
+1
@@ -175,6 +175,7 @@ describe('Docs product navigation', () => {
175
176 const securityUrls = [
177 '/docs/security/overview',
178 + '/docs/security/audit-logs',
179 '/docs/security/token-custody',
180 '/docs/security/data-retention',
181 '/docs/security/zero-data-retention',