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): drop redundant change-matrix table

Anshu Garg99f61eb7714f
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 a1938fdf6..634e7c14e 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
@@ -21,16 +21,7 @@ You can tell a connection is Composio-managed by the `auth_config.is_composio_ma
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.
-## What changes in the API
-
-| Connection type | Project masking setting | Tokens in response |
-|---|---|---|
-| Composio-managed | On | Masked (unchanged) |
-| Composio-managed | Off | **Masked (new behavior)** |
-| Your own auth config | On | Masked (unchanged) |
-| Your own auth config | Off | Returned in full (unchanged) |
-
-### Example
+## Example
Before, with project masking disabled on a Composio-managed Gmail connection:
@@ -60,7 +51,7 @@ After:
The same treatment applies to the `data`, `params`, and `headers.Authorization` fields 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)