Path | Duration | Level | Before you start | ||
🟠 Analysis | 50 min | Intermediate | [[11 · Programaciones - el trabajo planificado | Schedules - planned work]] · Recommended: [[10 · Consultas - reutilizar los datos que ya tienes | Queries - reusing the data you already have]] |
The dashboard is the first thing a user sees when entering Mairu. If it is well designed, each person finds at a glance what they have to do or keep an eye on. If it is a generic screen for everyone, nobody looks at it.
🎯 By the end you'll know how to
Choose the right widget depending on the objective.
Create one dashboard for whoever executes and another for whoever supervises.
Give permissions to a dashboard and turn it into the home screen of a profile.
🧠 The idea: navigate, execute, consult, analyze, report
Before adding a widget, ask yourself what it is on the screen for:
Objective | Widget | What it needs first |
Navigate | Shortcut · Pinned items · Link | — |
Execute | Tasks | Schedules (lesson 11) |
Consult | Response list | List-type query (lesson 10) |
Analyze | Indicator (KPI) · Power BI | Indicator-type query · Power BI report (lesson 14) |
Report | Free text · Message board · Gallery · Greeting | — |
And design by profile:
Profile | Needs | Typical dashboard |
Whoever executes (operator) | To know what's up today and start quickly | Tasks + shortcuts + pinned items |
Whoever supervises (quality, manager) | To know what's going wrong and where to act | Indicators + lists + everyone's tasks + Power BI |
💡 Each profile has an Initial route: the screen it sees when logging in. It is usually one of the published dashboards.
🛠️ Guided practice
Dashboard 1 · Operator home
Create a new dashboard called Operator home and enter edit mode.
Add and configure these widgets (drag them to place them and use the pencil to change their size):
Widget | Configuration |
Greeting | User name, date and time |
Tasks | Cards mode · Active and Overdue statuses · visibility By position |
Shortcut | New packaging control button to the form |
Pinned items | The forms each operator marks with the pin |
Free text | Three lines with the key instructions of the control |
Dashboard 2 · Quality
Prepare the KPI query. Create an Indicator query Pending review that counts (count) the controls whose status (state_id, attribute name) is Pending review. It is the same condition you used in lesson 12.
Create the Quality dashboard with:
Widget | Configuration |
Indicator (KPI) | Query Pending review · subtitle controls · visual condition: if greater than 0, red background |
Response list | Query Controls pending review (lesson 12) |
Tasks | Table mode · all statuses · visibility All departments |
Power BI | You will add it in lesson 14 |
💡 From the Response list widget, Quality can select several controls and use the bulk edit, just like in the history.
Final step · Permissions and home screen
Publish the two dashboards and give view permission to the corresponding profile: Operator home → Operator; Quality → Quality. You can do it from the configuration of the dashboard itself or from the matrix in Settings > Security (they are synced).
In Settings > Security, edit each profile and choose its Initial route: the dashboard you have just created for it.
🔍 Check that it works
When logging in,
operario.pruebagoes straight into Operator home and sees their shift tasks.calidad.pruebagoes into Quality. With a control pending, the KPI comes out red; when they close it as Compliant or Non-compliant, the KPI drops and the control disappears from the list.operario.pruebadoes not see the Quality dashboard.
⚠️ Common mistakes
"I see the dashboard but my user doesn't." Whoever creates a dashboard always has full access, even without permissions. Check the user profile's view permission and that the dashboard is published.
"The user doesn't go into their dashboard when logging in." The Initial route of their profile is not set.
"The KPI doesn't appear when configuring the widget." The Indicator widget only accepts Indicator-type queries.
"The Power BI or Link widget comes out blank." The Link widget only works with pages that allow being embedded.
Filling the dashboard with widgets. If a widget doesn't help that profile navigate, execute, consult, analyze or report, it doesn't belong.
🏋️ Challenge
Design the Production supervisor dashboard (the profile from the challenge in lesson 3). They need to see the NOT OK controls of their lines, the operators' overdue tasks and quick access to the control history. Before creating it, write for each widget what its objective is (navigate, execute, consult, analyze or report).
📚 Learn more
Dashboard permissions - why a user doesn't see a Dashboard · FAQs Dashboards
➡️ Next lesson: Power BI - from form to report