Settings

Team: people and what they reach

One list of everybody who has access, one way to add somebody, a profile per person showing which properties their roles actually reach, and the departments they belong to.

Last updated

Who this is for: Owner, Manager — requires org.members.invite; changing role assignments or departments 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, on the People tab. A second tab, Departments, holds the org dimension covered further down this page.

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.

Important

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.

Department sits below that, one value for the whole person rather than per role — see the next section for what it is and who can set it.

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.

Note

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.

Departments#

A department is the org dimension approvals, expense allocation and productivity reporting group by — Front Office, Housekeeping, F&B, whatever divisions your property actually reports on. It lives alongside Team rather than as its own Settings entry, because a department only ever means something in relation to who is on it.

Manage the list#

Switch to the Departments tab.

  1. Select Add department and give it a Name.
  2. Select a department's name to rename it.
  3. Use the switch in the Active column to deactivate one you no longer use.

A department is never deleted, only deactivated — the same convention as a charge code or an article group: a deactivated department stops being offered when assigning somebody, and everybody already on it keeps their assignment exactly as it was.

Assign somebody to a department#

Department is one value per person, not per role. Open their profile, find Department, and choose from the list — setting it writes the same value onto every membership row they hold, so it never disagrees with itself across roles.

Back on the People tab, a department filter appears beside the role filter once at least one department exists, so you can narrow the list to one division at a time.

How it connects#