Create Accountor Login
Docs

Setups

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.

Every update passes all 5,581 automated checks before it ships, and every screen change is walked through before release.

What a Setup Is

A setup is a package of data, never code, that sets a company up for one kind of business. It holds structure and starting choices only: which apps are on, your own modules and their fields, numbering, settings defaults, the email template's notice, roles and groups, announcements for your team, and reports. A web agency, a landscaping company, and an accounting firm would each have their own.

A setup is a copy kept in your own account. Nothing in it is ever another company's data, and nothing in it is ever your clients' data.

Screens for choosing, previewing, and applying a setup, for sharing one, and for the client portal a setup fills are Planned. Today a setup is read, previewed, applied, and undone through the actions below, which the screens will use.

What a Setup Never Holds

A setup never holds records or their values, people, roles given to people, keys, tokens, logins, connections, web addresses for webhooks, prices, or anything sealed. A setup that contains any of these is refused. Everything a setup adds that runs by itself or is shown to people is added turned off or already ended, for a person to turn on. Applying a setup never sends an email, never charges anyone, and never sends anything to a client account.

The Sections

Each section is filled through the owning app's own actions, so every permission check, validation rule, and Activity Log line is the same as on its own screen.

SectionWhat it isWhat is carriedIf you already have itUndo
apps AppsWhich apps are onApp namesAn app that is on is already there. An app your provider has not included is skipped and says Needs your provider.Apps stay on. There is no way to remove an app.
modules Modules and FieldsYour own modules and their fieldsNames, field labels and types, choices. Never values.The same module with the same fields is already there. A module with other fields is yours, and Add Beside adds the setup's version under a clear name, turned off.Turned off, never deleted. Its records are kept.
numbering NumberingThe Default Starting NumberThe starting number. Never a Company Code, which is the maker's own letters.A starting number you chose is yours. Existing records are never renumbered.Never changed back.
settings Settings DefaultsBusiness HoursTime zone, hours for each day, open all dayHours you already set are yours.Left as they are.
email_template Email TemplateThe notice and layout of replies in your email templateThe notice and reply layout. Never colors, logos, a website, a phone, or an email.A template you saved is yours.Left as it is.
roles Roles and GroupsRoles per app and permission groupsNames, levels, and which role a group gives in each app, by the role's name. Never who holds them.A role or group with the same name is yours (Add Beside adds it under a clear name).Removed only while nobody holds it.
announcements AnnouncementsMessages for your own teamThe message and its linkA message you already have is already there.Removed, and kept as removed.
reports Report TemplatesTeam reports as definitionsThe name and the blocks. Never a schedule, who gets it, or a report for one client.A report with the same name and blocks is already there.Removed, and kept as removed. Its runs stay.
home Home LayoutHow Home is arranged for your teamThe widgets and their order and size, as your company stored them.Home arranged the same way is already there. A Home you already arranged is yours and stays.Home goes back to how it was.
client_menu Client MenuThe menu your clients seeOne layout: what is hidden, renamed, moved, and linked.A menu you already have is already there. A draft you already have is yours and stays.The draft stays. It was never published.
dashboards Client DashboardsDashboards for the client portalEach dashboard's name and widgets as definitions. Never a client's numbers.A dashboard with the same name and widgets is already there.The dashboard stays, unpublished.
agreements Sign-Up AgreementsWhat clients agree to when they sign upEach name, whether it is Required or Optional, and its text or link.An agreement with the same name and wording is already there.The agreement stays retired. Agreements are never deleted.

A setup never publishes or sends anything. The client menu arrives as a draft, a dashboard arrives unpublished, and an agreement arrives retired, so no client sees a change and no one is asked to agree to anything until a person turns it on. Wording in an agreement is a draft: read it, make it your own, and then bring the agreement back on Sign-Up Agreements.

Announcements to clients, services for clients, and guided tours are Planned sections.

Start Blank

Start Blank is a setup every company already has. It turns nothing on. It holds the Plain client menu and the starter permission groups (Account Manager and Project Manager), which are already there. Applying it saves the Plain menu as a draft. Plain is also in Starting layout on Client Menu, together with the client menu of every setup you have applied.

Looking at the Setups You Hold

Action core.setups.list lists the setups your company received or made, and the ones it applied. Action core.setups.get shows one received setup with what applying it would do, or the ledger of one apply: every piece and what happened to it.

A setup you received is a read only copy. Nothing lets you change it.

Previewing a Setup

Action core.setups.preview shows exactly what applying a setup would do, and writes nothing. Each section is listed with each piece by name, and each piece is one of:

  • New: it will be added.
  • Already there: you have the same thing, and it is left as it is.
  • Yours: you have something different in the same place. It is kept unless you choose Add Beside.
  • Needs something: it cannot be added yet, for example an app your provider has not included.

The preview also says plainly what a setup never changes: records, people, roles given to people, keys, billing, and anything you already set up.

Applying a Setup

Action core.setups.apply applies a setup you hold. Only owners, admins, and people who hold Set up the workspace from a setup may apply one. An AI agent or an API key never applies a setup.

  • Each piece is added only when it is new, as the person who applied it, through that app's own action.
  • Nothing you already have is edited, replaced, or deleted. The only choice is Add Beside, which adds the setup's version under a clear name, turned off where that applies.
  • Each piece is written on its own. A piece that fails, or that you may not change, is reported on that piece, and the rest still apply. A piece that fails leaves nothing behind.
  • Everything is recorded in a ledger with each added piece's fingerprint, and the Activity Log says what was applied.
  • A closed account is read only, so it cannot apply a setup.

Undoing a Setup

Action core.setups.undo takes back an apply. Use action core.setups.preview with the undo choice first to see exactly what will happen.

Undo touches only what that apply added, and only while it is still as it was added. A piece you changed since stays, and the answer lists it ("You changed this, so it stays"). A module is turned off, never deleted, so its records are kept. Apps stay on. Numbering, settings defaults, and the email template are left as they are. A role or group is removed only while nobody holds it. Undo never touches anything of your own.

Who May Do What

  • Set up the workspace from a setup (core.manage_setups): owners and admins to start, and any role that holds it. It is needed to look at, preview, apply, and undo setups. Each piece also needs the permission of the app it changes. A piece you may not change is skipped, and the answer says so.

AI Agents and the API

Your AI agents and API keys can read what a setup would do, but only a person applies or undoes one.

  • List the setups (action core.setups.list, MCP tool setups_list).
  • Read one setup or one apply's ledger (action core.setups.get, MCP tool setups_get).
  • Preview an apply or an undo without changing anything (action core.setups.preview, MCP tool setups_preview).
  • Apply a setup (action core.setups.apply) and undo one (action core.setups.undo) have no MCP tool, because they change the company.

Making, Sharing, and Verticals Planned

Making a setup from your own structure, sharing it with your partners or clients, updates that arrive as offers, and verticals (a named client portal for one group of clients, with more than one per company) are Planned. A setup you make will be checked for text that names you, your people, or your own web address before it can go out.

Ask Us Anything

We’d love to hear from you!