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: clarify that Composio creates auth configs, not the user

Sushmithamallesh476d38ef88bf
diff --git a/docs/content/docs/authentication.mdx b/docs/content/docs/authentication.mdx
index 9901e380a..997871edc 100644
--- a/docs/content/docs/authentication.mdx
+++ b/docs/content/docs/authentication.mdx
@@ -46,7 +46,7 @@ An **auth config** is a blueprint that defines how authentication works for a to
- **Scopes** — what actions your tools can perform
- **Credentials** — your own app credentials or Composio's managed auth
-You create one auth config per toolkit, and it applies to every user who connects that toolkit. When a user authenticates, Composio creates a **connected account** that stores their credentials (OAuth tokens or API keys) and links them to your user ID.
+Composio creates one auth config per toolkit, and it applies to every user who connects that toolkit. When a user authenticates, Composio creates a **connected account** that stores their credentials (OAuth tokens or API keys) and links them to your user ID. If you want to create your own auth configs, see [custom auth configs](/docs/using-custom-auth-configuration).
```mermaid
graph LR