Kinds and Levels
Part of the MountDev Ops Subscriptions documentation. Updated November 17, 2026
MountDev Ops Subscriptions 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.
Subscriptions describes what it holds in the permission catalog, so permission screens and connection lists can learn what it can do. This changes nothing about who may do what in Subscriptions today. That is still decided by roles, permission groups, and the Subscriptions permissions.
What Subscriptions Declares
Its Client Actions are declared as an area with the levels they use:
| Area | What it covers | Levels |
|---|---|---|
| Client Actions | The actions your clients can start from their own account, with their cost, limits, and who may start each | See, Change, Remove |
The rest of Subscriptions (its products, services, subscription lines, and the monthly run) are described by their record kinds and by each action's area until their actions declare their own kind and level.
How the Levels Map
Each level maps to the connection level an action already has: See is Read, Change is Write, and Remove is Delete. The permission id and level each action gives a connection did not change.
