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): tighten raw-tokens section

Anshu Garga4aa8dc22d72
diff --git a/docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx b/docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx
index 8cd5486a9..a1938fdf6 100644
--- a/docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx
+++ b/docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx
@@ -66,15 +66,13 @@ The same treatment applies to the `data`, `params`, and `headers.Authorization`
- [`GET /api/v3/connected_accounts`](https://docs.composio.dev/rest-api/connected-accounts/get-connected-accounts)
- [`POST /api/v3/connected_accounts`](https://docs.composio.dev/rest-api/connected-accounts/post-connected-accounts)
-## If your workflow reads tokens directly
+## If you need raw tokens
-A small number of workflows — typically those that call provider APIs outside of Composio's execution path — read `access_token` or `refresh_token` from the connected-accounts response. If that's you, the recommended path is to connect through an auth config you own. Tokens issued against your OAuth application belong to you, and the connected-accounts API returns them in full (subject to your project's masking setting).
+To keep reading `access_token` or `refresh_token` from API responses, connect through your own auth config. Tokens issued against an OAuth application you own are returned in full (subject to your project's masking setting).
-Getting set up:
-
-1. Register an OAuth application with the provider — for Gmail, you can start in the [Google Cloud Console](https://console.cloud.google.com/apis/credentials).
+1. Register an OAuth application with the provider — for Gmail, start in the [Google Cloud Console](https://console.cloud.google.com/apis/credentials).
2. [Create a custom auth config](https://docs.composio.dev/rest-api/auth-configs/post-auth-configs) using those credentials.
-3. Create new connections against that auth config. Response fields behave as they always have for customer-owned configs.
+3. Create new connections against that auth config.
<Callout type="info">
**No action is needed for most teams.** If you build on the Composio SDK, Tool Router, or MCP, your integrations keep working as-is. If your application reads `access_token` or `refresh_token` directly from a Composio-managed connection, moving those connections onto a custom auth config preserves the previous response shape.