Dashboards for Your Clients
Part of the MountDev Ops Workspace documentation. Updated November 16, 2026
MountDev Ops Workspace documentation | Updated November 16, 2026
A dashboard is a named set of widgets you show your clients on their portal: their own numbers, general numbers, or something embedded from another website. Owners and admins make and publish them.
Our Commitment
MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.
Every update passes all 5,581 automated checks before it ships, and every screen change is walked through before release.
Making a Dashboard
On Home, owners and admins choose Arrange Home, then Dashboards (actions core.dashboards.list and core.dashboards.save), then New Dashboard. Give it a name and add up to 12 widgets. Each widget is one of three kinds:
- Client data. One of your own custom widgets whose sources each link their rows to a CRM company, such as Projects or Invoices. Each client sees only their own rows. The client's company is added by the server from the client's own sign-in, never from the page, the address, or anything a client can change, so a changed or forged request still returns only that client's rows. A client with no company link sees no rows, not every row. A source with no link to a company (a Dataset, Time, or a module of your own with no company field) cannot be client data.
- General data. The same for every client, chosen by you. It shows totals and charts only (Number, Trend, Bar, or Line), never a row or a name, and it groups only by a choice or a yes or no field. A field marked Private in a Dataset can never be used. General data is worked out with your permissions, the person who published it, so it stops if you lose access.
- Embed. An address you add, shown in a frame. It must start with
https://, with no name or password in it. The frame is sandboxed (allow-scriptsonly, with no same-origin access, forms, top navigation, or popups) and sends no referrer. Nothing about the signed-in person or client is in the address or the frame. List each website you embed once in Allowed Embed Hosts; the portal page allows frames from those hosts only.
A dashboard stores only its definition, never data. Saving a change to a dashboard takes it off the portal until you publish it again.
Publishing
Publish to Portal (action core.dashboards.publish) chooses All clients or Chosen clients, and asks you to confirm who will see it before anything is published. Take Off Portal (core.dashboards.unpublish) removes it at once. Only owners and admins can do any of this, and no AI agent, API key, or client can. Every make, change, publish, and take off is in the Activity Log with who did it and to whom.
View As
View As (action core.dashboards.view_as) shows a dashboard exactly as a chosen client sees it, read only, before or after publishing. It runs the same code the portal runs, and each use is written to the Activity Log.
On the Client Portal Planned
The Dashboard page on the client portal arrives with the client portal itself. Clients will see only the dashboards published to them, read only, on the one sign-in they already have, and a client will not be able to change a dashboard. A closed account sees its dashboard read only like the rest of its portal.
