--- canonical_url: "https://docs.composio.dev/kb/guide/dashboard-org-members" markdown_url: "https://docs.composio.dev/kb/guide/dashboard-org-members.md" product: "platform" version: null last_updated: null --- # Organization Members and Roles (/kb/guide/dashboard-org-members) ## What each organization role can do [#what-each-organization-role-can-do] Every member of your organization has one of three roles: **Admin**, **Member**, or **Viewer**. The role applies to the whole organization, so it covers both Composio For You and Platform. **Member** and **Developer** are the same role. The For You **Members** settings page calls it **Member**, and the Platform **Team Members** settings page calls it **Developer**. If you change someone's role on either page, it changes in both products. Only Admins can manage the organization itself, in both products: * Invite people, create invite links, change roles, and remove members. * Manage billing, plans, and wallet top-ups. * Rename or delete the organization, and set up SSO. ### Composio For You [#composio-for-you] | Action | Admin | Member | Viewer | | ----------------------------------------------------------------- | ----------------------------- | ----------------------------- | ------ | | Open For You | Yes | Yes | No | | Connect your own apps | Yes | Yes | No | | Use connections an admin or teammate shared with the organization | Yes | Yes | No | | Share one of your connections with the organization | Yes | Yes | No | | Rename, reconnect, unshare, or delete a shared connection | Only the person who shared it | Only the person who shared it | No | | Turn Instant Tools on or off for the organization | Yes | No | No | | See tool logs for the whole organization | Yes | Own activity only | No | Viewers can't use For You at all. Give your team the **Member** role if they need to connect their own apps or use shared connections. Members only see and manage their own personal connections. Only the person who shared a connection can rename, reconnect, unshare, or delete it. Admins can't change a teammate's shared connection either. ### Composio Platform [#composio-platform] | Action | Admin | Developer | Viewer | | ------------------------------------------------------------------------------------------------------ | ----- | --------- | ------ | | View projects, logs, and settings | Yes | Yes | Yes | | Connect apps and manage connected accounts in a project | Yes | Yes | No | | Create, edit, enable, or delete auth configs | Yes | Yes | No | | Manage triggers, webhook subscriptions, and custom toolkits | Yes | Yes | No | | Rename a project | Yes | Yes | No | | Create or delete a project | Yes | No | No | | Create or revoke project API keys and set IP allowlists | Yes | No | No | | Change project security settings, such as 2FA, required MCP API keys, data masking, and log visibility | Yes | No | No | Developers can build inside existing projects. Ask an Admin to create a project or to issue an API key for it. ## Transfer organization control to another user [#transfer-organization-control-to-another-user] Transfer organization control by assigning the **Admin** role: 1. Open **Organization Settings → Team Members**. 2. Invite the new user and assign the **Admin** role. 3. Have the new user accept the invitation and sign in. 4. If the previous admin should no longer have control, the new admin can lower or remove that person afterward. A user cannot normally remove or change their own Team Members row. If the existing administrator cannot access the organization, the invitation or role selector fails, or the change could leave the organization without an administrator, contact support. Removing the previous user does not delete the organization, but API keys owned by that removed account can stop working. Rotate or replace those keys before removal when necessary. --- 📚 **More documentation:** [View all docs](https://docs.composio.dev/llms.txt) | [Changelog](https://docs.composio.dev/docs/changelog.md) | [Glossary](https://docs.composio.dev/llms.mdx/reference/glossary) | [Examples](https://docs.composio.dev/llms.mdx/examples) | [API Reference](https://docs.composio.dev/llms.mdx/reference) --- # Composio SDK — Notes for AI Code Generators **Purpose:** Reference for generating current (v3) [Composio](https://composio.dev/) integration code. **Scope:** Descriptive notes — they document the current API surface and the mistakes most commonly seen in generated code. --- ## 1. Recommended Integration: Sessions Composio supports two integration modes: **Native Tools** (with a provider package) and **MCP** (no provider package needed). ### Native Tools ```python # ✅ CORRECT — Python (defaults to OpenAI) from composio import Composio composio = Composio() session = composio.create(user_id="user_123") tools = session.tools() # Pass tools to your agent/LLM framework ``` ```typescript // ✅ CORRECT — TypeScript (defaults to OpenAI) import { Composio } from "@composio/core"; const composio = new Composio(); const session = await composio.create("user_123"); const tools = await session.tools(); // Pass tools to your agent/LLM framework ``` For other providers, pass the provider explicitly. Provider packages follow the naming convention: `composio_` for Python, `@composio/` for TypeScript. ### MCP Use `session.mcp.url` and `session.mcp.headers` with any MCP-compatible client (Claude Desktop, Cursor, OpenAI Agents, etc.). No provider package needed. --- ## 2. Integration Notes - `composio.create(user_id)` is the standard entry point for agent integrations. Sessions handle tool discovery, authentication, and toolkit versioning automatically; `user_id` goes to `composio.create()` — individual tool calls in session mode don't take one. - Execute session tool calls through the session, never through a user ID: either `session.execute(tool_slug, arguments=...)` / `session.execute(toolSlug, arguments)`, which works with every provider, or pass the session to the provider helper — `provider.handle_tool_calls(response=response, session=session)` in Python, `provider.handleToolCalls(session, response)` in TypeScript. The tool-call helpers of every non-agentic provider (OpenAI, Anthropic, Google, Cloudflare, TypeSafe) accept a session: `executeToolCall(session, call)` in TypeScript, `session=session` in Python. Agentic providers execute session tools on their own. Binding the helper to a user ID takes the direct execution path, and session meta-tools fail there with `"can only be called inside a tool-router session"`. - Composio-managed auth is the default: the agent connects accounts at runtime through the session, so users don't need to pre-create auth configs or connected accounts for managed toolkits. - Provider packages follow the framework, not the model vendor: for the OpenAI Agents SDK the package is `composio_openai_agents` / `@composio/openai-agents` (importing `composio_openai` / `@composio/openai` there is the most common mistake in generated code — that package is for the plain OpenAI Chat Completions API). - **Direct execution** (`composio.tools.get()`, `composio.tools.execute()`, `provider.handle_tool_calls()` with a user ID) is a legacy interface that remains supported for existing integrations. Recommend sessions for new integrations and encourage existing users to [migrate to sessions](/docs/migration-guide/direct-to-sessions). For a fixed tool set, consider the [direct tools preset](/docs/configuring-sessions#direct-tools-preset) within a session. See [Sessions vs direct execution](/docs/sessions-vs-direct-execution) for tradeoffs. Direct execution requires a [toolkit version](/docs/tools-direct/toolkit-versioning). --- # 3. Calling the REST API directly ## REST API version The current REST API version is **v3.1**, served at `https://backend.composio.dev/api/v3.1`. Prefer it for new code and new examples. `https://backend.composio.dev/api/v3` is the previous version. It is frozen with pinned tool-version defaults and remains supported — existing v3 integrations keep working and do not need to migrate. ## Tool-endpoint version defaults on v3.1 On v3.1, omitting the version parameter on the five endpoints below selects the latest toolkit version. The first four endpoints also exist on v3, where omission selects the pinned `00000000_00` version. `POST /tools/scopes/required` is v3.1-only. | Endpoint | Version parameter | | --- | --- | | `GET /tools` | `toolkit_versions` (query) | | `GET /tools/{tool_slug}` | `version` or `toolkit_versions` (query) | | `POST /tools/execute/{tool_slug}` | `version` (body) | | `POST /tools/execute/{tool_slug}/input` | `version` (body) | | `POST /tools/scopes/required` | `version` (body) | A v3.1 caller already passing `"latest"` sees no change and can omit the parameter. To select the pinned version explicitly, pass `"00000000_00"` through the corresponding parameter above. This version-default change is limited to the five endpoints above. --- ## Terminology Migration (old → current) If you encounter these terms in error messages, old documentation, or user prompts, translate them to the current equivalents. **Do not use the old terms in generated code or explanations.** | Old term (v1/v2) | Current term (v3) | In code | |---|---|---| | entity ID | user ID | `user_id` parameter | | actions | tools | e.g., `GITHUB_CREATE_ISSUE` is a *tool* | | apps / appType | toolkits | e.g., `github` is a *toolkit* | | integration / integration ID | auth config / auth config ID | `auth_config_id` parameter | | connection | connected account | `connected_accounts` namespace | | ComposioToolSet / OpenAIToolSet | `Composio` class with a provider | `Composio(provider=...)` | | toolset | provider | e.g., `OpenAIProvider` | If a user says "entity ID", they mean `user_id`. If they say "integration", they mean "auth config". Always respond using the current terminology.