Workflows Settings
Part of the MountDev Ops Workflows documentation. Updated November 5, 2026
MountDev Ops Workflows documentation | Updated November 5, 2026
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,744 automated checks before it ships, plus screen tests on 9 screen sizes for everything it changes.
Who Manages Workflows
Owners and admins add, change, turn on, run, and stop workflows, and they answer the cards a workflow waits for. Members have no access to Workflows. Change a person's access in Settings, Permissions.
Turning One On
A workflow you save is always off. It starts nothing by schedule or event until a person turns it on, and turning it off stops its schedule at once. Pressing Run starts one run whether the workflow is on or off, so you can try it first. A workflow saved by anything other than a person is saved off and stays off until a person turns it on.
Your Data
Everything Workflows keeps is in Export Everything: your workflows, what starts them, every run and its steps, and the cards. A step's result is kept as ids and counts only, and a failure is kept as a short plain reason with no key, token, or address in it.