What happened
What this says
Current to 10 Oct 26Operations Analyst asking best practice for dashboard architecture (one master or separate per depot) and access control model. Bethan recommended one master dashboard with filters and generous permissions.
Problem: Customer unsure whether to build single dashboard with depot filters or separate dashboards per depot, and how access control works at scale. Handling: Bethan recommended one master dashboard with depot and date range filters for easier maintenance, explained access control is independent of data access, and asked for user count to tailor further guidance. Watch: Strong adoption signal; customer planning team-wide rollout across multiple depots.
Details
Updated 9 Oct 26Trail
- created · Aisha Rahman 23 Sep 2026 13:36Hi, I'm trying to create a dashboard to show our depot teams real-time delivery statuses and customer at-risk indicators. But I'm not sure about the best way to structure it – should I make one large dashboard or separate ones per depot? And how do I control who can see what? I've looked at the guide but I'm a bit confused about the access model. Can you give me a bit of guidance? Thanks, Aisha
- public_reply · Bethan Lister 23 Sep 2026 21:14Hi Aisha, great to hear you're building dashboards – that's a great way to drive adoption. Let me help. A few thoughts: start with one master dashboard and add filters for depot and date range, much easier to manage than separate ones. On access, you can grant dashboard access independent of data access, so you can be generous with permissions. Can you tell me how many people on the depot teams you're planning to give access to? That'll help me give you the right guidance. Thanks, Bethan
- status_change · 6 Oct 2026 23:59