Entities And Multi Tenancy

A SaaS app has thousands of end users. The team wires the agent so every user's actions run under one shared entity.

Map each end user to a distinct, stable entity_id (e.g. the app's user id) so connections and executions are isolated per user. A single shared entity collapses every user's connections into one identity and breaks isolation.

An execute call is issued without specifying entity_id. Composio applies a default entity.

Treat omission of entity_id as a bug in any multi-tenant flow: it falls back to a default/shared entity. Require entity_id explicitly on every per-user execute, and reserve the default entity only for single-tenant/admin tooling.

A single user connects Gmail, GitHub, and Slack. The agent must pick the right connection per action.

Within one entity, resolve the connection matching the action's app/toolkit (GITHUB_* -> the GitHub connection). Do not assume one connection per entity; select by app and confirm it is ACTIVE before executing.