Settings
Members and invitations
Invite a colleague, scope them to one property, assign or remove roles — and why the last Owner cannot be removed from the organisation.
Last updated
Who this is for: Owner, Manager — requires
org.members.invite; assigning and removing roles requiresorg.members.manage. Where: Settings → Members
Two lists on one screen. People is everybody who already has access and what each of them holds. Invitations is everybody who has been asked and has not accepted yet.
A person's access is not one role — it is the union of every membership they hold. Somebody can be Front Desk at one property and Read-only across the organisation at the same time, and they get both.
Invite someone#
- Under Invitations, select Invite.
- Enter their Email.
- Choose a Role.
- Choose a Scope — Entire organisation, or one named property.
- Select Send invitation.
Scope is the half people forget. 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.
Important
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. When the invitation is created, the screen shows a Token and an Accept link with copy buttons — copy one of them 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 invite them afresh.
The recipient opens the accept link, signs in or registers, and lands in your organisation with the role and scope you chose.
Revoke an invitation before it is accepted#
- Find the invitation in the list. Pending ones carry a pending badge.
- Select Revoke.
The link stops working immediately and no membership is created. This is the fix for an invitation sent to the wrong address, and for the accept link you lost before copying it.
Assign a role to someone who already has an account#
- Under People, select Assign role.
- Enter their Account email.
- Choose a Role and a Scope.
- Select Assign role.
This path is for people who are already in Nerve — either already in your organisation, or with an account of their own elsewhere. It does not create an account: somebody who has never signed up needs an invitation instead.
Assigning a second role does not replace the first. Both memberships sit on the person's card, and their permissions add up.
Remove a role from someone#
- Find the person under People.
- Select the × on the membership you want to remove.
The membership disappears. If it was their last one in this organisation, the organisation also stops being offered to them in the workspace picker.
The last Owner cannot be removed#
An organisation must always keep at least one Owner. Removing the final Owner membership is refused, and so is removing your own — there is no path that leaves an organisation with nobody who can administer it.
The way to hand the organisation over is therefore in this order:
- Assign Owner to the person taking over.
- Then remove the outgoing Owner's membership.
Once there are two Owners, either one can be removed. The safeguard only ever protects the last one.
Note
There is no "change this person's role" control. A role change is an assign followed by a remove, which is why demoting the only Owner is refused for the same reason removing them is — it is the same action.
Memberships you cannot revoke here#
A membership labelled via ‹operator› link was not granted on this screen. It came from an operator link: a management company's roster was delegated a role in your organisation, and every person on that roster received an ordinary membership as a result.
Remove it by revoking the grant or the whole link on Operator links and the delegation roster — not here. Revoking the link removes every delegated membership at once.
What's next#
- Roles and custom permission bundles — authoring the role before you assign it
- Roles and what each one can do — what each default bundle carries
- Enabling apps for a property — the other reason someone's menu is shorter than you expected