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): follow repo guide — h3 sections, relative paths, drop redundant callout

Anshu Garg72c8ff09573b
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 634e7c14e..d952788db 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
@@ -8,20 +8,20 @@ For connections created through a Composio-managed auth config, access tokens, r
**Most integrations need no changes.**
-- Tool execution through the SDK, Tool Router, and MCP is unchanged. Composio continues to handle authentication server-side, so your agents and workflows never needed to read these tokens directly.
-- Connections on your own auth config are unchanged. Token visibility continues to follow your project's masking setting exactly as before.
+- Tool execution through the SDK, Tool Router, and MCP is unchanged. Composio handles authentication server-side, so your agents never needed to read these tokens directly.
+- Connections on your own auth config are unchanged. Token visibility continues to follow your project's masking setting.
-## What is a Composio-managed auth config?
+### What is a Composio-managed auth config?
When you connect a user through a toolkit's default integration — for example, Gmail or Slack without registering your own OAuth application — the connection runs through an OAuth application that Composio owns and operates on behalf of every team using that default. The access and refresh tokens the provider issues are bound to Composio's shared OAuth client.
-You can tell a connection is Composio-managed by the `auth_config.is_composio_managed: true` field on the connected-account resource.
+You can identify a Composio-managed connection by the `auth_config.is_composio_managed: true` field on the connected-account resource.
-## Why this change
+### Why this change
-Because the OAuth application is shared across every team on that default, any action a provider takes on it — rate limits, scope adjustments, or in the extreme case, suspending the OAuth client — affects everyone using it. Keeping the credentials inside Composio protects the reliability of the shared integrations, and tool execution continues to work without any change; Composio uses the tokens server-side.
+Because the OAuth application is shared, any action a provider takes on it — rate limits, scope adjustments, or in the extreme case, suspending the OAuth client — affects everyone using that default. Keeping the credentials server-side protects the reliability of the shared integrations without changing how tool execution works.
-## Example
+### Example
Before, with project masking disabled on a Composio-managed Gmail connection:
@@ -49,22 +49,18 @@ After:
}
```
-The same treatment applies to the `data`, `params`, and `headers.Authorization` fields wherever these values would otherwise appear.
+The same applies to `data`, `params`, and `headers.Authorization` wherever these values would otherwise appear.
-## Affected endpoints
+### Affected endpoints
-- [`GET /api/v3/connected_accounts/{id}`](https://docs.composio.dev/rest-api/connected-accounts/get-connected-accounts-by-nanoid)
-- [`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)
+- [`GET /api/v3/connected_accounts/{id}`](/reference/api-reference/connected-accounts/getConnectedAccountsByNanoid)
+- [`GET /api/v3/connected_accounts`](/reference/api-reference/connected-accounts/getConnectedAccounts)
+- [`POST /api/v3/connected_accounts`](/reference/api-reference/connected-accounts/postConnectedAccounts)
-## If you need raw tokens
+### If you need raw tokens
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).
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.
+2. [Create a custom auth config](/reference/api-reference/auth-configs/postAuthConfigs) using those credentials.
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.
-</Callout>