An organization is the container for people and the Business Units they work on. Every Nimbus account belongs to at least one organization, and organizations are how access scales beyond a single team.
| Type | For |
|---|---|
| **Client** | A company that runs its own marketing in its own SFMC Business Units. |
| **Agency** | A company that manages SFMC for other companies. |
You choose the type during onboarding. It mainly affects defaults and the plans available to you — agencies get plans priced for managing many client Business Units.
Within an organization, members hold an organization role:
| Role | Can do |
|---|---|
| **Owner** | Manage members, the subscription, and which Business Units the organization can reach. |
| **Admin** | Same as owner. |
| **Member** | Belong to the organization and inherit the access it grants. |
These are distinct from tenant roles (owner/admin/operator/viewer), which control what a person can do *inside* a Business Unit. See Team & Roles.
From the organization settings, an owner or admin can:
The point of an organization is shared access. An admin or owner of a Business Unit can grant an organization access to it, with a role (operator or admin). From then on, every member of that organization can reach the Business Unit at that role — without an individual invite each.
This is the core agency workflow:
A scope is a per-member, per-tenant restriction. Without a scope, a member sees every Business Unit the organization can reach. With scopes set, they see only the assigned ones. Scopes are managed from the member's entry in organization settings and are enforced everywhere — lists, dashboards, and the API all filter to the member's scope.
A person can belong to more than one organization — for example a contractor working with two agencies. Their access is the union of what each organization grants, always bounded by their role and scopes in each.