deskbird Intelligence: Overview dashboard

The Overview dashboard is the single place for admins to monitor desk mapping and office detection across all offices in the company. Instead of opening each office one by one, admins see at a glance which offices are detecting presence, where network rules conflict, how far desk mapping has progressed, and where action is needed. The Overview is available to companies with deskbird Intelligence, which is included in all Professional and Enterprise plans and is also available as a standalone subscription.

1. Where to find the Overview
2. KPI cards
3. Office table
4. Search, filter and sort offices
5. Fix issues from the Overview
6. FAQs

1. Where to find the Overview

The Overview is part of Intelligence in the main navigation. Where it appears depends on the setup status of the company:

• While setup is in progress: the Setup guide appears first, with the Overview directly below it.
• After all setup steps are completed: the Setup guide is removed from the main navigation and the Overview is shown first. The Setup guide remains available through a link in the page header.
• Companies without the Setup guide: only the Overview is shown.

Two quick links sit in the top-right corner of the page:

• Learn more: opens the deskbird Help Center.
• deskbird Dock app: opens the deskbird Dock download page, to install Dock on macOS or Windows. See Install on macOS and Install on Windows.

2. KPI cards

Four cards at the top of the page summarize the configuration health of the whole company:

• Active offices: the number of offices that are successfully detecting presence, out of all offices (for example, 14/47).
• Conflicted offices: the number of offices whose network rules overlap with the rules of another office, so Dock cannot tell which office a device is in. When this number is above zero, review the network rules of the affected offices.
• Mapped desks: the average share of desks mapped to a monitor, across all active offices.
• Conflicted monitors: the number of monitors with a mapping conflict, and the number of active offices they are spread across.

💡 Note: Mapped desks only counts active offices. Offices that are not yet detecting presence do not lower the percentage.

3. Office table

Below the KPI cards, a table lists every office with the following columns:

• Office: the office name, with its country code and city.
• Floors: the number of floors in the office.
• Desks: the total number of desks in the office.
• Office detection status: the current state of office detection for that office (see below).
• Desk mapping progress: a progress bar showing how many of the office's desks are mapped to a monitor.

The Office detection status column shows one of these values:

• Active: office detection is configured and working.
• Conflict: the office's network rules duplicate the rules of another office and need to be fixed.
• Pending: office detection has not been set up for this office yet.
• Partial: office detection is only partly configured for this office.

4. Search, filter and sort offices

Use the controls above the table to find offices quickly:

• Search: type an office name to narrow down the list.
• Filter: show only offices with a specific office detection status, for example all offices in Conflict or Pending.
• Sort: order the table by office name, number of floors, number of desks, or office detection status.

💡 Tip: to plan the next rollout steps, filter by Pending and sort by desks to start with the largest offices.

5. Fix issues from the Overview

Each row links directly to the page where the office is configured, so issues can be fixed without searching through the admin settings:

1. In the office table, hover over the row of the office.
2. To fix office detection, click the settings icon next to the Office detection status (tooltip: Open office detection for [office name]). This opens the office detection settings for that office. See Setting up office detection and network configuration.
3. To continue desk mapping, open resource detection for that office from the Desk mapping progress column. See Resource detection.

⚠️ Important: offices with the status Conflict cannot reliably detect presence. Fix conflicting network rules first, because desk mapping and booking automations depend on working office detection.

6. FAQs