The Setup Library
Part of the MountDev Ops Verticals documentation. Updated November 21, 2026
MountDev Ops Verticals documentation | Updated November 21, 2026
The Setup Library is the page of Verticals where you install a ready-made setup, keep it up to date, undo it, make your own, share it, and give out a Setup Code. It is the same for every company. Everything on it needs the permission to set up the workspace (owners and admins by default, or anyone whose role allows it). A client portal user never sees it.
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 8,865 automated checks before it ships, and every screen change is walked through before release.
What Is in a Setup
A setup is structure and starting choices only: which apps are on, modules and fields, templates, numbering, client menus, dashboards, agreements, and messages. It never holds records, people, keys, connections, or prices. A paid package keeps its price in a Services You Sell entry, never in the setup.
Setups You Can Install
Setup Library lists every setup you can install, each as a card with its maker, its version, whether it is free or a paid package you already bought, what it adds by section, and where it came from: your provider, a Setup Code, the built in Start Blank, or you.
- See What It Changes shows every piece by name before anything is added: New (will be added), Already There (you have the same), and Yours (you have something different, which is kept unless you choose Add Beside). It is the same preview Set Up Another Vertical uses, and it saves nothing.
- Install applies the setup. Nothing you already have is overwritten, and anything that runs by itself (a message, a menu, a dashboard, an agreement) arrives turned off or as a draft for a person to turn on. Installing makes a vertical, named after the setup, which you can rename.
- Installed, version N shows what you have. See What It Added lists every piece and what happened to it.
- Undo This Setup takes back only what the setup added and only while you have not changed it. A piece you changed stays and is listed. A module that holds records is turned off, never deleted, and apps stay on.
Nothing offered to another company is ever listed here. Each company reads only its own list.
Add a Setup Code
A maker can give out a Setup Code. Paste it into Add a Setup Code and choose Add Setup Code. The setup arrives in a moment as a read only copy, and nothing changes until you choose Install. A code that was withdrawn, or one that does not exist, adds nothing.
Updates
When the maker publishes a newer version, and you installed an earlier one, the card shows Update Ready and the vertical's Overview shows Setup N Is Ready. See What Changes shows only what is new in the newer version. Nothing changes until you choose Update This Setup, and an update never adds again a piece you removed and never overwrites a piece you changed. A company that received a setup but did not install it is not sent updates. A retired setup shows No Longer Offered, and what you installed stays.
Make a Setup
Make a Setup copies your own structure so you can reuse it or share it.
- Tick the pieces to include. Each section lists its pieces by name, all ticked at first.
- Give it a name and one sentence, then choose Save Draft. A draft is not published and sends nothing.
- The text scan reads the draft. An email address, a phone number, one of your own web addresses, or the name of one of your people or clients must be replaced before it can be published. The screen says where it is. Change the text in your own setup, then save the draft again.
- Choose Publish. The first publish is version 1, and each later publish is the next version, with a note on what changed. A company that installed an earlier version is offered the new one.
You can install your own published setup like any other. It appears under Setups You Can Install as made by you.
What a Maker Sees
Counts only: how many accounts hold each version of a setup, and how many of them installed it. You never see which accounts, and never which pieces a company kept, changed, or removed. A setup travels as a copy of its body and its number, with your company's display name, and nothing about the company that receives it.
Selling a Paid Package
A paid package is an entry in Services You Sell (Subscriptions) that is marked as selling a package and linked to one of your own published setups. Its price is the product's, like any service you sell. A client buys it the way it buys any service, and Invoices bills it. After the purchase, the next time you send your clients their services, the client that bought it is offered the install, once, in its own Setup Library. A free package needs no purchase: share it, or give out a code. Verticals never charges, never holds a price, and never touches your payment provider. See Services You Sell.
A partner earns on a package only when its program lists that entry in Earns On as a package. A free install earns nothing, and a refund reverses what was earned.
For AI Agents
An agent can list the Setup Library (action core.setup_library.list, tool setup_library_list) and save a draft setup (action core.setups.make.save, tool setups_make_save). A draft is only a draft: a person publishes it. Agents never publish, share, retire, make or withdraw a Setup Code, install, update, or undo, because those change a company or what other companies receive. Setup Codes are never listed to an agent.
Actions
core.setup_library.list: the cards, your own setups, and the counts. For people and AI agents.core.setup_library.pieces: every piece you could put in a setup, by section. People only.core.setups.make.save: save a draft. People and AI agents.core.setups.make.publish: publish the draft as the next version. People only.core.setups.share: share the current version with the accounts you provide for. People only.core.setups.retire: retire a setup. People only.core.setups.code.make,core.setups.code.withdraw,core.setup_library.codes: make, withdraw, and list your Setup Codes. People only.core.setup_library.redeem: add a Setup Code from another company. People only.core.setup_library.install,core.setup_library.update.preview,core.setup_library.update,core.setup_library.undo: install, see an update, update, and undo. People only.
