Create Accountor Login
Docs

MountDev Ops Forms

How MountDev Ops Forms works, page by page. Updated November 19, 2026

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

!The Forms page with each form and the recent submissions.

!The Forms page with each form and the recent submissions, on a phone in dark mode.

Every update passes all 8,865 automated checks before it ships, and every screen change is walked through before release.

Tested Every Release

All 110 of Forms's own automated checks run on every update.

What they cover: Forms and submissions | Records and fields | Spam and abuse protection | Partners and commissions

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 Settings.

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.
  • Forms on Your Websites: a form on a page you build in Websites, sent to your website's own address, with your Turnstile keys and partner codes, and the emails a visitor chooses to leave, kept as CRM leads.
  • Forms Inside Websites: a Forms group in a website's menu with Forms, Submissions, and Form Settings for that website.
  • Visible On: the card on each form that lists the pages of your websites that show it, each marked Live or Draft Only.
  • Partner Projects From a Form: taking a project a partner sends from your website, with the partner's code.
  • 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.
  • Permissions for Connections: every permission an app or an AI assistant can be given in this app, with its level.

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 on Forms' Settings page, the last item of its menu (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). It can also build forms, with these safeguards:

  • Make a form (forms.create): the form is saved off. It takes no submissions, has no public address, and sends no emails, until a person turns it on in Forms.
  • Change a form (forms.update): name, fields, button, thank-you message, and where submissions go. It never turns a form on or off. Turning on the automatic reply to the people who send the form, or telling everyone on the team about each submission, waits in Waiting for Your Approval for an owner or admin.
  • Change Forms Settings (forms.settings.update): the sender name saves at once. The sending address waits for an owner or admin. The Turnstile keys are never changed by an agent.
  • Delete a form (forms.delete): always waits for an owner or admin, like every delete. A form with submissions cannot be deleted.

Turning a form on or off stays with people. Every change an agent makes is in the Activity Log, marked as an AI agent.

Moving from Another System

A website contact form from another system becomes a form in your workspace. The submissions that system logged from the website come in with Settings, Import and its Export for MountDev Ops file (Importing) as Submissions of the Contact Us form, with their pages, referrers, first pages, and campaigns. Importing never deletes anything, here or in the old system, and running it again updates instead of copying.

Ask Us Anything

We’d love to hear from you!