Enabling apps for a property

Who this is for: Owner — the screen requires hotel.settings.manage, and the switches require app.enable, which only Owner holds by default. Where: Settings → Hotel → App enablement

Nerve is a set of apps sharing one hotel. Each property decides which of them it runs, and that decision is a feature gate: an app that is off contributes nothing to anybody's navigation, whatever their role says.

Every property card on Settings → Hotel carries its own App enablement block, so two properties in the same organisation can run different sets.

Turn an app on or off#

1. Open Settings → Hotel.
2. Find the property's card.
3. Under App enablement, flip the switch beside the app.

Eight switches, labelled with the app key rather than the menu heading. Integration is off, which is the default.

The change saves immediately, and the navigation re-resolves in place — the group appears or disappears without a reload.

Which apps a property starts with#

The switches are labelled with the app's internal key rather than the menu heading it produces, and they are listed alphabetically. The middle column is the translation:

Switch	Navigation group it produces	On by default
Accounting	Accounting	yes
Crs	Reservations	yes
Frontdesk	Front Desk	yes
Housekeeping	Housekeeping	yes
Integration	Integrations	no
Inventory	Inventory	yes
Pos	pos — the Point of Sale screens	yes
Rms	Revenue	no

Revenue and the Integration Hub are off on a new property. That is why a fresh organisation has no Revenue menu even for the Owner, and why the answer is a switch rather than a permission.

Catatan

Settings itself is never gated this way. It belongs to the core app, which is always enabled — there is no switch that can lock you out of the screen that has the switches.

What actually happens when you turn one off#

Three things, in this order:

1. The whole navigation group disappears for everyone at that property — all of Front Desk's items, not just some.
2. A direct URL into one of its screens returns an unauthorized state. It does not say whether any data exists behind it; a refusal never reveals the shape of what it is refusing.
3. Every permission that app owns goes inert. It stays in the role and stops counting for anything.

Revenue switched on: the group is in the menu and Rms is in the enabled set.

One switch later. No Revenue group, no error anywhere — a disabled app is invisible, not refused.

A direct URL into a disabled app. The refusal says nothing about whether data exists behind it.

The data is untouched. Re-enable the app and the group comes back with everything still in it.

Penting

Point 3 is the confusing one. A role can hold a permission and still be refused, and the refusal is indistinguishable from not holding it. If a colleague swears they have the right role and the screen is still missing, check the app switch before you check the role.

Tips

The dashboard is the fastest way to check. Its Enabled apps card lists the property's live set, and the Permissions count beside it moves when you flip a switch — which is the clearest demonstration that enablement decides what a permission is worth.

The three questions a screen asks#

A screen appears only when all three answer yes:

Question	Where it is answered
May you? — does your role carry the permission	Roles
Did you turn it on? — is the owning app enabled on this property	this page
Is it ready for you? — has the feature been rolled out to your organisation	the Nerve team

The third is rare and not something you configure; it exists so a feature can ship dark. But it is the reason a screen can be missing when the first two are plainly satisfied.

Why two people see different menus walks the diagnosis in order.

The Integration Hub says the same thing about installed apps#

Enabling a third-party app from the App Directory works the same way and for the same reason — the Integrations overview states it from that side. One idea, two doors into it.

What's next#

• Properties and hotel settings — the rest of this screen
• Roles and what each one can do — which permissions belong to which app
• Members and invitations — the other half of who sees what