@devries-cameron20 / composio-1 / commits / a56586224
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.

docs: add white-labeling FAQs to common FAQ page

Add three new FAQ entries for commonly asked white-labeling questions: - Is white labeling available on the free plan? - How do I hide the Composio logo during authentication? - I changed my branding but still see 'Secured by Composio' Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Sushmitha Mallesh committed Mar 4, 2026 at 22:23 UTC a565862244a97649cb98448242b3c5d04d2862e6
1 file changed +12
docs/content/docs/common-faq.mdx
+12
@@ -12,6 +12,18 @@ Yes. By default, OAuth consent screens show "Composio" as the app name. If you c
12 You can also proxy the OAuth redirect through your own domain so users never see `backend.composio.dev` in the URL bar. See [White-labeling authentication](/docs/white-labeling-authentication).
13 </Accordion>
14
15 +<Accordion title="Is white labeling available on the free plan?">
16 +Yes. White labeling works on all plans, including free. You can create custom auth configs with your own OAuth credentials on any account. See [White-labeling authentication](/docs/white-labeling-authentication).
17 +</Accordion>
18 +
19 +<Accordion title="How do I hide the Composio logo during authentication?">
20 +Go to your [project settings](https://platform.composio.dev/settings) and upload your own logo and app title. This replaces Composio branding on the Connect Link page. To also remove "Composio" from OAuth consent screens (Google, GitHub, Slack, etc.), create a custom auth config with your own OAuth credentials. See [White-labeling authentication](/docs/white-labeling-authentication) for the full guide.
21 +</Accordion>
22 +
23 +<Accordion title="I changed my branding but still see 'Secured by Composio'">
24 +The Connect Link logo and app title customization does not remove the "Secured by Composio" badge. To remove it, you need to set up your own OAuth app by creating a [custom auth config](/docs/white-labeling-authentication#using-your-own-oauth-apps) with your own client ID and secret.
25 +</Accordion>
26 +
27 <Accordion title="What is the difference between a tool and a toolkit?">
28 A **toolkit** is a collection of related tools grouped by app, for example the GitHub toolkit or the Gmail toolkit. A **tool** is a single action within a toolkit, like `GITHUB_CREATE_ISSUE` or `GMAIL_SEND_EMAIL`.
29