Documentation
Settings
Organisation, properties, members, roles and audit.
14 pages
- Settings overviewOrganisation, properties, members, roles, terminology, notifications and audit — the section that decides what everyone else in your house can see and do.
- Organisation settingsRename your organisation, find the id an operator needs to link to you, and see which parts of the account the Nerve team owns rather than you.
- Properties and hotel settingsCreate a property, edit its profile, and set the two policies that change how the desk behaves: the readiness gate and the core-night window.
- Members and invitationsInvite a colleague, scope them to one property, assign or remove roles — and why the last Owner cannot be removed from the organisation.
- Roles and custom permission bundlesAuthor a role from the permission catalog, clone one you already have, and learn what the reserved Owner role will not let you do.
- Roles and what each one can doThe default role bundles, what each can and cannot reach, and how role, permission and app enablement combine to decide your sidebar.
- Enabling apps for a propertyOne switch per app, per property. It makes whole navigation groups appear and disappear, and it explains most "the menu is missing" questions.
- House terminologyOverride Nerve's hospitality vocabulary with the words your house actually uses, per language — and what that costs when you read the documentation.
- Importing your dataFill one spreadsheet offline, upload it, read the cell-by-cell validation, and commit — the fastest way to bring a new property to life.
- Operator links and the delegation rosterHow one organisation's staff come to operate another organisation's hotels — invited, accepted, delegated, and revocable in one move.
- The operator portfolioToday's position across every property your organisation manages for somebody else — one read-only screen, composed without crossing a tenant boundary.
- Notifications and documentsPreview what a guest receives, in their language, before they receive it — and check whether the message you thought was sent actually arrived.
- Step-up securityWhich money-impact actions make someone re-prove who they are, above what amount, and where every completed verification is recorded.
- The audit logOne chronological trail of the high-trust actions in your organisation — people, API keys and agents in the same stream, with actor, target and outcome.