Skip to main content
An organization is the unit of governance in Danube. Members share the organization’s connected tools, its access policies apply to every agent that calls through a member’s key, and every call lands in the organization’s audit log. Every account starts with a personal organization. Creating a company organization moves your team onto shared governance without changing how agents connect: the same API keys, the same MCP endpoint.

​
Roles

Roles are ordered by privilege. A higher role can do everything a lower one can.

​
Set up an organization

1

Create the organization

Go to Dashboard > Organization and click Create organization. Give it a name; the URL slug is derived from the name unless you set one.
2

Add members

Members are added by the email address of an existing Danube account, with a role. There is no invitation email in this release: ask teammates to sign up at danubeai.com first, then add them.
3

Create teams (optional)

Teams group members inside an organization so that access policies can target a team instead of individuals. Each team has a lead and members.
4

Switch context

The organization switcher in the dashboard header controls which organization you are acting in. Tools you connect, keys you create, and policies you edit belong to the active organization.

​
How organizations change tool access

  • Shared credentials. A service connected inside an organization is available to every member the policies allow, without each person connecting it again.
  • Internal tools. Services created with the Connector Builder or marked internal are visible only to members of the organization, never in the public catalog.
  • Policies. With no policies, every member has full access. Adding the first policy switches the organization to deny-by-default for members. See Tool Access Policies.
  • Audit. Every execution, denial, membership change and policy change is recorded. See Audit Log.

​
Plans

Organizations carry a plan (free, team, or enterprise) that is separate from an individual account’s subscription. See Plans & Billing for what each tier includes and how to upgrade.

​
Endpoints

All organization endpoints live under /v1/organizations and accept the same authentication as the dashboard (a session token) or an API key. Member operations take the Danube user id of the member. Adding a member takes {"email": "...", "role": "member"}.