With authentication on, each dashboard has its own rights. A new dashboard is open only to the person who created it and to dashboard administrators. They decide who else may view or edit it.

This page describes Community release 2026.11.16.1 and later. Authentication must be on: see Security.

Rights

RightAllows
Can viewOpen the dashboard, see its revisions under History and its call log
Can editView, change the dashboard, restore an earlier revision
WhoOn a dashboard
CreatorCan edit. Shares the dashboard and deletes it
Dashboard administratorsThe same as the creator, on every dashboard. They also hand a dashboard over to another owner
OthersThe rights the creator or an administrator gave them

The rights of the creator and of administrators on a dashboard can’t be taken away. The dashboard header shows the owner: created by <user>.

Every signed-in user may create dashboards. Dashboards are built by an AI agent over MCP, and the user the agent signed in as becomes the creator: see Build a dashboard with an agent.

Dashboard administrators are the groups listed under mondrian.security.dashboard.manage in auth/security/security.properties. Setup gives this right to /emondrian-admins:

mondrian.security.dashboard.manage=/emondrian-admins

A change to the file applies at the next request, with no restart.

Share a dashboard

Open the dashboard menu and choose Share…. In the window Who may use “<name>”:

  1. Under Give to, choose User and enter a user name, Group and enter the group’s full path, such as /Sales/Managers, or Everyone signed in.
  2. Under Right, choose Can view or Can edit.
  3. Click Give.

To take a right away, click the icon next to it. Rights given to a group follow the user’s current groups, checked at every request.

Hand a dashboard over

An administrator sees Hand over to user in the same window. The new owner becomes the creator of the dashboard. The previous owner keeps no rights on it, unless given a right separately or an administrator.

What a user sees

  • The dashboard list shows only the dashboards the user may view.
  • A dashboard the user may not view opens as not found, the same as a dashboard that doesn’t exist.
  • A user who may view a dashboard but not edit it opens it; a save is refused.

Dashboard rights don’t give access to data. Each visual reads its data in the viewer’s browser through the gateway, with the viewer’s schema roles. A user who may open a dashboard but may not see a cube sees no data from that cube.

AI agents

An agent connected over MCP acts as the user who signed in, with that user’s rights on each dashboard:

ToolNeeds
list_dashboardsReturns the dashboards the user may view
get_dashboardCan view
update_dashboardCan edit
delete_dashboardCreator or administrator
create_dashboardSigned in; the user becomes the creator
get_dashboard_accessCan view. Returns the owner and the user’s own right; the creator and administrators also get the list of rights, with who gave each one and when
set_dashboard_accessCreator or administrator

set_dashboard_access takes the dashboard id and up to 100 changes. Each change names kind (user, group or all), principal (a user name, a group path, or *) and level (read, write, or null to take the right away). It returns the new list of rights. Handing a dashboard over is not available through MCP.

Every call of set_dashboard_access is written to logs/mcp-audit.log with the user’s name, whether it was allowed or not.

On a server started read-only, create_dashboard and set_dashboard_access are available only with emondrian.mcp.dashboardWrite=true.

Dashboards created before this release

They have no creator: the dashboard administrators own them, and the header shows owned by the administrators. Every signed-in user may view them. An administrator can hand each one over to its owner and set its rights.

Authentication off

Dashboard rights apply behind the eMondrian login. With authentication off, every dashboard is open to everyone who can reach the server.