@devries-cameron20 / composio Mirror · read-only
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.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 06:00 UTC

next
md 62 lines 3.33 KB
Rendered Raw
1 ---
2 type: "reference"
3 title: "Current Support FAQs"
4 description: "Public answers for recurring Composio support issues."
5 category: "authentication"
6 visibility: "public"
7 timestamp: "2026-07-14T12:55:03Z"
8 tags:
9 - "faq"
10 - "faqs"
11 ---
12 # Current Support FAQs
13
14 ## Route toolkit requests and toolkit partnership applications
15
16 The same public request board covers all three request types:
17
18 - a new toolkit or integration;
19 - a missing tool or action in an existing toolkit;
20 - a missing trigger or event in an existing toolkit.
21
22 Direct all three to https://request.composio.dev/boards/tool-requests. Ask them to include the provider or toolkit, the exact tool/action/API endpoint or trigger/event, and their use case. Do not send one of these request types somewhere else, and do not promise an ETA. If the request type is unclear, ask one focused clarification so they can file it with the right details.
23
24 When a company wants its own product added to Composio, direct a representative
25 with a company work email and product details to
26 https://composio.dev/partnerships#apply instead. The public partnership form asks
27 for company, product, and proposed-journey context. Do not treat unrelated sales,
28 SEO, recruiting, or sponsorship pitches as toolkit-partnership requests.
29
30 ## Security, privacy, data-retention, and compliance information
31
32 Direct general security, privacy, data-retention, audit, and compliance questions to https://trust.composio.dev/. Do not infer or restate policy details that are not present in approved public material. If the Trust Center does not answer the customer's question, offer human follow-up. Use the documented Dashboard self-service path for ordinary organization deletion. Substantive vulnerability details, legal data-erasure requests beyond that flow, legal requests, and customer-specific access questions still require specialist review.
33
34 ## Security reporting
35
36 If you believe you have found a potential security vulnerability in Composio,
37 please report it privately through the channels in our
38 [security policy](https://github.com/ComposioHQ/composio/security/policy). A
39 private GitHub Security Advisory is the preferred route, with
40 `security@composio.dev` available as an email alternative.
41
42 Include enough detail to help the team reproduce and assess the finding, but do
43 not include customer data, credentials, or other secrets.
44
45 ## Google `access_not_configured` requires a Workspace for Education administrator
46
47 Google documents `400 access_not_configured` as a Workspace for Education app
48 access-policy error. The institution's Workspace administrator must configure
49 access for the app; changing Composio scopes or repeatedly reconnecting does not
50 resolve that policy decision.
51
52 If the organization allows users to request access, the user can submit the
53 request from Google's error page. An administrator with the required Security
54 settings privilege can review pending requests or configure the exact OAuth
55 client under **Security → Access and data control → API controls → Manage
56 App Access**. The administrator should use the access level and organizational
57 unit appropriate for the institution. Google says policy changes can take up to
58 24 hours, though they usually apply sooner.
59
60 Do not generalize this code to every Google Workspace account. Distinguish it
61 from `admin_policy_enforced`, `access_denied`, and unverified-app errors before
62 giving instructions.