Organizations

An organization is the unit of collaboration in the platform. It groups users who share access to the same set of projects and other resources.

How Organizations Are Created

Organizations are not created in the FDK server directly. They come from your identity provider (IDP) — the same Keycloak or Entra ID realm that handles login.

When a user signs in for the first time, the server reads the organizations that the user belongs to from the IDP’s token and provisions them automatically:

• If an organization in the token does not yet exist on the server, it is created.
• The user is registered as a member of every organization their token lists.
• Subsequent sign-ins keep the user’s organization list in sync with the IDP.

This means you manage org membership where you already manage your users — in your IDP — and the FDK server reflects whatever the IDP says.

Belonging to Multiple Organizations

A user can belong to more than one organization at the same time. This is common in consulting or partner scenarios, where one person collaborates with several customer orgs.

When a user belongs to multiple organizations, the platform asks them to choose which organization to act under when they create a new resource. That choice determines which org owns the resource and, by default, who else on the team can see it.

Why Organizations Matter

Every resource you create — a project, a dataset, an analysis — is owned by exactly one organization. The owning organization is what makes “share with my team” possible without inviting people one-by-one. See Access Control for how this plays out at the resource level.