Settings overview

Who this is for: Owner — most of this section requires org.manage. Manager reaches several screens on their own permissions. Where: Settings

Settings is where an organisation is administered rather than operated. Everything a colleague can or cannot do starts here: which properties exist, which apps each one runs, who your members are, what each role carries, what your house calls things, and what everybody did afterwards.

It is the section that answers "why can't my colleague see X".

Who works here#

The Owner owns this section. org.manage is the permission that unlocks the organisation profile, operator links and the delegation roster, and no other default role carries it.

Manager is not locked out, though. The Settings group is core, which is never gated by app enablement, so a Manager sees exactly the screens their own bundle reaches:

A Manager reaches	A Manager does not
Members, Hotel, Terminology, Notifications, Step-Up Security, Audit Log	Organisation, Roles, Operator Links, Delegation Roster, Portfolio, Data Import

Everything else — Front Desk, Accountant, Storekeeper, Read-only — has no Settings menu at all by default.

Ghi chú

This section uses the default terminology. Your house may have renamed these terms under Settings → Terminology.

What's in this section#

The organisation and its properties

• Organisation settings — the org name, its id, and what the Nerve team owns rather than you
• Properties and hotel settings — create a property, edit its profile, and set the two policies that change how the desk behaves
• Enabling apps for a property — the switch that makes whole nav groups appear and disappear

People and what they may do

• Members and invitations — invite someone, scope them to one property, and assign or remove roles
• Roles and custom permission bundles — author a role from the permission catalog
• Roles and what each one can do — the default bundles, as a reference table

The house's own vocabulary and data

• House terminology — rename hospitality vocabulary per language
• Importing your data — the onboarding workbook: download, fill, validate, commit

Multi-property operators

• Operator links and the delegation roster — one organisation operating another's hotels
• The operator portfolio — today's position across every managed property

Oversight

• Notifications and documents — what Nerve sends, in which language, and whether it arrived
• Step-up security — which money-impact actions demand re-verification
• The audit log — one trail for people, API keys and agents

Mẹo

A single-property house can skip Operator links and The operator portfolio entirely. They exist for management companies that run hotels belonging to somebody else's organisation.

How it connects#

• Everything the other sections do is gated from here. A screen appears when your role carries its permission and the app that owns it is enabled on the property. Why two people see different menus walks that diagnosis end to end.
• App enablement is the same idea the Integration Hub states for apps you install — see the Integrations overview.
• Agent and API activity lands in the same audit trail as human activity, which is what makes MCP agents reviewable rather than opaque.
• Crossing into the partner portal is a different kind of re-authentication from step-up on a refund. Realms explains the distinction.