The Access Report
Part of the MountDev Ops Workspace documentation. Updated November 17, 2026
MountDev Ops Workspace documentation | Updated November 17, 2026
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.
The Access Report tells owners and admins, before permissions move to the new model, which people would lose which levels of access, so nobody gains or loses access by surprise. It is worked out from your company's own roles and people, never from a record, and nothing in it changes what anyone can do today.
What It Compares
For each member of your company (owners and admins are never limited, so they are not compared), the report asks every action under a kind of record in the apps you have two questions: does today's gate let them do it, and does their role in that app allow the level it needs (See, Add, Change, Remove, or Export)? A difference is a place where today's gate says yes and the role says no, such as a Viewer who can still reply because the action never asked the role. Someone with No access in an app is the same both ways, so they are not a difference.
Only apps that have declared their kinds of records and actions in the permission catalog are compared. Helpdesk is declared today; the others join as they declare theirs.
Running It
Owners and admins run it with the action core.access.report, which is never for AI agents, API keys, or connections. It answers with:
- the model your company is on (the old one until you switch);
- how many people, actions, and kinds were compared;
- how many people would change and how many would not;
- the same by permission group;
- a page of the people who would change, each with the app, kind, and level they would lose, and how many actions it touches.
A page is 25 people by default and at most 100 (limit and offset).
It keeps a count for each difference (who, app, kind, level, and when it was first and last seen) in core_access_shadow. It keeps no name, no record, and no value. A difference it no longer finds is marked cleared, never deleted. Running it is not counted as an action in Usage.
What Is Planned
A screen for the report with a download, keeping each difference as it is today or changing it, and the switch itself are built in later parts of the permissions overhaul (Planned).
