Team roles and access

Decide who on your team sees which parts of Nimbu, and why two colleagues get a different menu.

Two colleagues in the same account can see a different menu. That is not a bug. Access is checked per site, and not everybody needs everything.

This page helps you decide who gets what, and where you arrange it.

Two layers

Account membership decides whether somebody belongs to your organisation at all and which sites appear in their list. You manage that under Account, in Teamleden (team members).

Per-site access decides what that person can open within one site. Somebody can have full access on one site and limited access on another, inside the same account.

See Account overview for where the team member list lives.

Nimbu does not show areas you have no access to. Someone without settings permissions does not see Instellingen greyed out; they simply do not see it.

That makes "it isn't there" an ambiguous complaint. Before you go hunting for a bug, check two things:

Is the right site selected? Permissions apply per site.
Does that person have access to the area?

The order is not arbitrary. Wrong site selected happens more often than a missing permission.

Permissions that stand on their own

A few permissions cause more confusion than the rest:

Access to a site's settings is separate from access to its content. Somebody can edit pages without ever reaching Domeinen.
The Ontwikkelaar (developer) block in Settings, holding Meldingen, Apps, Ontwerp, Push & integraties, and Variabelen, hangs off its own permission.
Reviewing spam on form submissions is separate from viewing those submissions.
Channels with sensitive data, such as a contact form full of names and phone numbers, can carry a separate permission.

Roles on a site: mind the overlap

The word "role" does double duty in Nimbu. There are the people on your team who use the admin, and there are roles for the customers or members who log in on your website. The second is site content, not admin access.

The demo site has no customer roles configured at all. So if you go looking for a colleague's access and end up at an empty list, you are probably on the wrong screen.

Adding somebody

Who belongs to the account is listed under Account, in Teamleden (team members). That is where it starts: somebody joins the account first, then gets access to the sites they need.

Exactly how adding works differs per account and per the access you hold yourself. If Teamleden offers you no way to add somebody, ask the account owner.

Do not hand out everything by default

Full access is the fastest way to get somebody working, and also the fastest way to have a domain accidentally disconnected or a consent configuration rewritten. Start with what the person needs today. Widening it later takes a minute.

Somebody leaving

Have a departing team member removed from the account rather than only stripping their permissions. As long as the membership exists, access to every site in the account is one setting away.

Then check whether anything still carries their name: a notification recipient using their personal email address, for instance. Those mails otherwise land in a closed mailbox.