Navigating the Console

The Console has a consistent layout across every page. Learning where the fixed elements live — the navigation menu, the tenant selector, the theme toggle, the help dialog — means you can find any feature in a few clicks. This chapter is the short tour.

The overall layout

Every page shares the same shell:

• A header along the top with the product logo, the tenant / location / group selector, the theme toggle, and access to your profile and help.
• A left-hand navigation menu grouping every feature area the product exposes.
• A main content area to the right, where the currently opened page renders.
• A footer with product and build information.

You can resize the navigation, and the Console remembers your preference. The header remains visible on every page.

The navigation menu

The navigation menu on the left is built dynamically: the items you see depend on your permissions, the modules enabled on the deployment, and the order you chose to display them in. Two users with different permission sets on the same deployment will see different menus.

The default top-level groups, in their default order, are:

1. Dashboard
2. Devices Quick Access — with All Devices, Unauthorized Devices, and Device World Map sub-items.
3. Tenants
4. Automations
5. Policies
6. Patch Management
7. Collections — Scripts, Jobs, Sensors, Custom Fields, App Hub, Application Control, Device Control, Software Deployment.
8. File Server & Monitoring — File Server, Relay Server, Website Uptime, Port Scanner.
9. Tickets (only if the Ticket System is enabled)
10. Reports
11. Management — Events, Audit, Users.
12. Settings — 16 sub-pages covering administration.

Each group expands to reveal its sub-pages. Selecting a sub-page loads it into the main content area.

Note: Menu visibility is gated by roughly twenty permission flags at the top level, plus additional flags per sub-page. See the Permission reference appendix.

Customising menu order

The Console stores a per-user menu order in your account — the default order is the one listed above, and the server loads your personal order on every login. You can edit the order under /home.

The "Go Pro" upgrade button

If the deployment is unlicensed, a gold Go Pro button appears prominently in the navigation. Clicking it opens the upgrade / licensing flow. Once the deployment is licensed, the button disappears.

The tenant selector

Many pages — Tenant Settings, Location Settings, the Devices page, most Collections pages — act on a currently selected tenant, location, and group. The selector in the header is how you pick them.

1. Click the selector in the header to open a tenant / location / group picker.
2. Choose the tenant, then narrow to a specific location or group if desired.
3. The selection persists across the session and is used by every context-sensitive page you open afterwards.

A few pages also show the selected context inline near the top of the content area, so you always know what you are acting on.

Tip: If a page says "no tenant selected" or shows an empty state unexpectedly, open the header selector first and pick a tenant.

Dark mode

A theme toggle in the header switches between light and dark mode. Your preference is stored in your user account, so the theme is consistent across devices and sessions.

If the deployment has been whitelabeled (see A.6 Whitelabeling & themes), the brand colours apply in both modes. Custom community themes imported via the whitelabeling settings also respect the light/dark split.

Help and support

Help is available from the header via the in-app support dialog.

• Contact support — an in-app form for contacting our support team.
• Update available — appears when a new Console or server version is available, with a short summary and a link to the update flow.
• Subscription reminder — surfaces subscription renewal information on deployments that require it.

For deeper issues, the Troubleshooting appendix enumerates the common failure modes with diagnostics.

Notifications and toasts

Short-lived status messages appear as toast notifications in a corner of the screen — for example "Policy saved" after saving a policy, or an error after a failed bulk action. Toasts disappear after a few seconds; for historical records, check Events or Audit.

Real-time Console features (device status, script execution results, policy deployment feedback) use a persistent connection to the server. If toasts or status indicators stop updating, refresh the page to re-establish the connection.

Keyboard shortcuts

The Console does not define global keyboard shortcuts. There is no product-wide dark-mode toggle, command palette, or save/close binding. Keyboard handling is limited to page-local conveniences — for example, pressing Enter submits the login form, and the remote control window binds function keys relevant to that session. Each per-page shortcut is noted in the chapter that documents that page.

Where to go next

You now know the shell of the Console. From here, jump to whichever feature area matters most:

• Chapter 2 — Dashboard — the default landing page for most users.
• Chapter 3 — Devices — inventory, approvals, remote access.
• Chapter 4 — Tenants, Locations & Groups — managing the hierarchy.
• Part III — How-To Guides — task-oriented walkthroughs.