What Your Account Can Use
Part of the MountDev Ops Workspace documentation. Updated November 5, 2026
MountDev Ops Workspace documentation | Updated November 5, 2026
Some apps and services are not part of every account. Your plan includes some, and a provider can offer others. What your account can use is called an entitlement. Everyone's account works the same way: nothing depends on who you are, only on what your account has.
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 2,956 automated checks before it ships, plus screen tests on 9 screen sizes for everything it changes.
What You See
On Settings, Apps, an app your account does not have says so in plain words, and shows the one control that fits how your provider offers it:
- Turn On: you turn it on yourself. The app shows up in your menu and the app picker at once.
- Apply: you answer a few questions, and your provider decides. The tile says Waiting while your application is with your provider. If your provider declines, the tile says Declined and shows the reason, and you can Apply Again.
- By Invitation: you cannot apply. Your provider invites the accounts that can use it. Ask your provider.
An app you do not have is left out of your menu and the app picker, and its screens refuse with "Ask your provider". Members see the same words without the buttons. Only people whose role allows it turn things on and apply (action core.entitlements.list lists what your account has and what is offered to it).
Turning on Something Yourself
An owner or admin presses Turn On (action core.entitlements.turn_on). Only something your provider lets you turn on yourself can be turned on this way. Something you turned on yourself can be turned off again (action core.entitlements.turn_off); something your plan or a provider gave you cannot.
Applying
Apply opens a form with the questions your provider set, up to eight. Required ones are marked. Press Send Application (action core.entitlements.apply). Your answers are kept in your own account, in your region. Your provider sees that an application came in and reads the answers through the access your account gave it, so they are never copied into the provider's account.
You can have one application waiting at a time. When your provider answers, you see the result on the same tile. An approval turns the app on at once, with nothing to install or wait for.
Managed Services
A managed service is one your provider does the work for. The work runs on your own data, in your own region, using the access your account gave your provider. Your provider never copies your data into its own account. Everything it does is in your Activity Log with its name.
You choose whose metered resources the service uses: your provider's, billed as usage at your provider's prices, or your own key where the service supports it (action core.entitlements.resources.set). You can end your provider's access at any time with End Provider Access (action core.entitlements.provider.revoke). The service stops at once.
If You Offer Things to Other Accounts
An account that offers things to other accounts also sees two cards on Settings, Apps. They show only when there is something in them.
- Your Offers lists what you offer and how each one is given: Turn On, Apply, or By Invitation. Change sets the name, the way, the questions on the application (one a line, up to eight, a star at the end of a line when an answer is required), whether it is a managed service, and whether the account may use its own key. These are actions
core.entitlements.offers.listandcore.entitlements.offers.save. - Applications is your queue. Each application shows what it is for, its number, and its date. Approve turns the entitlement on for the account. Decline asks for a reason, which the account sees. Your account keeps only the application's number and your decision, never the answers. These are actions
core.entitlements.queueandcore.entitlements.decide.
Showing an offer to an account, granting it to an account, and taking it back are actions too: core.entitlements.offers.share, core.entitlements.invite, and core.entitlements.revoke. The first offers are made through these actions; a catalog screen for offers is planned (Planned).
What Is Kept, and Where
- Your account's entitlements, applications, answers, decisions, and reasons are kept in your own account, in your region.
- A provider's account keeps its offers, one task for each application with the application's number and the decision, and the messages waiting to go. Never the answers.
- Messages between two accounts hold numbers and decisions only. They wait in a queue and are tried again until they go through; ones that cannot be delivered after ten tries are marked and kept, not lost.
- Nothing is stored outside the two accounts. Turning something off never deletes your records.
Who Can Do What
- Owners, admins, and anyone whose role allows it turn things on, apply, choose resources, and end a provider's access (the switch Turn on, apply for, and manage what your provider offers in Settings, Permissions). The same people, with Offer, grant, and decide on entitlements for other accounts, offer, decide, and invite for their own account. A person whose role gains a switch starts seeing the matching cards; one who loses it stops.
- Everyone else sees the plain words and cannot change anything here.
- AI agents and API keys cannot use any of these actions. They change who can use what, which stays with people.
- The platform puts a plan's entitlements on (action
core.entitlements.install), takes in messages from another account (actioncore.entitlements.receive), and lets a provider read an application through the access the account gave it (actioncore.entitlements.application.read). No person's role holds these.
For People Building Apps
An app, or one action, says which entitlement it needs in its manifest with entitlement: 'key'. The platform refuses it for an account without the entitlement, hides the app and its records, and keeps it out of the app picker. Code never checks which account it is. The release check fails a change that compares an account's id or a company's name in a condition.
