Sign in and find your way around

Who this is for: everyone with an account — no permission is required to sign in or read your own dashboard. Where: the sign-in page, then Dashboard

Before anything else, one idea that explains most of what follows:

Your navigation is built on the server from your own permissions. It is not a fixed menu with some items greyed out. Two people at the same hotel, signed in at the same time, legitimately see different sidebars — and neither of them is broken.

Sign in#

1. Open the property's Nerve address. You are sent to the sign-in page.
2. Enter your e-mail and password.

A wrong password produces an inline error and creates no session. From there:

• If your account reaches exactly one organisation with exactly one property, you go straight to the Dashboard — there is nothing to choose.
• If it reaches more than one, you land on the picker first. See workspaces, organisations and properties.

Your session survives a page reload. A hard refresh shows a brief Restoring your session… state and then re-renders the page you were on — it does not bounce you back to sign-in.

Sign out#

Use the account menu at the foot of the sidebar. You are returned to the sign-in page, and pressing Back does not reveal application content behind you.

Read the sidebar#

The sidebar has three parts, top to bottom:

• The property switcher, in the header. It names the property you are working in and the organisation above it.
• The navigation, in the middle.
• Your account, in the footer.

The navigation is two levels, as a drill-down rather than an expanding tree.

Level one lists Dashboard, then your Apps — Front Desk, Reservations, Housekeeping, Accounting, Revenue, Inventory, Integrations — each with a count of the screens inside it, and then Workspace, which holds Settings.

1. Select an app to drill into it.
2. Level two lists that app's screens.
3. Select the app's name at the top to come back out.

The open group follows the page you are on, so a bookmark or a pasted deep link opens inside the right app rather than at the top level. Peeking into another group is temporary — navigate, and the menu snaps back to where you actually are.

Understand why your menu differs#

Three things must all be true for a screen to appear:

1. Your role carries the permission that screen requires.
2. The app that owns the screen is enabled on this property.
3. You are in a context — an organisation and a property — where that role applies.

So a colleague's missing menu item can mean a different role, an app switched off for their property, or that they are looking at a different property from you. Why your menu differs from a colleague's works through it.

Penting

A screen you cannot reach is not hidden-but-present. Typing its URL directly returns an unauthorized state that does not reveal whether any data exists behind it. Nav filtering is a convenience on top of real enforcement, not the enforcement itself.

Read your dashboard#

The Dashboard states where you are and what you hold:

Card	What it tells you
Active scope	The property — or the organisation, when you are working at org level
Realm	Which tenancy realm you are in. See realms
Permissions	How many permissions you hold in this context
Enabled apps	How many apps are switched on for this property

Below those, two lists: the apps enabled on the property, and your permissions — the literal, server-resolved set, named exactly as the documentation names them.

Tips

That permissions list is the fastest answer to "why can't I do X". Every page in these docs names the permission its screen requires on its first line; check it against your dashboard before raising a ticket.

What's next#

• Workspaces, organisations and properties — switching between them
• Why your menu differs from a colleague's — the three-way gate in practice
• Your first week on Nerve — if you are the one setting the property up