@devries-cameron20 / composio Mirror · read-only / commits / c5c9f4359
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.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 22, 08:15 UTC

docs: restore connected accounts and token expiry accordions

Only the auth config accordion was meant to be removed. Restore the connected accounts and token expiry accordions that were accidentally removed. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Sushmithamallesh committed Feb 19, 2026 at 12:07 UTC c5c9f435916e4dbd792936b371a232baea1ada36
1 file changed +11 -1
docs/content/docs/authentication.mdx
+11 -1
@@ -62,12 +62,22 @@ Composio handles this automatically:
62 2. The auth config is reused for all users authenticating with that toolkit
63 3. Connected accounts are created and linked to your users
64
65 -Most toolkits work out of the box with **Composio managed OAuth**. For API key-based toolkits, users enter their keys directly via Connect Link. Composio automatically refreshes OAuth tokens before they expire — you don't need to handle re-authentication.
65 +<Accordions>
66 +<Accordion title="What are connected accounts?">
67 +A connected account is created when a user authenticates with a toolkit. It stores the user's credentials (OAuth tokens or API keys) and links them to your user ID. Each user can have multiple connected accounts, even for the same toolkit (e.g., work and personal Gmail).
68 +</Accordion>
69 +<Accordion title="What happens when tokens expire?">
70 +Composio automatically refreshes OAuth tokens before they expire. You don't need to handle re-authentication or token expiration. Connected accounts stay valid as long as the user doesn't revoke access.
71 +</Accordion>
72 +</Accordions>
73 +
74 +Most toolkits work out of the box with **Composio managed OAuth**. For API key-based toolkits, users enter their keys directly via Connect Link.
75
76 You only need to create a custom auth config when:
77 - You want to use your **own OAuth app credentials** for white-labeling
78 - You need **specific OAuth scopes** beyond the defaults
79 - The toolkit doesn't have Composio managed auth
80 +- You have **existing auth configs** with connected accounts you want to use
81
82 To bring your own OAuth apps or customize scopes, see [custom auth configs](/docs/using-custom-auth-configuration).
83