Create Accountor Login
Docs

MountDev Ops Verticals

How MountDev Ops Verticals works, page by page. Updated November 21, 2026

MountDev Ops Verticals documentation | Updated November 21, 2026

Verticals is the app for the client portals your company offers. A vertical is one client portal for one group of clients: its own client menu, dashboards, sign-up agreements, and services, made from a setup or from nothing. Every company can add it, the same way, and turn it off again without losing anything.

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 Here Today

Verticals is in the Sales part of the menu. Its pages are Verticals, Your Services for Clients, Setups, Shared Pieces, Setup Library, and Portal Addresses (for people who may change where client portals live), with Settings last. Opening a vertical switches the workspace into that vertical's own place, with a column of its own, a strip across the top that says who is affected, and one Exit Vertical Setup button. Only your own people see a vertical's name. Your clients never do.

A vertical is made when you apply a setup. The first apply makes your first vertical, and Set Up Another Vertical makes the next. Applying a setup never overwrites anything you already set, and everything it adds that runs by itself arrives turned off.

An AI agent can list your verticals (action core.verticals.list, tool verticals_list), read one (core.verticals.get, tool verticals_get), rename one (core.verticals.rename, tool verticals_rename), see which vertical each client is in (verticals_clients), put a client in a vertical (verticals_client_set), and turn a vertical's new sign-ups off (verticals_signups_set, never on). Reading one shows how many clients it serves and whether new sign-ups are on or off. Each tool is its own permission, off until a person turns it on for a connection. The Welcome is marked as read with core.verticals.welcome, for people only. Applying and undoing a setup are people's only.

In These Docs

  • The Verticals Page: each vertical with Open, and Set Up Another Vertical with its preview of exactly what changes.
  • Inside a Vertical: the column, the strip, Exit Vertical Setup, the Welcome, the Overview, Rename This Vertical, Preview as a Client, and the Save for Clients bar.
  • Clients in a Vertical: which vertical each client is in, New Clients Start In, and what each vertical has of its own.
  • Groups of Verticals: the Groups card, where you name a set of your verticals and see what it reaches first, and the triggers Workflows can listen for.
  • Shared Pieces: the Shared Pieces page, where you share a client menu, a dashboard, or a sign-up agreement across verticals, see where it is used, and make your own copy.
  • The Partners Card: the card on a vertical's Overview that shows the referral programs aimed at it, with counts only.
  • New Sign-Ups: the switch on each vertical, off at first, that decides whether new people can create an account.
  • Portal Addresses: the page where each client portal's address is set (a domain and a path), Apply One Address to All, drafts, forwarding addresses, and what an AI agent may do.
  • The Setup Library: install a ready-made setup, keep it up to date, undo it, make your own, share it, give out a Setup Code, and sell a paid package.
  • Setups: the setups you have, what an apply added, and Undo This Setup.
  • Your Services for Clients: offering your own tools to your clients' apps and AI assistants, moved here from Publish in Integrations.
  • Turning Verticals On and Off: who may open it, and what turning it off does.

Ask Us Anything

We’d love to hear from you!