Team: people and what they reach

Who this is for: Owner, Manager — requires org.members.invite; changing role assignments requires org.members.manage. Where: Settings → Team

This screen used to be called Members and showed two lists side by side — People who had access, and Invitations that had been sent — above two separate buttons, Invite and Assign role. Choosing between those two buttons required you to already know whether your colleague had a Nerve account, which is not something you can be expected to know.

It is one list and one button now.

Everybody with access, the roles each of them holds, and the scope of each role.

Access is the union of somebody's roles#

A person's access is not one role — it is every membership they hold, added together. Somebody can be Front Desk at one property and Read-only across the organisation at the same time, and they get both.

Scope is the half people forget. A role is always held somewhere: either across the entire organisation, or at exactly one named property. A Front Desk agent hired for one hotel should be scoped to that hotel — they will then see only that property in the switcher, and the other one does not exist as far as they are concerned.

Add somebody#

1. Select Add person.
2. Enter their email.
3. Choose a role.
4. Choose a scope — the entire organisation, or one named property.
5. Select Add person.

You are not asked whether they already have an account, because Nerve can tell. If the email already belongs to a Nerve account, the role is assigned outright and they have access immediately. If it does not, an invitation is issued instead. The panel that appears afterwards says which of the two happened.

Quan trọng

When it is an invitation, the accept link is shown once, on this screen, and is not e-mailed. Invitation e-mail is not wired up in any environment yet. The result panel shows a token and an accept link with copy buttons — copy one now and send it to the person yourself. Navigate away and it is gone: the invitation is still valid and still listed, but the link cannot be shown again, and you will have to revoke it and add them afresh.

The recipient opens the accept link, signs in or registers, and lands in your organisation with the role and scope you chose.

Open somebody's profile#

Select a person's row.

Every role the person holds, and — the question the old list could not answer — which properties those roles actually reach.

Role assignments is every membership they hold, each with the scope it was granted at.

Properties reached is the part worth reading. A scope is abstract; this section resolves it into the actual list of properties the person can open today. An org-wide role says so explicitly — every property in this organisation, including any added later — which is the sentence that makes the difference between org scope and property scope concrete before you grant it rather than after.

Remove a role#

Open the person's profile and select the × on the membership you want gone.

The membership disappears. If it was their last one in this organisation, the organisation also stops being offered to them in the workspace picker.

Ghi chú

An organisation must always keep at least one Owner. Removing the final Owner membership is refused, and so is removing your own last one — there is no path that leaves an organisation with nobody who can administer it.

How it connects#

• A role is a bundle of permissions, and you can author your own — see Roles and custom permission bundles and the reference table in Roles and what each one can do.
• Adding somebody here does not decide which apps they see. That is app enablement on the property — see Enabling apps for a property.
• When a colleague cannot see a screen you can, Why two people see different menus walks the diagnosis end to end.
• The people and roles listed here are what you assign as requesters and approvers on Escalation.