Create Accountor Login
Docs

Portal Addresses

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

MountDev Ops Verticals documentation | Updated November 21, 2026

A portal address is where one client portal lives: a domain and a path, like example.com/clients or clients.example.com. This page covers the rules every address follows and the checks your workspace makes before it saves one. The page for choosing addresses is built, and so are the steps that connect a domain, the one-use switch between portals, and the answers that follow your addresses. Your workspace answers a visitor on each address you made live. The screens for making an address live and for choosing a sign in page are still being built and are marked (Planned).

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.

The Portal Addresses Page

Portal Addresses is a page of Verticals, after Setups and before Settings, for people who hold the permission below. It lists your portals, one row each:

  • Company Default is always first: where your team signs in. Until you change it, it is your current address with /account on the end.
  • One row for each vertical shows its name, how it is arranged (Under the Company Address, Behind a Shared Address, or Its Own Address), how many clients it has, its address, a state pill (Live or Draft), whether new sign-ups are on, and Change. A vertical with no address of its own says so and opens under the company address.
  • Forwarding Addresses lists every old address of a portal with Stop Forwarding. The platform's own address says Always On and has no button. Until an address has been made live there is nothing here.

Change opens one pop up for that portal: a Domain and a Path. As you type, the page asks the same checks the server makes and shows the one sentence for a clash, a reserved name, or a missing path, and which rule applies (a path is required on a domain your website uses and optional on any other). Save as Draft is only turned on when the address passes. A draft changes nothing anyone sees.

Apply One Address to All is a button at the top of the page. Type one domain and the pop up shows every portal with a path proposed from its name, which you can edit, and a check for each. Also move the company default is off at first, and the row says Left alone. Apply as Drafts saves every portal as a draft, or none if any one has a problem. Old addresses keep forwarding, so changing back never loses a link.

The Brand Kit shows its Sign-In Address read only, with a link to this page, so there is one place for it.

Making an address live is not on this page yet (Planned).

What an Address Is

An address is a domain and a path, shown as one line.

  • The path is required when the domain serves one of your websites. An apex such as example.com or www.example.com, or any domain your Websites app serves, belongs to the website, so the portal needs its own path, for example /clients. A path of / is refused with the sentence: "Your website uses this address, so the portal needs its own path, for example /clients."
  • The path is optional on any other domain. A subdomain such as clients.example.com can hold a portal at its root, or at a path of your choice (clients.example.com/hosting).
  • A path is one or two words of lowercase letters, numbers, and hyphens, each 1 to 40 characters, with no trailing slash. Capitals, dots, percent codes, and a query are refused. A leading slash is optional when you type it.
  • A domain is a plain website address like example.com, with no path, port, or number address. A pasted https:// at the start is removed.

Names the Workspace Uses

The first word of a path can never be one of the names your workspace and your sign-in service already use: account, api, mcp, c, drive, book, meeting, embed, fonts, handoff, enter, internal, _mdo, r, join, link, sign-in, sign-out, ops, terms, passkey, security, proposals, billing, chat, email, upload, assets, app, .well-known, robots.txt, sitemap.xml, and favicon.ico. A path may use one of them as its second word (clients/account).

Clashes

An address is refused, before anything is saved, with one plain sentence:

  • A page of your website. A path equal to, or under, a page or redirect of a website you serve on that domain is refused: "Your website already has a page at /pricing." The home page does not block a path. A removed page no longer blocks.
  • The other direction. The Websites app refuses, with the same check and the same kind of sentence, a page, post, doc, redirect, or collection item whose address is equal to, under, or above a portal's path on one of the website's addresses, and refuses to add a website address where a portal already shares a path with one of its pages or redirects. Both sides read the same lists, so a page and a portal can never end up on the same path.
  • Another portal. Two portals on one domain cannot have the same path, or paths where one starts the other (/clients and /clients/vip). The root of a domain overlaps every path.
  • An address another company holds. A domain is held by one workspace at a time. The refusal says only "That address is not available." It never says who holds it, and it reads the same whether the address is held, was given up, or was never used. Whether another company holds it is only known when a person saves the address, because taking the name needs a person's own act.
  • The limit. You can bring up to 50 domains. A new path on a domain you already brought costs nothing and does not count. The platform does not charge for addresses. Ask your provider if you need more than 50.

The Company Default and Drafts

The company default is where your own team signs in. Until you change it, it is your current address with /account on the end, and nothing is stored for it. Your Brand Kit's sign-in address is that default's domain.

Saving an address makes a Draft. A draft changes nothing anyone sees: no link, email, or cookie. A vertical has at most one draft at a time, and saving again replaces it. The names a replaced draft held are given up unless another address of yours, or an old address that still forwards, uses them. A person who holds the permission saves a draft with core.portal_addresses.save, which also takes the address's name for your workspace. An AI agent saves one with core.portal_addresses.draft, which holds no name: the name is taken when a person saves it or makes it live.

Apply One Address to All previews one domain for every portal, with a path proposed from each portal's name (Agency Clients becomes /agency-clients, editable), and names every clash before anything is saved (core.portal_addresses.apply_all.preview). A person applies it (core.portal_addresses.apply_all): every portal gets a draft, or none does. The company default is left alone unless it is included.

Going Live and Forwarding

A person makes a draft live with core.portal_addresses.live. An address can go live only when its DNS access and its certificate are in place, and the checks run again right then. The address it replaces is kept as a forwarding address with no end date, and one Portal Address Changed event is recorded with the vertical's number, the kind of change (went_live, changed, or retired), and the new domain and path, and nothing about any client. A draft never makes an event.

The platform's own address for your company default (/account) keeps forwarding and can never be stopped. An address your company retired can be stopped with core.portal_addresses.forwarding.stop. Webhook addresses are never moved by any of this (see Your Workspace Addresses).

Make It Live is on the Set Up screen of each draft (see Connecting a Domain below). Forwarding of old addresses in a browser is described under Old Addresses Keep Working below.

Old Addresses Keep Working

When an address is made live, the one it replaces is kept as a forwarding address with no end date.

  • Browser pages (a saved link, a link in an email already sent, the installed app's first page, and /account once the company default has moved) forward with a 308 to the same page on the new address, path and query included.
  • API, MCP, and webhook calls are never forwarded. They are answered where they are, because services do not follow redirects. So is any call that carries a key, and any call that is not a plain page request.
  • The installed app. An installed app is bound to its address and cannot move. The old address shows one short page once on each device ("This portal moved", with the new address and Install Again) and then forwards. The page holds no sign-in, session, or address in the marker it leaves.
  • Stop Forwarding is yours to choose for an address you retired. A stopped address answers the same plain not-found page as an address nobody has, so it never confirms that an account exists there.

Your workspace answers a visitor on each address from this list, and nothing changes for a company that has not made an address live: every address and page answers exactly as before.

Sessions and the Portal Switcher

  • Each address has its own cookie. It is host only (no domain), with its own path (/clients for example.com/clients, / on a host with no path), HttpOnly, Secure, and SameSite=Lax. Nothing is shared across hosts, and nothing is shared across the paths of one host.
  • Your Portals. A person who is a client of more than one portal moves between them with a one-use handoff, not a shared cookie. The workspace makes a token for that person and that one address (core.portal_handoff.make), valid for 60 seconds, stored only as a hash. The browser is sent to the other address's handoff page, which uses it once and then sets that address's own cookie. A second use, an expired token, or a token for another address shows the sign-in page, and nothing says which. The token carries no session, is never logged, and the referrer is not sent. The list (core.portal_handoff.portals) holds only the portals the person has access to, in this company.
  • The team signs in at the company default. A portal address shows only that portal. A team member who signs in on one is handed to the company default, and a client who signs in on another portal's address is shown the portal they are in.
  • Return addresses are checked. After sign-in a person is sent back only to a page of this site or to one of your own live addresses. Any other address is refused, so a link cannot send a person to another site.
  • Passkeys belong to a domain. A passkey made on clients.example.com also works on example.com, and example.org needs its own. A one-time code works on every address. After a first sign-in with a code on a domain with no passkey, the person is offered Add a Passkey Here once.
  • The installed app, per address. Each address has its own app details (name, address, and scope from its domain and path), so two portals on one domain are two installable apps.

Sign-In on Every Route

A signed-out visit to a portal's address is answered from that address's own row. The same protections apply on every route: the portal's own address, a page of one of your websites, a shared path, and /account.

  • The vertical comes from the address row, never from text in the visit. The company default belongs to no portal, so New Clients Start In decides, and that portal's New Sign-Ups switch applies.
  • New Sign-Ups Off removes Create an Account and refuses a sign-up with the one sentence "New sign-ups are turned off here. If you already have an account, sign in." Signing in is untouched.
  • The limits belong to the person. Five codes an hour and the pause after ten wrong tries count against the person and the network, never against an address, so trying another address resets nothing.
  • Nobody learns who holds an address. An address nobody holds, one that stopped forwarding, and a path nobody holds all answer the same plain page, with the same data, so nothing says whether a company exists there.

What a portal address serves. An address you made live shows your workspace from its own domain and path: its screens, files, and the installed app's details all use that address, and the portal's sign in cookie belongs to it alone. Pages and calls under /account on the same domain keep answering as they always did. A path on a domain that is not one of your live portals, and a domain nobody holds, answer exactly as before. The team signs in at the company default; the portal's own domain is for its clients.

Connecting a Domain

Each domain you bring (not each path) needs two things, and you do neither by hand. A domain you already brought is ready for every other path on it.

  1. DNS access. The page shows Waiting for DNS Access and one step: in Cloudflare, invite the address your provider names as a member with the DNS role only. A domain that is not on Cloudflare shows the move-first step instead (the Free plan is enough). No DNS record is ever shown, stored, or sent, in the screen, an email, a notice, or an answer.
  2. A certificate. When access arrives the platform adds the domain and its certificate and renews it by itself. The address shows Waiting for Certificate, then it is ready, and Make It Live works.

On the Portal Addresses page, a draft has a Set Up button. It opens the Set Up screen with the steps, where each one stands, what it costs, Check Again, and Make It Live. Make It Live asks once, with what changes, and works only when DNS access and the certificate are both done. DNS access usually takes a few minutes after you invite the address, and a certificate a few minutes to a few hours after that.

A background check looks again every 2 minutes for the first hour, every 10 minutes for the next 24 hours, then hourly, and moves the address on by itself. Once DNS access is there and no certificate has been asked for yet, the check adds the domain once; it is never added twice. Until your provider's side of this is connected, addresses stay on Waiting for DNS Access and nothing breaks. A person begins the steps with core.portal_addresses.dns.start (for a portal's address, or for the domain of its sign in page). A person or an AI agent reads where they stand with core.portal_addresses.dns.check (tool portal_addresses_dns_check), which never shows a DNS record.

Cost. Before you add an address the page says: "Adding an address is free. A new path on a domain you already brought costs nothing either. You can bring up to 50 domains." The platform does not charge for addresses. The 51st domain is refused with "You can bring up to 50 addresses. Ask your provider if you need more."

The Sign-In and Sign-Up Page

Each address has a choice of where its sign in and sign up page is. On This Address is the start. A Page From Websites uses a page of one of your websites that holds both a Sign In section and a Sign Up section (Sign In and Sign Up Sections). A page is accepted only if it holds both sections, is ready, and is not removed, and the refusal says which section is missing. An Address of Its Own is a separate domain, for example login.example.com, used only for the sign in and sign up page. Save it with core.portal_addresses.signin.save (kind own_address and a domain), which takes the domain's name for your workspace and saves a draft. It has the same DNS and certificate steps as any address (core.portal_addresses.dns.start with its sign-in domain), and a person makes it live with core.portal_addresses.signin.live. Until then the portal signs in on its own address. It serves only the sign in and sign up page: every other path on it answers the same plain page as an address nobody holds. It counts toward your 50 domains, and no portal can share it.

The sections draw the same card the portal's own address would draw, so nothing about signing in changes with the choice: the limit of five codes an hour and the pause after ten wrong tries belong to the person, never to an address, and the sign up card shows only while New Sign-Ups is on for that portal. If the chosen page is removed, set back to a draft, or loses a section, the portal signs in on its own address again and the owners and admins are told on the bell. The choice is kept, and the page serves the portal again once it holds both sections and is ready. Only a person chooses; an AI agent cannot, and there is no MCP tool for it. A signed-out visit goes to the page you chose, or signs in on the portal's own address (see Sign-In on Every Route). The screen for this choice comes in a later update (Planned).

Who Can Do What

The permission is Change where your client portals live (core.manage_portal_addresses). Owners and admins have it to start, and it can be given to anyone one by one in Permissions. Every action here needs it. A closed account cannot change an address.

ActionWhat it doesAI agent
core.portal_addresses.listLists every portal's address, state, and the forwarding addressesYes, tool portal_addresses_list
core.portal_addresses.checkChecks a proposed address and saves nothingYes, tool portal_addresses_check
core.portal_addresses.apply_all.previewPreviews one address for all portalsYes, tool portal_addresses_apply_preview
core.portal_addresses.draftSaves a draft that holds no nameYes, tool portal_addresses_save
core.portal_addresses.saveSaves a draft and takes its namePeople only
core.portal_addresses.apply_allSaves a draft for every portal at oncePeople only
core.portal_addresses.liveMakes a draft livePeople only
core.portal_addresses.signin.saveChooses where a portal's sign in and sign up page isPeople only
core.portal_addresses.forwarding.stopStops forwarding an address your company retiredPeople only
core.portal_addresses.dns.startBegins the DNS and certificate steps for a draftPeople only
core.portal_addresses.dns.checkShows where the DNS and certificate steps stand, never a DNS recordYes, tool portal_addresses_dns_check
core.portal_addresses.signin.liveMakes the domain for a portal's sign in page livePeople only
core.portal_handoff.portalsLists the portals the signed-in person may move to (Your Portals)People only
core.portal_handoff.makeMakes the one-use token for a move to another of the person's portalsPeople only

An AI agent never makes an address live, applies one address to all, or stops forwarding, because they change what every client and every email uses. There is no MCP tool for them, and no API key can run them.

Portal Address Changed

Workflows and webhooks can listen for the event verticals.address.changed. It is made from one hidden record of Verticals, so its history and export come from the same place as every record. It carries the vertical's number (0 for the company default), what happened, and the new domain and path.

Ask Us Anything

We’d love to hear from you!