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 | --- |
| 2 | type: "guide" |
| 3 | title: "Platform project settings" |
| 4 | description: "Current navigation for Platform project configuration and organization settings." |
| 5 | category: "account-and-billing" |
| 6 | visibility: "public" |
| 7 | timestamp: "2026-08-17T00:00:00Z" |
| 8 | tags: |
| 9 | - "dashboard" |
| 10 | - "settings" |
| 11 | --- |
| 12 | # Platform project settings |
| 13 | |
| 14 | ## Project settings control one project |
| 15 | |
| 16 | Open **Platform → Settings** for the selected project. The current project |
| 17 | settings pages are **General**, **API Keys**, **Webhooks**, **White Labeling**, |
| 18 | and **Usage**. |
| 19 | |
| 20 | - **API Keys** creates or revokes project keys and manages any key-level IP |
| 21 | allowlist. Copy a newly created secret into the customer's secret manager; |
| 22 | never ask for it in support. |
| 23 | - **Webhooks** manages the project webhook endpoint and signing secret. |
| 24 | - **White Labeling** controls the hosted authentication screen. Provider OAuth |
| 25 | consent-screen branding still requires the customer's own provider app. |
| 26 | - **Usage** shows project-level usage rather than organization-wide usage. |
| 27 | |
| 28 | ## Organization settings control the organization |
| 29 | |
| 30 | The organization settings pages are **General**, **Members**, **Billing**, |
| 31 | **Usage**, and **Account Settings**. Use them for organization identity, |
| 32 | membership, plan and usage information, account security, and organization |
| 33 | deletion. Confirm whether the customer intends to change one project or the |
| 34 | whole organization before directing them to a destructive control. |