Skip to main content
Version: Next

The console at a glance

This chapter is a short tour of the parts of the console you see on every page: the home page, the sidebar, the page header with its tenant chip, and the message you get when part of the console is not available on your installation.

It is for anyone new to the console. Read it once, and the later chapters will make more sense.

The home page​

After you sign in, you land on the home page. It welcomes you by name and shows two counts: how many Devices and how many Device Types your tenant has. Select either count to open that list.

The Home entry at the top of the sidebar always brings you back here. It is not the same as Dashboards, which holds the dashboards your team builds.

The sidebar​

The sidebar on the left is how you move around the console. It lists the areas of your tenant in a fixed order.

Home is a single page. Every other entry is a collapsible section that groups related pages. Select a section's heading to open or close it, and select a page inside it to go there.

EntryWhat it holds
HomeThe home page.
MonitorDashboards built by your team, Alarms raised by your rules, and Notification Policies: who is told about alarms, and the quiet hours that hold their pages.
DevicesDevices, Device Types, Device Profiles (which hold the profile's rules, metrics and commands), Device Groups, Command Batches, Maintenance Windows and Updates (Artifacts, Rollouts and Signers for over-the-air updates).
ConnectHow devices and other systems reach the tenant: Provisioning Profiles, Trust Anchors, Integrations and Connectors (outbound connections to other systems).
OrganizationAssets, Customers and Areas (including Geofences); Facets, the keys you use to describe and filter entities; and Browse, a query builder for finding entities by their facets.
AccessMembers, Service Accounts, Roles, Sign-in Security and Audit, the tenant's record of who changed what.
SettingsBranding, Map and Language.

You see only the entries your role allows. If your role cannot read alarms, for example, Alarms is not in your sidebar. Updates appears only when your installation runs the update service. The Access and Settings sections are for tenant administrators.

If your access is limited to some of the tenant's customers, the sidebar holds only Home, Dashboards, Alarms and Devices. See What a customer user sees.

Your name and email address sit at the bottom of the sidebar. They open the user menu, which is described in Signing in.

To make more room for the page, use the button at the left of the page header to collapse the sidebar to a narrow strip of icons. Use it again to expand it.

The page header and the tenant chip​

Every page has a header bar. On the left is the name of the section you are in. On a detail page, such as one device, a link on the right takes you back to the list.

At the far right is the tenant chip. It shows which tenant you are working in: the tenant's name, with its token underneath.

If your tenant has uploaded a logo, the chip shows the logo in place of the building icon. If your access is limited to some of the tenant's customers, the second line names those customers and your role in place of the token: for example Acme · viewer, the customer's name and then the token of your role. Everything you see and change in the console belongs to this tenant. To work in a different tenant, sign out and choose it when you sign in again.

When an area is unavailable​

DeviceChain is made of several services, and whoever installs it decides which ones to run. Some are optional, such as the AI service or the outbound connectors service. If a page needs a service your installation does not run, the page shows Not deployed instead of its usual content.

The message names the missing service. Nothing is wrong with your session or your account. If you need the feature, ask your administrator, using the service name from the message.

The screenshot shows an instance-administration page, but tenant pages behave the same way. For example, Connectors shows this message when the outbound connectors service is not running.