The Save Bar
Part of the MountDev Ops Workspace documentation. Updated November 4, 2026
MountDev Ops Workspace documentation | Updated November 4, 2026
Every screen saves the same way. Nothing goes live until you press Save, and nothing you type is ever lost.
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 2,571 automated checks before it ships, plus screen tests on 9 screen sizes for everything it changes.
How It Works
As soon as you change anything on a screen, one bar fades in at the top of the page: Unsaved changes, with Discard and Save. When you have changed several things, it says how many, such as 3 changes, and each field you changed shows a Changed outline so you can find it. The bar is the same in every app and at every screen size, phones included, where it sits at the top too.
- Save shows the loader across the bar, then Saved, and the bar fades out.
- Discard puts back the values the screen had before you started, and the bar fades out.
- If a save fails, the bar stays and says why, with Retry. Nothing you typed is lost.
- Screens do not have a Save button of their own. Your Profile is the first screen to use the bar; the other screens move to it app by app.
Nothing You Type Is Lost
While a screen has unsaved changes, they are kept in your own account, a few seconds after each change. If the page reloads, your device crashes, or you open the same screen on another device signed in as you, the screen brings your changes back with the bar showing, and says where they came from (Brought back from your last visit or Brought back from your computer). Saving or discarding clears them. Anything kept for more than 30 days is removed, and you keep at most 50 screens' worth.
What is kept is yours alone. Other people, including owners and admins, never see it, AI agents and API keys cannot reach it, and it lives in your company's own database, in its own region. Passwords and files are never kept.
The actions behind this are core.unsaved.get (bring back what you had not saved on a screen), core.unsaved.put (keep it), and core.unsaved.clear (forget it once it is saved, sent, or discarded). They are only for a signed-in person, never for an AI agent.
Messages
A message you are writing, such as a reply or a note, is kept the same way. For a message the bar says Draft not sent and its button is Send instead of Save. Nothing is ever sent on its own.
Leaving with Unsaved Changes
If you move to another screen, switch to another company, or close the tab with unsaved changes, you are asked first: Stay, Discard, or Save. Stay keeps everything where it is. A new version of MountDev Ops is never picked up while something is unsaved.
