Create Accountor Login
Docs

Sign-Up Agreements

Part of the MountDev Ops Workspace documentation. Updated November 15, 2026

MountDev Ops Workspace documentation | Updated November 15, 2026

Sign-Up Agreements is the list of agreements your company asks its clients to agree to when they sign up, such as your terms, your privacy policy, or anything else of your own. You write them, choose which are required, and keep a record of who agreed to which version and when. If you add none, your sign-up has no agreements step.

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 4,559 automated checks before it ships, and every screen change is walked through before release.

Where It Is

Open Settings, then Company. The Sign-Up Agreements card holds your list. Who Accepted opens from it. Owners and admins see it, and anyone whose role holds the permissions Change the agreements your clients agree to at sign-up and See who agreed to what at sign-up (Settings, Permissions). People you add can be given either one on its own.

Your List

Each agreement has:

  • a name, which is what people see next to the checkbox;
  • its text, written here (up to 50,000 characters), or a link to your own page that starts with https://;
  • Required or Optional: sign-up cannot finish until every Required agreement is checked, and Optional ones can stay empty;
  • a version.

You can have up to 10 active agreements. Add Agreement adds one, Edit changes it, Preview shows it the way a client reads it, and the arrows Move Up and Move Down set the order clients see (action core.signup_agreements.save, action core.signup_agreements.reorder, and action core.signup_agreements.overview to read the list with the retired ones). MountDev Ops ships no agreement text of its own, and a new company's list starts empty.

Versions

Changing an agreement's name, text, or link publishes a new version. Earlier versions are kept exactly as they were, so the record always shows the words a person agreed to. Changing Required or Optional, or the order, is a setting and makes no new version.

When you publish, Ask People to Accept Again at Their Next Sign-In is off at first. Turn it on and each person who signed up earlier and has not accepted that version sees one card at their next sign-in, with only what they owe. An Optional agreement is asked again only when you turn it on, and it never stops anyone from signing in. When you add an agreement, the same switch asks people who already signed up.

Retiring

Retire takes an agreement out of sign-up and out of asking again (action core.signup_agreements.retire). Its versions and every acceptance stay, and nothing is deleted. Open Retired and choose Bring Back to use it again (action core.signup_agreements.restore).

What a Client Sees

At sign-up, one more step shows your agreements. Each is a checkbox with a Read link that opens it in a large reader (a link agreement opens your own page in a new tab). The page says that the time, the address, and the browser are kept with what they agreed to. Create Account stays off until every Required agreement is checked. If your list is empty, there is no step.

Right after a new client's account is made, the same card asks for every agreement they have not answered yet, Required and Optional. At sign-in, a person who owes a newer version sees one card asking them to accept it. They cannot go on until they accept what is required. They can sign out, and nothing is deleted.

Always There

Two things are never in your list and cannot be removed or edited here: the payment authorization shown when a card or bank account is saved, and the text message consent. Both name your company. The Always There part of the card shows them read only.

Who Accepted

Who Accepted lists each acceptance with the person, the agreement, the version, and the time, newest first (action core.signup_agreements.accepted). Search needs at least 2 letters, and you can filter by agreement. Each row also keeps the address and browser it came from. Waiting shows how many people have not yet accepted a version you asked them to accept again. Download Export saves the list as a spreadsheet (action core.signup_agreements.export). Every look and download is in the Activity Log.

What a Client Keeps

A client reads what they agreed to on Your Profile, My Agreements, with Read Version for the exact words (action core.signup_agreements.mine). It is a copy kept in their own account, so your account and theirs never read each other. Only they see it.

Who Can See It

Your list and its record are in your own workspace and region. No other company, no MountDev staff, and no tool outside your account can read who agreed. The sign-up page asks your workspace for your list only on the connection your own account turned on by publishing its first agreement, and it keeps nothing.

AI Agents

An AI agent you connect may read the list, with the tool signup_agreements_list: the names, the text or link, Required or Optional, and the versions (action core.signup_agreements.list). It can never change the list, record an acceptance, or see who agreed.

Ask Us Anything

We’d love to hear from you!