Dashboard link fails across organizations
A platform team runs Grafana 10.4 with two organizations, Platform and Web. Priya is a Viewer in both. Her default organization is Web, where she can browse several dashboards. A teammate in Platform sends her a link to a dashboard: https://grafana.internal/d/api-lat01/api-latency. Priya opens it and sees "Dashboard not found". Her teammate, an Editor in Platform, opens the same link successfully. The dashboard sits in the Platform organization under the folder Observability, which grants the SRE team Viewer access. Priya is a member of SRE in Platform. She checks a folder URL and can open a folder also named Observability in Web, but that is a different folder with the same name. She has not used the organization switcher since joining. The team has a policy that links must work for on-call staff without extra instructions.
1. What is the most likely explanation for the failure, and what would you check first before changing any permissions?
Read the worked answer
The most likely cause is organization context, not folder permission. Grafana resolves dashboard UIDs inside the organization the user currently has active. Priya's default organization is Web, while the dashboard lives in Platform. The matching folder name in Web is a red herring, because folders and dashboards are scoped to an organization. The link also lacks an orgId parameter, so Priya stays in Web when she clicks it.
Check first by opening the organization switcher in the bottom-left navigation and switching to Platform, then reloading the link. Alternatively, append the Platform org ID to the URL, for example ?orgId=1, or ask the teammate to use Grafana's built-in Share link while Platform is active. Only if the link still fails in Platform should you inspect the Observability folder ACL and the SRE team membership. Changing folder permissions before confirming the active organization would waste time and could widen access unnecessarily.
2. How should the team make dashboard links reliable for on-call staff?
Read the worked answer
Standardize links so they carry organization context. Grafana share links can include orgId, and the team should generate links from the dashboard's Share dialog rather than copying the browser address bar. If most on-call staff work in Platform, set Platform as their default organization during onboarding, but do not rely on that alone because users with multiple organizations can switch.
Also document the organization name on the dashboard and in runbooks. A short link or a link with an explicit orgId removes the ambiguity. Avoid copying a dashboard between organizations and assuming the same URL will work, because the dashboard UID is resolved per organization. Folder permissions still matter after the organization is correct, but they cannot fix a link that points into another tenant.
3. Explain the difference between organization membership and folder permission in this case.
Read the worked answer
An organization is a tenant boundary. Being a member of Platform is required before any dashboard inside Platform is visible, regardless of folder ACLs. Folder permissions then decide what a member can view or edit inside that organization. Priya had the correct SRE team and folder grant in Platform, but she was browsing Web, so the Platform folder ACL was never evaluated.
The dashboard was not found because the object does not exist in Web's namespace, not because Priya lacked Viewer rights. This distinction matters for troubleshooting: a permission denial usually appears as access denied or an empty folder, while a wrong organization can look like a missing dashboard. Check the tenant first, then the folder grant.