Installing and enabling apps for a property

Who this is for: Owner, and any role with apps.manage — no other default role carries it. Where: Integrations → App Directory

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. Turning one on or off is self-service, from the App Directory — the one screen that can enable any app for a property, including the Integration Hub the Directory itself lives inside.

หมายเหตุ

Why the Directory can always reach itself. apps.manage is a core permission — always available, never gated by any app's own enablement — specifically so this screen can never lock an Owner out. Earlier, it belonged to the Integration Hub app, which meant a brand-new property (Integration off by default) had no way to reach the one screen that turns Integration on; the only route left was Nerve staff, internally. That bootstrapping trap is fixed: the Directory is reachable from the moment a property exists.

Install or remove an app#

1. Open Integrations → App Directory.
2. Find the app under Nerve apps (first-party) or Partner apps (third-party, built outside Nerve).
3. Select Install.

Installing a first-party app flips its enablement immediately — its navigation group appears, and its permissions start resolving, for everyone at that property, with no redeploy. Installing a partner app is a consented grant: you see exactly which permissions it is requesting before you confirm, and it mints a scoped credential the app uses to call Nerve.

Select Uninstall to remove either kind. It revokes symmetrically — the navigation group disappears, the permissions go inert, and a partner app's credential is revoked — but the property's own data is untouched. Re-install and everything is exactly as it was.

When an app is outside your plan#

Some apps are commercial. A card for an app your organisation is not entitled to shows a badge — Requires subscription for a partner app, Not in plan for a first-party one — in place of a working Install button.

สำคัญ

This is a paywall, not a permission problem. You can hold apps.manage and still be unable to install a specific app, because entitlement is a separate, commercial gate on top of the permission one — the same distinction Roles and what each one can do draws between may you and did you pay for it. Contact your account manager to upgrade; there is nothing to configure your way around here.

หมายเหตุ

Every Nerve-built app installs free today — the paywall badge is what you would see on a partner app your plan does not include. The mechanism exists per first-party app too, so do not assume it can never apply to one; check the badge on the card rather than assuming from this note.

Which apps a property starts with#

App	Navigation group it produces	Pre-installed on a new property
Accounting	Accounting	yes
Crs	Reservations	yes
Frontdesk	Front Desk	yes
Headquarter	Headquarter	no
Housekeeping	Housekeeping	yes
Integration	Integrations	no
Inventory	Inventory	yes
Pos	Point of Sale	yes
Rms	Revenue	no

Revenue, the Integration Hub and Headquarter are off on a new property — install them from the Directory when you are ready for them. That is why a fresh organisation has no Revenue menu even for the Owner, and why the answer is installing the app rather than a permission.

หมายเหตุ

Settings itself is never gated this way. It belongs to the core app, which is always enabled — there is no state in which the administration screens disappear.

What actually happens when an app is off#

Three things:

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.

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

สำคัญ

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 Directory before you check the role.

หมายเหตุ

Read a property's installed-app set directly on the Directory — every card carries an Installed badge when it is on. If you cannot reach apps.manage yourself, diagnose by elimination instead: does anyone at that property see the group, Owner included?

The four questions a screen asks#

A screen appears only when all four answer yes:

Question	Where it is answered
May you? — does your role carry the permission	Roles
Is the app on? — is the owning app installed on this property	Integrations → App Directory — this page
Did you pay for it? — is your organisation entitled to the capability	your plan — the badge on the app's own Directory card, and see White-label for the worked example
Is it ready for you? — has the feature been rolled out to your organisation	the Nerve team

The last of the four is not something you configure. It exists so a feature can ship dark, and is why a screen can be missing when everything else — permission, installation, plan — is plainly satisfied.

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

What's next#

• Integrations overview — the rest of what lives beside the Directory
• Hotel: properties, profile and policy — what is still on that screen
• Roles and what each one can do — which permissions belong to which app
• Team: people and what they reach — the other half of who sees what