Skip to content

DocsEnterprise

Organisations

Several teams on one deployment, each seeing only its own repositories and managing only its own people.

What an organisation is

  • Every principal belongs to one organisation. Until you create another, everyone is in default.
  • A principal sees only its own organisation's repositories. Another organisation's read as missing from every REST route and MCP tool.
  • Each organisation can have a repository of the same name: Acme's backend is stored as acme/backend. Repositories in default keep their bare names.
  • Seats count across all organisations.

Create one

terminal
# As a deployment administratorbbm-atlas enterprise organizations create acme --name "Acme Corp"bbm-atlas enterprise principals create-user boss@acme.example --organization acme --role administratorbbm-atlas enterprise organizations list

The console's Organisations page does the same. People who sign in through single sign-on join the organisation the method names (BBM_ATLAS_EE_OIDC_ORGANIZATION, BBM_ATLAS_EE_SAML_ORGANIZATION).

Who manages what

WhoSees and manages
The deployment's administrators: admin keys, Administrators of defaultEvery organisation; they create organisations
An organisation's AdministratorsTheir own organisation's people, keys and audit records
Everyone elseWhat their roles allow, in their own organisation

If the licence lapses

Organisations can't be managed without an active licence, but they stay apart: a repository's recorded owner still decides who sees it. Nothing is deleted, and a renewed key restores management.