Nimbus is built for teams. Access is controlled at two levels — the Business Unit (tenant) and the organization — and every member holds a role that decides what they can do.
Within a single Business Unit, a member has one of four roles:
| Role | Can do |
|---|---|
| **Owner** | Everything, including managing the team and removing themselves. |
| **Admin** | Everything operational — connection settings, rules, integrations, team management. |
| **Operator** | Run reruns and manage day-to-day monitoring; cannot change connection or team settings. |
| **Viewer** | Read-only access to events, monitoring, and data. |
Pick the least-privileged role that lets someone do their job. Most people running campaigns are operators; stakeholders who only need visibility are viewers.
From Settings → Team & roles, an admin or owner can:
Pending invites are listed until they are accepted or cancelled.
The invite email links to an acceptance page. If the recipient does not yet have a Nimbus login, they are taken to sign up with their email pre-filled; once signed in, accepting the invite grants the role from the invite.
Instead of inviting people to each Business Unit one at a time, you can grant an entire organization access to a Business Unit. Every member of that organization then reaches the Business Unit with a role you choose. This is how agencies operate — see Organizations.
Within an organization, a member can be scoped to specific Business Units. A scoped member only sees the tenants they are assigned, even though the organization as a whole has access to more. Use scoping to keep a contractor or a junior operator focused on the accounts they own.
A person can reach a Business Unit two ways:
The Team & roles screen shows both, so it is always clear *why* someone can see a Business Unit.