Skip to content

Dashboards permissions

Access to dashboards comes from the service, not from the dashboard. There are no per-dashboard permissions and no sharing settings on an individual dashboard.

Every dashboard operation needs one of three access levels, and your service role decides which you have.

Level Service roles that have it
Read Any member of the service
Edit Owner, editor, admin
Admin Owner, admin

A viewer on a service has read only. An editor can build and publish but cannot do the admin-level operations. Owner and service admin can do everything.

Someone holding the platform-level system_admin role bypasses all of these checks on every service.

Operation Level
Open a dashboard and read it Read
Open a published dashboard Read
Export data from a published dashboard Read
Create a dashboard Edit
Add, bind, move, and delete widgets Edit
Configure filters Edit
Publish, and publish again Edit
Create and edit delivery schedules Edit
Delete a dashboard Admin

If a service has teams attached to it, the dashboard list applies a second check: you must belong to one of those teams to see any dashboards, whatever your service role says. A service with no teams attached skips this, and every member sees the list.

This is the usual cause of an empty dashboard list for someone who is definitely a member of the service.

Publishing a dashboard internally hosts it inside Lunar Paper and requires the reader to be signed in. It does not by itself give more people access — the internal access rules still decide which signed-in users can open it.

Publishing is therefore not a way to share a dashboard with someone outside the service.

The Schedules tab in the module shows schedules for the current service, and needs the same access level as the schedules themselves.

There is a separate platform-wide schedules administration view that lists every dashboard schedule across all services. That one requires the platform admin role, not a service role.

Publish and version covers what publishing does. Troubleshooting covers what a permission failure looks like from the outside.