Create Accountor Login
Docs

MountDev Ops Forms

How MountDev Ops Forms works, page by page. Updated October 7, 2026

MountDev Ops Forms documentation | Updated October 7, 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.

What Forms Is

Forms puts forms on your websites and keeps every submission. You build a form from the same field types as your modules, put it on any website with a small script or an iframe, and choose where each submission goes: it is always kept in Forms, and it can also become a lead in CRM, a ticket in Helpdesk, or both, while those apps are added. Your team hears about new submissions by email, and the person who sent the form can get an automatic reply.

Forms needs no other app. CRM and Helpdesk are used only when you add them in Setup.

In These Docs

  • Building Forms: the Forms page, adding and changing a form, its fields, the thank-you message, where submissions go, the auto-reply, spam protection, putting it on your website, and turning it off or deleting it.
  • Submissions: what is kept for each submission, its page, and CRM leads and Helpdesk tickets.
  • Forms Settings: the sending address, and your Cloudflare Turnstile keys for spam protection.

Starting Module

  • Submissions: name, form, email, phone, company, message, status (New, Reviewed, or Spam), every answer, the page it was sent from, the referrer, the first page the visitor saw, the five campaign (UTM) values, where it was sent, and the numbers of the form and of any CRM contact, CRM company, and Helpdesk ticket it became.

Submissions follow the same rules as every module: change its fields, turn it off, or delete it in Setup (Modules and Fields), and decide who sees them with roles (Roles). While Submissions is turned off, your forms take no submissions and say so to visitors.

Who Can Do What

  • See forms and submissions, and hear about new ones (permission forms.view): owners, admins, and members.
  • Build and change forms, their embed code, and Forms Settings (permission forms.manage): owners and admins.

For AI Agents

A connected AI agent can see your forms (forms.list, forms.get), a submission (forms.submission.get), and Forms Settings without the secret key (forms.settings.get). Building, changing, turning on or off, and deleting forms, and changing Forms Settings, stay with people: a form is a public page that can email the people who send it.

Moving from the Cascadia Hub

Cascadia's website contact form becomes the first form in Cascadia's own workspace. The submissions the hub logged from the website (the site forms log) come in with Bring In Cascadia's Data (Importing) as Submissions of the Contact Us form, with their pages, referrers, first pages, and campaigns. Importing never deletes anything, here or in the hub, and running it again updates instead of copying.

Ask Us Anything

We’d love to hear from you!