Create Accountor Login
Docs

Public Widgets for a Website

Part of the MountDev Ops Workspace documentation. Updated November 16, 2026

MountDev Ops Workspace documentation | Updated November 16, 2026

An owner or admin can make one widget, or a dashboard of general data, public for a website. Visitors see a snapshot of totals, never your records, and the address serves only that stored snapshot.

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.

What Can Be Public

  • Totals and charts only. A public widget shows as a Number, Trend, Bar, or Line, made from counts, sums, and averages. It is never a List or a Table, and never shows a row, a name, an email, a phone number, or anything about one person or one client.
  • Small groups are merged. A group of fewer than 3 rows is shown together with the others as Other, so a small group cannot single someone out.
  • Grouping is limited. A public widget groups only by a choice field, a yes or no field, or by day, week, or month. Never by a person, a client, or a name.
  • Private never goes public. A Dataset field marked Private, and a field your role rules hide, can never be used. If a field a public widget uses is marked Private later, the widget stops at once.
  • A dashboard can be public only when every widget in it is general data. Client data and embeds never are.

Making One Public

Owners and admins open the widget in the gallery under Custom (or a dashboard in Dashboards) and choose Publish Publicly (actions core.widgets.public.preview and core.widgets.public.publish). The pop up shows the exact numbers that will be public. Choose how often they refresh (every 15 minutes at first, from 5 minutes to 24 hours), check "I understand anyone with this link can see these numbers", and choose Yes, Make It Public. The embed code is shown once, so copy it then. Only a hash of its key is kept.

A Snapshot, Not Live

A background job works the numbers out on the schedule you chose, as the person who confirmed it (their access is read fresh each time), and keeps only the totals. The public address serves that stored snapshot. It reads no data of yours, and it has no way to ask for other data: nothing a visitor sends changes what it shows. It sets no cookie, keeps no count of who views it, and has its own small rate limit. The address answers as a small web page, and with ?format=json as the same totals as data.

Changing and Revoking

  • Revoke (action core.widgets.public.revoke, in Dashboards under Public Widgets) deletes the address's key and the snapshot at once. The address then says "This widget is no longer available."
  • The list of public widgets (action core.widgets.public.list) shows each one with its name, what it shows, how often it refreshes, when it last updated, and whether it is on or stopped, never the key.
  • Changing a public widget or dashboard stops it until you confirm it again, and a new confirmation is a new address and a new embed code.
  • A person who confirmed it and then loses access to your workspace stops it too.

Only owners and admins can do any of this, and no AI agent, API key, or member can. Every publish and revoke is in the Activity Log with who did it. Public widgets are stored in your own workspace and region.

Ask Us Anything

We’d love to hear from you!