Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | ## Project settings control one project |
| 2 | |
| 3 | Open **Platform → Settings** for the selected project. The current project |
| 4 | settings pages are **General**, **API Keys**, **Webhooks**, **White Labeling**, |
| 5 | and **Usage**. |
| 6 | |
| 7 | - **API Keys** creates or revokes project keys and manages any key-level IP |
| 8 | allowlist. Copy a newly created secret into the customer's secret manager; |
| 9 | never ask for it in support. |
| 10 | - **Webhooks** manages the project webhook endpoint and signing secret. |
| 11 | - **White Labeling** controls the hosted authentication screen. Provider OAuth |
| 12 | consent-screen branding still requires the customer's own provider app. |
| 13 | - **Usage** shows project-level usage rather than organization-wide usage. |
| 14 | |
| 15 | ## Organization settings control the organization |
| 16 | |
| 17 | The organization settings pages are **General**, **Members**, **Billing**, |
| 18 | **Usage**, and **Account Settings**. Use them for organization identity, |
| 19 | membership, plan and usage information, account security, and organization |
| 20 | deletion. Confirm whether the customer intends to change one project or the |
| 21 | whole organization before directing them to a destructive control. |