Create Accountor Login
Docs

Clients in a Vertical

Part of the MountDev Ops Verticals documentation. Updated November 19, 2026

MountDev Ops Verticals documentation | Updated November 19, 2026

Each client is in at least one vertical, and may be in several. A vertical's published client menu, dashboards, and sign-up agreements reach only its own clients, so a company that offers more than one kind of portal can give each group of clients its own.

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.

Which Vertical a Client Is In

A client with no choice of its own is in the vertical chosen in New Clients Start In, or your first vertical if you have not chosen one. Open a client company in CRM and use its Vertical card (it shows when you have two or more verticals and the client has a workspace account), see each vertical the client is in with a Primary or Also In word, and use Make Primary, Take Out, or Add to a Vertical with Add as Also In (action core.vertical_memberships.save, people only). The card reads which verticals each client is in with core.vertical_memberships.list. A client always stays in at least one vertical, so Take Out is not offered on its last one. The older action core.verticals.client.set still moves a client so that one vertical is its only one, and is what an AI agent uses. The card reads which vertical each client is in with core.verticals.clients, for people only. Moving a client sends it the client menu of its new vertical, or the default menu when that vertical has none published. A company with one vertical sees no picker and no difference.

A Client in More Than One Vertical

A client can be in several verticals. One is its Primary, where it lands and the vertical whose client menu its own workspace follows, and the others are Also In. A vertical's client count counts every account in it, so a client in two verticals counts once in each. The client's Vertical card lists each vertical it is in, and Your Portals in the portal's menu is (Planned), because it comes with the client portal page. The card and the rules behind it:

  • Save a membership (action core.vertical_memberships.save, people only, not for AI agents, API keys, or clients): choose the client account, the vertical, and one of Primary (adds the vertical if the client is not in it and makes it the Primary, keeping its others as Also In), Also In (adds it and leaves the Primary alone), or Remove (takes the client out of it).
  • A client always stays in at least one vertical in use. Taking away its Primary hands the Primary to the next vertical it is in. A vertical that is closed is skipped, and a client in no other vertical starts where new clients start.
  • A membership that is taken away is kept with the date, never deleted, and adding it again brings it back.
  • Only one of your own verticals in use can be chosen, and only a client account your company provides for.
  • See every vertical each client is in (action core.vertical_memberships.list, people only) lists each client with its Primary and the others, by number and name.
  • A client you never changed keeps the vertical it has now. The older record of which vertical a client is in is read when a client has no membership of its own, and is never changed again. Nothing stored is rewritten.
  • What a client sees in each portal is that portal's own client menu and dashboards. A dashboard published to all clients of a vertical reaches its Primary and Also In clients alike, and a dashboard cannot be published to a chosen client that is not in its vertical. Nothing a client does in one portal is hidden from another beyond what its records already share, because it is the same account.
  • Sign-in stays one sign-in for the whole company, and moving to a different company is still Switch Company.

New Clients Start In

Open Verticals, then Settings, and find New Clients Start In. Choose a vertical and press Choose Vertical (action core.verticals.start_in.set, people only). Clients already placed do not move. Each vertical on the Verticals page shows how many clients it serves, as a number only.

What Each Vertical Has of Its Own

  • Client Menu: one draft and one published layout for each vertical. Publishing sends it to only that vertical's clients, and Reset to Default sends the default menu to only those clients (actions core.menu.layout.save, core.menu.layout.publish, and core.menu.layout.reset, with the vertical). See Client Menu.
  • Dashboards: each dashboard belongs to the vertical it was made in. Published to all clients, it shows to that vertical's clients only, and it cannot be published to a client of another vertical. See Dashboards for Your Clients.
  • Sign-Up Agreements: each vertical has its own list, order, and Required or Optional, and a sign-up link made for a vertical asks only for that vertical's agreements. See Sign-Up Agreements.

Everything made before verticals belongs to your first vertical, so nothing you already set changes. Announcements to a vertical's clients come with the Announcements app's audience choice and are Planned.

Who Can Change It

Owners and admins, and anyone whose role holds Set up the workspace from a setup. An AI agent you connect can read which vertical each client is in (tool verticals_clients) and put a client in a vertical (tool verticals_client_set), the same save as the Vertical card, each its own permission and off until a person turns it on for a connection. It cannot choose where new clients start. It can read a vertical's published layout and agreements with the same tools as before.

Ask Us Anything

We’d love to hear from you!