Demo Accounts

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.

A demo account is a full workspace filled with made-up data, made for showing your product to a prospect. You make one in seconds from an industry starting set, on the Demo Accounts page or by asking your AI agent, and it ends on its own after 14 days. Every account has demo accounts, the same way, at no charge.

Demo accounts show made-up data only. The data stays fixed and changes are not saved, which keeps demos light on resources. Never enter real customer information.

What a Demo Account Is

• Its own workspace. Each demo account is a new workspace, kept in the same data region as your own workspace. Nothing is copied from your workspace or any other.
• A made-up owner. Each demo account has one person: its industry set's made-up owner (for example Robin Example, robin.example@example.com, for Landscaping). You open it with Open Demo and look around as that owner. Nothing about you is stored in the demo, and it is not in your list of companies.
• Made-up data only. Every company, person, invoice, project, and ticket in it comes from the industry starting set. Every name says it is made up (Example, Demo, Test, or Acme), every email address is at example.com, and every phone number is in the fictional 555-01xx range. Each made-up person has one name, used the same way everywhere, and every invoice's lines add up to its total.
• Free. A demo account is never billed and never counted as a customer.
• No limit on how many. You can make as many demo accounts as you need.

Industry Starting Sets

Each demo account starts from one of five sets. Each set turns on the apps it uses; you can choose fewer.

Every set also has one made-up lead, task, activity, website, product, payment, folder, form entry, and template where its apps have them, so no list in the demo is empty. When you turn an app off, its records are left out.

Each set's made-up owner, the one person in its demos:

What to Show

What to show (the about of core.demo.create) also sets how many records of each kind the demo is made with, within its starting set. For example, "30 patients, 4 open invoices, and a booking form" makes a demo with 30 contacts, 4 open invoices, and a form called Booking Form Demo (when Forms is one of its apps). Everything it makes is made up, the same way as the rest of the set.

It understands a number right before one of these words, singular or plural:

• Numbers are digits (1,000 reads as 1000), the words zero to twenty, or "a" and "an" for one.
• Words between: up to two plain words may come between the number and the word ("4 open invoices", "3 monthly lawn plans"), or one after "a" or "an" ("a booking form"). Words such as of, and, or, more, than, few, and lot are never read across, so "a lot of clients" sets nothing. A word right before another of these words only describes it, so "a contact form" is a form.
• Phrases: a comma, period, semicolon, colon, bracket, or line break ends a phrase, and nothing is read across one. Only the first 500 characters are read, and the first mention of each kind counts.
• Limits: at most 200 of any kind, and at most 10 forms. At least 1 client and 1 contact, since the rest link to them.
• Only the demo's apps: a kind whose app the demo does not have is left out, and a kind it does not mention keeps the set's own count.
• Nothing else changes: the text never sets a name, an address, or any other value. Anything it does not understand is left alone.

The demo account list shows what it understood (shows, for example "30 contacts, 4 open invoices, and 1 form").

Making a Demo Account

Use New Demo Account on the Demo Accounts page (see New Demo Account), or ask your AI agent to make a demo account (action core.demo.create, tool core_demo_create). It needs:

• Name: what the demo account is called, up to 80 characters. It becomes the demo workspace's company name.
• Industry starting set: landscaping, dental, agency, bakery, or law.
• Apps (optional): which of the set's apps are on. Leave it out for all of them. An app the set does not have is refused, and the message lists the set's apps.
• What to show (optional): a short description of what the demo is for, up to 500 characters, kept with the demo account. Numbers in it set how many records of each kind it has; see What to Show.
• Client Experience (optional): what the demo's people see at /account: the menu, the Home cards, and the notifications. See Client Experience below. Leave it out for the usual workspace.

The demo account is Building at first. Within seconds your workspace makes the new workspace, adds the apps, fills it with the set's records through the same record actions the screens use, and marks it Ready. From then on its data is fixed. If a step fails it is tried again a few times; after that the demo account shows Problem, and you can delete it and make another.

A demo account is always made for a person, who opens it with Open Demo, so an API key cannot make one.

Your Demo Accounts

Your AI agent can list your demo accounts (action core.demo.list, tool core_demo_list), newest first. Each shows its name, its industry starting set, its apps, what it was made to show and the counts it understood from that, its Client Experience, whether it is Building, Ready, or Problem, when it was made, when it ends, when its share link stops (shared_until, empty when no link is on), and who made it (made_by). The list also gives the five starting sets, the plain notice above, and options: the menu items, Home cards, notification kinds, and menu groups a Client Experience may name, each with its app.

Export Everything includes the list as Company/Demo Accounts.csv, with each demo's Client Experience in a short line (for example "Menu: Home, Your Bills | Home: invoices.owed | Notifications: none"). The made-up data inside each demo stays in the demo.

Client Experience

While a demo account is being made, you shape what its people see at /account, so your client sees what their own experience is going to be like: the menu, the Home cards, and the notifications. Your provider's person who opens the demo and a prospect on a share link both see it. Every account has it, the same way.

Give it when you make the demo (the experience of core.demo.create), or change it while the demo is Building with core.demo.experience_update (tool core_demo_experience_update): the demo account's id and the whole experience, which replaces the one before. Leave the experience out to put back the usual workspace. It has up to three lists, each in the order it shows:

• menu: the menu's items, each { key, name, group, on }. The key is a menu entry of the workspace or of one of the demo's apps, such as app:crm, app:invoices, or page:members. The name (optional) is plain text, up to 40 characters; leave it out to keep the usual name. The group (optional) is one of today, work, customers, money, sites, auto, or settings. Set on to false to hide an item. Home (page:home) is always first and is never hidden or renamed: leave it out, or put it first, on, with no other name.
• home: the Home cards, each { key, on }, such as core.needs (Needs You Today) or invoices.owed.
• notifications: the kinds of notification that show, each { key, on }, named by app and kind, such as invoices.billing_run or meetings.meeting.

A list you leave out keeps the usual one. A list you give shows only its items with on true, in its order; anything not in it is hidden. For example:

{
  "menu": [ { "key": "app:invoices", "name": "Your Bills" }, { "key": "app:crm", "name": "Your Account", "group": "customers" }, { "key": "app:files", "on": false } ],
  "home": [ { "key": "invoices.owed" } ],
  "notifications": [ { "key": "invoices.billing_run" } ]
}

Each item is checked against the demo's own apps. A refusal says what is wrong in plain words: a key the demo does not have (with the keys it has), an item listed twice, more items than the demo has, a name that is not plain text or is too long, a group not on the list, Home hidden, renamed, or not first, or a field or list the experience does not have.

Inside the demo:

• The menu is Home, then the shown items, in order, with their names and groups, as the menu's places. A hidden app is left out of Recent too.
• Home shows the chosen cards, in order. Arrange Home is not offered, since the demo's Home is set.
• The bell shows only the chosen kinds, and its count and the device's notice count only those. The bell's list (core.bell.list) gives them in the experience's order, each with its place as rank.

The experience only hides, orders, renames, and regroups what a person in the demo may already see; it never shows anyone something their access does not allow.

When the demo is built, its experience is written into the demo before its data is frozen, and is fixed with the rest from then on. Changing it after the demo is finished is refused: "The demo account (name) is finished, so its Client Experience is fixed with the rest of its data. Make a new demo account to show a different one." If a change arrives while the demo is being built, the demo keeps the experience it was built with, and so does its line in your list.

Who can: anyone who may make demo accounts (core.demo_accounts.create), and their AI agents. A workspace that is not a demo is never changed by any of this.

When a Demo Account Ends

Every demo account lasts 14 days from when it was made. On its end date your workspace deletes it in full, the same way as Deleting a Demo Account, and its line in your list. The person who made it and your workspace's owners get a notice in the bell: "Demo Account Ended", saying the demo reached its end date and was deleted. The Activity Log says so too. If part of it cannot be deleted just then, your workspace tries again every hour until it is gone.

Deleting a Demo Account

To delete a demo account sooner, type its name to confirm (action core.demo.delete). The Activity Log says who deleted it. A wrong name is refused and nothing changes. Deleting is for people only: AI agents and API keys cannot delete a demo account.

Deleting removes everything of the demo, all of it made up:

• its workspace and everything stored in it;
• its Activity Log and record history, kept month by month;
• its search index;
• its files, in its data region;
• its place in the directory that says where each workspace runs.

The demo leaves your list at once, and its share link stops. If part of it cannot be deleted just then, the answer says so (finishing), the demo stays out of your list and cannot be opened or shared, and your workspace finishes deleting it within minutes, trying again until it is gone. Nothing of any other workspace is touched.

Only demo accounts can be deleted this way. Each demo workspace knows which workspace made it and refuses anyone else, and an ordinary workspace can never be deleted this way: its place in the directory is forgotten only after the demo itself confirmed which workspace made it.

Who Can Use Demo Accounts

Three switches in Settings, Permissions decide who may use demo accounts. Owners and admins have all three to start, or anyone whose role allows it:

• See and open the demo accounts your company made (core.demo_accounts.read): lists them, and Open Demo.
• Make demo accounts with made-up data (core.demo_accounts.create).
• Share and delete demo accounts (core.demo_accounts.manage): Share Demo Link, Turn Off Link, and deleting.

Your demo accounts are your own. No other account, your provider's included, sees them.

Inside a Demo

A demo works like any workspace: every screen opens and every button runs with the same checks. What makes it different is that its data is made up, stays fixed once the demo is finished, and nothing in it ever reaches a real person or service.

The Demo Label and the Demo Banner

Every screen of a demo shows a small Demo label in the header beside the page's title, so it never scrolls away. Choose it for a short note that says:

• "This is a demo with fixed sample data. Changes are not saved, which keeps demos light on resources."
• "Email goes only to a test address, texts and calls are simulated, and payments run in test mode."
• When the demo ends (for a prospect, when their link stops working).
• Opened by and the name of the person who opened it with Open Demo. A prospect on a share link has none.
• Back to and your company's name, for the person who opened it with Open Demo. It signs you out of the demo, and your own workspace opens again. A prospect has no Back button.

Home starts with the Demo banner, with the same words. The workspace learns that it is a demo from the demo itself (the demo part of core.home: its end, your company's name, and whether this is a prospect), never from which account it is.

Only the Demo's Own Apps

A demo shows only what is in it:

• No Managed Services anywhere: not in the menu, not on Home, and not in Usage. No Partner Program, and no real website or domain.
• All Apps and Services lists only the demo's own apps. Browse All Apps is not offered.
• Choosing the company's mark at the top opens the Demo label's note, since a demo has no list of companies.
• A page the demo has nothing for says plainly "This part of the workspace is not part of the demo." with Back to Home. A page never shows an error's own technical text.

What You See When You Try Things

• Uploads are off. Each upload button is turned off and says "Uploads are off in a demo."
• Send Email on a contact says: "This is a demo: email goes only to a test address, never to the person. It shows on the timeline, marked Test address only (demo)." The email shows on that contact's timeline for this visit, marked Test address only (demo). Each demo is made with its owner as CRM's sending address, so Send Email works.
• Record Payment on an invoice reads Record Payment (Test Mode).
• An invoice paid by a saved card says Would be charged automatically (demo) instead of Charged automatically.

The Demo's Today and Its Bell

• The demo's today. A demo's made-up data is dated from one fixed day, the demo's today (November 7, 2026), so every demo of a set is the same. Anything that counts what is coming up counts from the start of that day, never from the real date: CRM's Meetings This Week lists the demo's meetings in the 7 days after it, from Meetings as well as the meetings logged in CRM, whoever hosts or attends them, and a prospect's Upcoming Meetings card counts the same way. CRM's Calendar opens on the demo's month, marks the demo's today, and shows the demo's meetings from Meetings as well as the ones logged in CRM. An ordinary workspace counts from now, its Meetings This Week lists the meetings logged in CRM, and its Calendar opens on the real today, as before.
• Made-up times. Every made-up time in a demo is on a business day between 9 AM and 5 PM Pacific: the demo's meetings are on the business days after its today (November 9 to 16, 2026), and its requests, calls, and payments are on the business days before it.
• The bell holds only the demo's own notices. For a prospect on a share link, it shows the same notifications as their Home, worked out from their own made-up records, with the unread count on the bell; Mark Read and Mark All Read lower it for that visit only. Notices about your own account, such as "Demo Account Ended", your plan, Get Help, and connections, are never rung inside a demo and never shown there, in the bell, its count, or the notice on a device, for you or a prospect. They stay in your own workspace.

Changes Are Not Saved

While a demo is being made, its made-up companies, people, and records are saved as they are added. Once the demo is finished, its data stays fixed:

• Every action still runs and answers as usual, so a change looks real in the moment, but nothing it changed is kept.
• Background work, such as reminders, automations, and scheduled jobs, does nothing in a finished demo.
• A finished demo keeps no usage counts. Demo accounts are never billed.
• Signing in to a demo (Open Demo or a share link) and Turn Off Link signing its visitors out still work in a finished demo; nothing else is kept.

Nothing Real Comes In

A demo holds made-up data only, so anything that would bring real information in, or connect the demo to a real service, is refused. This is true while the demo is being made and after it is finished:

• Imports of any kind, including records, settings, time, and imports from other services.
• File uploads.
• Connected services, AI agent and app connections, API keys, webhooks, inbound webhooks, email delivery settings, sending logins, and Network Drive keys.
• Saving any password or key, and revealing a saved login.
• Email sent to one of the demo's forwarding addresses, and posts to its inbound webhooks.

Each of these says: "This is a demo account with made-up data only, so nothing can be brought in or connected here."

Nothing Is Sent

A demo never sends anything real:

• Email goes nowhere. While a demo is being made, each email is listed in Recent Emails with the status Simulated and the note "Not sent: this is a demo account." No email provider or mail server is asked.
• Payments never reach Stripe. Charging, refunds, payouts, and payment checks in a demo say: "This is a demo account, so no payment is made. Payments here never reach Stripe."
• Webhooks and automation calls to outside services are not sent. Each one is closed in its delivery list with the note "Not sent: this is a demo account."
• Outside services are never called, and booking link names, which every workspace shares, are never taken by a demo.
• Requests to your provider, such as Managed Services pages, website backups, and website files, are not sent. They say: "This is a demo account, so requests to your provider are not sent. Nothing here reaches any real service."

The Bell Inside a Demo

The bell inside a demo holds the demo's own made-up facts only, and never a notice about your own account, such as a demo ending or a change to your plan. Those wait for you in your own workspace.

• Your team's view. Signed in through Open Demo, the bell lists the demo's own facts worded for the team: a new request from the demo's client, an invoice out with them, a meeting coming up, a proposal waiting for them to review, a document out to sign, and the like. They come from the demo's own made-up records, so they match the screens.
• The prospect's view. A share link's visitor sees the same facts worded for them, the ones their Home shows.
• Marking read works while you are looking around. Like everything else in a demo, it is not saved: the next visit starts with them unread again.

The Time Inside a Demo

Every demo is dated from its own day, and its screens show a work day, so Home greets you by the demo's business hours (9 AM to 5 PM) rather than by the clock on your computer. Outside a demo, Home greets you by your own clock as before.

The Demo Accounts Page

Open the company switcher (your company's name under the greeting, or Workspaces in the Account menu) and choose Demo Accounts, under the companies and Add a Company. It shows for anyone who may see your demo accounts (core.demo_accounts.read), and never inside a demo.

The page starts with the plain notice above, then:

• The count: for example "5 demo accounts, with no limit set. Each lasts 14 days." and New Demo Account.
• Each demo account, newest first, with its status:
  • Building: being made. Its row says which starting set it is built from.
  • Ready: finished, with its data fixed.
  • Shared: ready, with a share link on. The row says until when.
  • Ending Soon: ready, and it ends within 3 days.
  • Problem: it could not be made. Delete it and make another.
• Under each name: its starting set, its apps, when it ends, and who made it.
• Open: opens the demo in place (see Open Demo). Only a Ready demo opens.
• Share: opens Share Demo Link (see Share Demo Link). Only a Ready demo can be shared.
• Client Experience: while the demo is Building, change what its clients see (see The Client Experience Editor) and choose Update Experience. Once it is Ready, it shows the experience it was made with, to view only.
• Delete: type the demo's name to confirm, then Delete Demo (see Deleting a Demo Account). Until the name matches, the button stays off.
• Extend and Save as Template are shown, marked Coming Soon, and turned off.
• The Templates and Website Demo tabs are shown, marked Coming Soon, and do not open yet.
• How Demos Work: what a demo is, in plain words, including that email goes only to a test address, texts and calls are simulated, and payments run in test mode.
• Demo Account Settings, marked Coming Soon: Team Limit and Default Lifetime in Days are shown, turned off. Until they come, there is no limit and each demo lasts 14 days.

A demo an AI agent made shows the same way. The page does not show what the agent asked for, since only the demo itself is kept.

New Demo Account

New Demo Account opens one pop up with two steps, the same size on both.

Step 1, Details: the plain notice, then:

• Name (required): for your own list. Use a made-up name. A name you already use is refused: "You already have a demo named (name). Choose another name."
• Start From: the five industry starting sets, each with its made-up business and what it holds. Your Templates is shown, marked Coming Soon, and cannot be chosen yet.
• Apps in the Demo: the starting set's apps, all checked. Uncheck any you do not want. At least one is needed.
• What to Show (optional): see What to Show.

Next: Client Experience moves to step 2. Back returns to step 1 with everything kept.

Step 2, Client Experience: the editor below, for the apps you chose. Make Demo Account asks for the demo with its experience (core.demo.create), and the demo shows as Building in your list. Within seconds it is Ready.

The Client Experience Editor

Three tabs, each a list in the order the client sees it, with a live preview of /account as the client beside it (on phones, behind the Preview tab):

• Menu: Home is always first and cannot be moved, renamed, or hidden. For every other item: drag it by its handle, or use Up and Down, to change the order; type a new name; choose its group; or uncheck it to hide it.
• Home Cards: the cards on the client's Home. Change the order, or uncheck a card to leave it off.
• Notifications: the kinds of notification the client gets. Change the order, or uncheck a kind to leave it out.

The preview shows the menu by group, the Home cards, and the notification kinds as they will show.

Open Demo

Open Demo (the Open button on a demo's row) signs you in to one of your own demo accounts, the same way you switch to any company you belong to: the loading bar runs while it gets ready, then the demo opens in place, with no page load, and you look around as its made-up owner (see Industry Starting Sets), never under your own name or email. Nothing about you is stored in the demo. Your own Activity Log says you opened it.

Your name goes along only with that sign-in, for the "Opened by" line in the Demo label's note (see The Demo Label and the Demo Banner): the sign-in answer gives it as opened_by, and POST /account/demo/session answers { demo, opened_by } for the person signed in. A share link's visitor has no opened_by.

• Who can: owners and admins, and anyone whose role or permission group allows "See and open the demo accounts your company made" (core.demo_accounts.read). The action is core.demo.open.
• Only your own demo accounts open. Another provider's demo never opens from your workspace, even if its id is known.
• A demo that has ended does not open, and your time in a demo never lasts past its end.
• Open Demo and a share link are the only ways in. A demo cannot be signed in to from the usual sign-in page or opened from the company list.

AI agents and API keys cannot open a demo: opening one signs a person in.

Share Demo Link

Share Demo Link makes a link you can send to a prospect. Anyone who opens it looks around the demo as a made-up person, Sam Example (sam@example.com), and reaches nothing outside the demo: no company list, no other company, and nothing real. Changes they make are not saved.

• Who can: owners and admins, and anyone whose role or permission group allows "Share and delete demo accounts" (core.demo_accounts.manage). The action is core.demo.share.
• The link works for 7 days, or until the demo ends if that is sooner. The time it stops is shown when you make it.
• Only a finished demo can be shared. A demo still being built says so and makes no link.
• Making a new link stops the one before it, so only the newest link works.
• Everyone who opens the same link is the same made-up visitor.
• A walkthrough can start when the link opens. Name it with the walkthrough key when you share (lower case letters, numbers, dots, dashes, and underscores, up to 60 characters, for example first-invoice). The key is part of the signed link, so it cannot be changed by editing the address, and the workspace receives it as walkthrough when the visitor arrives. A link without one starts no walkthrough.

Share Demo Link on the Page

Share on a Ready demo's row opens Share Demo Link:

• Walkthrough to Start: None, or a walkthrough to start when the link opens. Walkthroughs are not available yet, so None is the only choice for now.
• Make Link makes the link and shows it once, with Copy Link. Your workspace keeps only when the link stops, never the link itself.
• Open as the Prospect opens the demo in place as the made-up visitor the link signs in, Sam Example, with the walkthrough you chose, so you see exactly what the prospect sees. It needs the link to be on. It uses POST /account/demo/prospect with { demo_id, walkthrough }: your own workspace checks that you may open demos and that the demo is yours and has not ended, the link is checked the same way as when it is opened, and the demo signs in the same made-up visitor. A demo with no link on says: "Make the demo link first. The prospect sees the demo through it."
• When a link is already on, the pop up says until when, and offers Make New Link (which stops the one before it), Open as the Prospect, and Turn Off Link.
• Turn Off Link stops the link at once (below).

Turn Off Link

Turn Off Link (core.demo.share_off, the same permission as sharing) stops the link at once. Anyone who opens it after sees that the link is turned off or has ended, and a visitor already inside the demo is signed out on their next click. You can share the demo again any time, which makes a new link.

AI agents and API keys cannot share a demo or turn its link off.

What a Prospect Sees

A prospect who opens a share link is signed in as Sam Example and sees your client's own account at /account, not your team's workspace:

• One made-up client. Each demo has one client: the company of its first made-up contact, chosen the same way every time and kept in the demo when it is built. The prospect sees that company and its people, and only the records that belong to them: their invoices and invoice lines, their requests and the replies on them, their projects and tasks, their meetings, their plans, their proposals, and their agreements. Never another company's.
• Kept on the server. The demo itself decides what the prospect may see, the same way it decides for anyone: every list, search, and record page answers with that client's records only, and opening another company's record is refused. The screen never hides records on its own.
• The client menu. Home, then the client's pages in the order of the demo's Client Experience, with its names: Your Company, Requests, Invoices, Plans, Projects, Meetings, Proposals, Agreements, Files, and Contact Us, one for each of the demo's apps. A page for something the client has none of (Plans, with no plan) is left out. There is no search, no All Apps and Services, no Recent, and none of the team's tools. Any other address opens the client's Home.
• Home has the Demo banner, then the client's cards (Needs You Today, Open Invoices, Your Requests, Upcoming Meetings, Active Projects, Proposals to Review, and Your Plans, in the Client Experience's order), and their notifications, all worked out from the client's own records.
• Never a draft. A client never sees a proposal that is still a Draft: their Proposals page, Proposals to Review, Needs You Today, and their notifications count and show only proposals that were sent (any status other than Draft). Proposals to Review counts those waiting for them (Sent or Viewed).
• Meetings are listed soonest first: the meetings still to come in date order, then earlier ones. Each shows its date and time, such as "Wed, Nov 11, 11:00 AM".
• Requests show when each was sent or, once the team replied, when it was replied to. A request's replies each show who wrote it, when, and what it says. Replies on Your Requests names only a request the team has replied to; in each starting set, the first request has the team's reply and is Waiting on Customer, and the others have only the client's message.
• Every page has its own address, such as /account/client/agreements, so a page opens straight from a link or after a reload.
• Client actions. New Request, View (a request with its replies; the team's internal notes never show), Pay (Test Mode), Review and Sign, Request a Change, Book a Meeting, Update Our Details, and Contact Us. In a demo, each says what would happen and that nothing is sent or saved.

The prospect's view comes from three read-only actions only a share link's visitor inside a demo can use: core.demo.client (the menu, Home's cards, and the notifications), core.demo.client.page (one page's records), and core.demo.client.request (one request with its replies). AI agents and API keys cannot use them.

A walkthrough named on the share link is handed to the workspace when the prospect arrives. It starts once Walkthroughs are part of the workspace (Planned).

Opening a Shared Link Planned

The address a share link opens is not available yet. Until it is, a link can be made and turned off, but opening it shows nothing.

Inside a Demo, Still to Come Planned

Extend, and the bell's pop up listing a demo's notifications in the Client Experience's order (it lists them newest first today), are planned.

Templates and Website Demos Planned

Saving a finished demo as a template, making demos from your templates, a team limit, your own default lifetime, and Try a Demo buttons for your website are planned.