Skip to content

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(changelog): elevate the project-scoping section

Anshu Garg373b050d0fe8
diff --git a/docs/content/changelog/04-18-26-webhook-triggers-v2.mdx b/docs/content/changelog/04-18-26-webhook-triggers-v2.mdx
index aa7213e3a..3c262bee2 100644
--- a/docs/content/changelog/04-18-26-webhook-triggers-v2.mdx
+++ b/docs/content/changelog/04-18-26-webhook-triggers-v2.mdx
@@ -128,23 +128,23 @@ curl -X POST "https://backend.composio.dev/api/v3/trigger_instances/SLACK_CHANNE
Creating a V2-only slug without a matching `webhook_endpoint` returns `400` with a `suggestedFix` pointing to `POST /api/v3/webhook_endpoints`.
-## Constraint: one OAuth app, one project
-
-`webhook_endpoints` uniqueness is `(toolkit_slug, project_id, client_id)`. More importantly, the provider dashboard accepts exactly **one callback URL per OAuth app**, and each V2 URL resolves to a single project.
+## Heads up: OAuth apps are project-scoped on V2
<Callout type="warn">
-An OAuth app (`client_id`) on V2 can effectively serve only one Composio project. If the same OAuth app is currently shared across multiple projects or organizations on V1, either pick one project to own it on V2 or register separate OAuth apps per project.
+**Action required if you share a single OAuth app across multiple Composio projects or organizations today.** V2 ties each OAuth app (`client_id`) to exactly one project. Before moving such an app to V2, either consolidate to a single project or register separate OAuth apps per project.
</Callout>
-Scoping V2 endpoints to a single project gives each project:
+The provider dashboard accepts only one callback URL per OAuth app, and each V2 URL resolves to exactly one project — so a single OAuth app cannot feed multiple projects on V2.
+
+Project-scoped endpoints give each project:
-- Its own ingress rate-limit and backpressure budget
-- Isolated fan-out — events reach only that project's trigger instances
-- Isolated signing secret and app-level token storage
+- A dedicated ingress rate-limit and backpressure budget
+- Clean fan-out — events reach only that project's trigger instances
+- A signing secret and app-level token scoped to this project alone
- Accurate per-project metering and billing
- Independent teardown, rotation, and verification state
-V1's shared endpoint continues to work for any OAuth app left on V1, with no change in behavior.
+Your V1 endpoints are unaffected. Any OAuth app you leave on V1 continues to work across projects exactly as it does today.
## Backward compatibility