Summary
Dashboard 3.0 turns MKController into an operational “mission control”: flexible views (Card/List/Map), smart filters, clickable indicators, shared views, and automated email reports. This guide walks you through every piece and shows how to revert to the previous dashboard if you prefer.

MKController Dashboard 3.0: Full Guide

Dashboard 3.0 (called Panel in the UI) is an operational intelligence layer. In practice, it helps you see, segment, and act on your fleet faster—without needing five spreadsheets and a sixth sense.

Image 1

Quick summary: Think of Dashboard 3.0 as your network’s “group chat.” Instead of asking everyone “are you online?”, it shows who’s online, who’s quiet, and who’s definitely ghosting you—instantly.

What Dashboard 3.0 enables

Dashboard 3.0 is designed to support real operations, not just “pretty monitoring.” It helps you:

• Build custom views aligned with your business rules (projects, customers, sites, device types).
• Monitor not only routers, but the whole connected ecosystem around them.
• Spot issues earlier and reduce “time-to-uh-oh.”
• Improve response time and create consistent routines for teams.
• Use visual, analytical, and geographical perspectives from the same data.

How to think about it

Dashboard 3.0 is built around a simple loop:

1. Choose a view (Card, List, or Map).
2. Segment with filters (standard fields + custom attributes).
3. Measure with indicators (Big Numbers).
4. Act (click-to-filter, open devices, dispatch tasks, report results).
5. Package it as a View (shared dashboards) and automate delivery via Reports.

If you keep that loop in mind, every feature makes sense.

1) Card Mode (fast, visual, operational)

Quick summary: Card Mode is your “Netflix browse screen” for devices—except you’re not binge-watching shows, you’re binge-finding problems.

Card Mode is ideal when you want a quick operational scan:

• “What’s down?”
• “Which sites look suspicious?”
• “Are the core routers stable?”
• “Is anything screaming CPU 100%?”

Use Card Mode for triage, daily checks, and “first look” analysis.

How each card is structured

Each device appears as a card. The point is speed:

Best practices for Card Mode

• Use Card Mode as a “traffic-light screen” for operations.
• Keep card lines focused on actionable info (avoid vanity fields).
• Use filters + indicators together so the cards show only what matters right now.

Card Mode customization: device data + connected peripherals

Quick summary: This is where a router stops being “just a router” and becomes the “parent” of a whole family of devices. Yes, it’s a lot of responsibility.

A big idea in Dashboard 3.0 is that a “main” device (like a MikroTik) often supports other critical assets:

• Turnstiles
• Cameras
• Access control gear
• Any connected device you can monitor

Instead of checking each one in separate places, you can surface the essentials inside the same card.

Configure what appears on the card

In Device Configuration (sometimes labeled as default attributes), you can choose what the card highlights. Common examples:

• Firmware version
• Active alerts
• CPU usage
• Memory usage
• Connected devices count

How to choose the right fields

• If your team is technical, show performance and versions (CPU, memory, firmware).
• If your team is operational, show availability and alerts (status, active alerts).
• If you manage customer environments, show identifiers (site, project, asset ID).

Tip: If a field does not help someone decide what to do next, it probably doesn’t deserve card-space.

Tip 2:

Add peripheral monitoring to the same card

The goal is “one-glance availability” of everything that depends on the main router.

Example scenario In a condo, one router may be the hub for:

• Router status
• Turnstile status
• Camera system status

When a resident complains “the turnstile isn’t working,” you can:

1. Open the dashboard.
2. Check the device card.
3. Immediately see which component is down.

That’s fewer phone calls. Less guesswork. And less “it works on my laptop.”

2) List Mode (deep analysis, reporting, exports)

Quick summary: List Mode is the spreadsheet you actually like. It’s still a table, but it doesn’t judge you for filtering 27 times.

List Mode is made for detailed operational analysis:

• Large fleets
• Cross-checking fields
• Exporting data for reporting
• Building role-specific “views” for different teams

What you can do in List Mode

• Display devices as a table (columns you choose).
• Reorder and prioritize data the way your operation works.
• Export the table (useful for audits, SLA evidence, and cross-team sharing).

Practical column sets (copy-paste ideas)

Technical team (diagnostics)

• Status
• CPU
• Memory
• Firmware
• Connected clients/sessions
• Last seen

Operational team (availability)

• Status
• Availability
• Active alerts
• Site / region / project
• “Disconnected by” (when applicable)

Executive view (big picture)

• Status
• Availability (last 7 days)
• Number of sites affected
• Devices offline

Note: List Mode is usually where you validate “Is this really a trend?” after Card Mode flags a problem.

3) Map Mode (geographic operations and pattern spotting)

Quick summary: Map Mode is where you discover that “everything is fine” actually means “everything is on fire… but only in that one neighborhood.”

Map Mode gives a geographic view of your operation:

• Where devices are distributed
• Which regions are unstable
• Clusters of offline devices that suggest upstream issues

How status is represented

Dashboard 3.0 uses intuitive colors:

• Green: online
• Yellow: alert
• Red: offline

When Map Mode is most useful

• Multi-site operations (construction, franchises, branches).
• Residential/condo deployments with dispersed units.
• Project-based rollouts where location matters.

A practical “map troubleshooting” workflow

1. Switch to Map Mode.
2. Apply a filter (example: “Project = X” or “Environment type = Construction”).
3. Look for clusters of yellow/red markers.
4. If you see a cluster, suspect shared dependencies (ISP segment, power, upstream router).
5. Click devices in the affected region and confirm what changed.

4) Filters (turn a list of devices into an operational tool)

Quick summary: Filters are how you go from “I have 2,000 devices” to “I have exactly the 17 devices I care about right now.” It’s like wizardry, but less sparkly.

Filters are the backbone of Dashboard 3.0. They let you segment devices using:

• Standard MKController attributes (vendor, site, name, status, availability)
• Your own custom attributes (asset ID, region, environment type, etc.)

Why filters matter

With filters you can:

• Build dashboards per customer, project, or region
• Monitor only critical devices
• Measure SLA by group
• Reduce time to diagnose incidents
• Create role-specific screens

A simple filtering recipe

1. Start with a broad segment (example: Site, Vendor, Device type).
2. Add an operational condition (example: Status = Offline, Availability < 95%).
3. Save it as a View if it’s something you will use again.

Tip: If your filter is too broad, you’ll feel overwhelmed. If it’s too narrow, you’ll miss patterns. Aim for “actionable scope.”

5) Custom Attributes (your operational DNA)

Quick summary: Custom Attributes are where you teach MKController the “weird names your company uses.” Because every company has them. Yes, even yours.

Custom Attributes let you model your organization’s reality:

• Projects
• Asset tags
• Regions
• Device roles
• Environment types (construction, condo, residence, event)

They are created here: Settings → Panel → Attributes

Attribute types

1) Free text Use for unique, non-standard data:

• Asset ID / inventory code
• Internal ticket references
• Custom identifiers

2) Dropdown list (pre-defined values) Use for standardization:

• Device type (camera, turnstile, printer, router)
• Group
• Affiliation
• Availability category
• Environment type (construction, condo, residence)

Required vs optional attributes

You can mark an attribute as:

• Required: must be filled when adopting/adding a device.
• Optional: can be filled later.

This is governance. In plain English: you choose how strict you want your data to be.

Tip: Make only the “must-have for operations” attributes required. Too many required fields slows adoption.

6) Indicators (Big Numbers) + click-to-filter actions

Quick summary: Indicators are those big numbers that make managers happy. The twist: in Dashboard 3.0 they also make technicians happy, because you can click them and actually do something.

Indicators turn filtered data into KPIs you can act on. There are four main types:

A - Status indicators

Shows how many devices are online vs offline within a filter.

Use it for

• “How many are down in this region?”
• “Did the incident impact many devices or just one?”

B - Availability indicators

Shows average availability for a group over a period (example: last 7 days).

Use it for

• SLA measurement by customer
• Quality trends per region or project
• Evidence for incident reviews

C - Alerts indicators

Shows how many alerts are active and how many devices need attention.

Use it for

• Performance hotspots (CPU high, memory high)
• Communication loss
• Recurring instability

D - Connections indicators

Shows connection-related KPIs (examples: ARP connections, PPPoE sessions).

Use it for

• “Is this site alive but empty?”
• “Are sessions dropping?”
• “Is user volume normal?”

Click-to-filter (the “action layer”)

This is the big difference: indicators are interactive.

When you click a Big Number:

1. MKController applies the corresponding filter automatically.
2. You’re redirected to a filtered list of devices.
3. The system keeps your selected view (Card/List/Map).

Example You click “4 Offline” → you immediately see only those 4 devices.

That’s the dashboard acting like a control panel, not a poster.

7) Views (saved dashboards for teams)

Quick summary: Views are your “saved game.” You don’t have to rebuild the dashboard every time—unless you enjoy suffering. Some people do. We don’t judge (much).

Views let you bundle:

• Filters
• Indicators
• Rules and selections into a reusable dashboard “package.”

How to create a View

1. Create indicators you need.
2. Set your filters.
3. Click Create View.
4. Give it a name.
5. Choose visibility.

Public vs private views

• Visible to all users: great for operational and executive dashboards.
• Private: great for personal investigations or temporary analysis.

Editing rules (important for team sanity)

• Only the view owner can edit it.
• Updates apply to everyone who has access.

Tip: Name views like you name folders: specific, boring, and predictable. “Cameras — South Region” beats “My Cool Dashboard.”

8) Routines (Automated Reports by email)

Quick summary: Routines are the dashboard’s way of saying: “Relax. I’ll send the update email. You go drink water.”

Routines convert a View into a recurring email report. You can schedule daily/weekly/monthly updates for your team.

They live here: Settings → Panel → Reports

How to create a routine/report

1. Go to Settings → Panel → Reports.
2. Click Panel.
3. Click Create Report.
4. Select Report tab.
5. Define:
   • Report name
   • Linked View
   • Frequency (daily/weekly/monthly)
   • Processing time (respects the timezone set in Settings → Company)
   • Choose recipients: All users, or Specific users.

After saving, the report appears in a management table.

Use the test button before going live

Send a test email to:

• Validate layout and content
• Confirm recipients
• Adjust the view if needed

What the email contains (and why it’s useful)

A routine email includes:

• A summary of all indicators in the chosen view
• Automatic comparison with the previous equivalent period
  (today vs yesterday, this week vs last week, etc.)
• A direct button that opens the view quickly for the recipient

That comparison is gold for:

• Trend visibility
• SLA proof
• “Are we improving or just busy?”

Switching back to the previous dashboard (and getting help)

If you don’t like something in Dashboard 3.0, you have two safe options:

Option A: Toggle back to the previous version

Option B: Talk to support (recommended)

Sometimes a “problem” is just a missing view, filter, or attribute design. We can help you model it properly.

👉 Talk to our team on WhatsApp.