Team Agreement

Your team agreement is the agreement everyone on your team accepts before they use your workspace, such as a confidentiality and client protection agreement. You write it; your team reads and accepts it in the workspace; and it is always there for them to read again. MountDev Ops never puts it on a public page.

Who Accepts It

Everyone with a workspace role (owners, admins, and members) accepts the newest version:

• on their first sign-in after you publish it, and
• again whenever you publish a new version.

Until they accept, nothing else in the workspace opens for them, and AI agents they connected wait too.

Accepting It

The agreement opens as a card in place of the workspace (action core.agreement.mine), the same way client sign-in asks clients to agree to terms. When your company also posts it on its website, the card links to that public copy; what you accept is always the version in the workspace. After a new version, the card says the agreement was updated.

1. Select the agreement's name, or the checkbox beside it. It opens in a reader laid out like a legal page on a website (see How It Reads).
2. Read it to the end. At the end, select I Have Read and Agree. That checks I agree to the agreement. Until then, the card says to read it to the end, and Continue stays off. Closing the reader early changes nothing.
3. Choose Continue (action core.agreement.accept).

Checking I agree and choosing Continue is your electronic signature. The workspace records the version, the time, the name on your account, your IP address, and your device, and writes it in the Activity Log.

If the reader cannot open on your device for any reason, the same agreement opens on the page in the card's place, with Back at the top and I Have Read and Agree at the end, and you continue the same way. The workspace notes what went wrong in the Activity Log so it can be fixed (action core.client.error): where it happened, the browser's name, and the error's message, never anything you typed, and at most five reports a person in ten minutes.

Reading It Again

Everyone can read the version they accepted at any time on Your Profile, My Agreements: Read Version opens it in the same reader, with Close at the end. Download PDF saves it with how it was accepted (action core.agreement.pdf); the button says Preparing while the PDF is made.

How It Reads

The reader looks the same everywhere: at sign-in, in My Agreements, and in Settings. On top are the agreement's title and a close button. Below it:

• The version line: the version, the day it was published, and, when the agreement's first line has parts with | between them (such as "Independent Contractor | Effective October 1, 2026"), that line too.
• On This Page: every main heading, each a link that jumps to its section in the reader. A heading that starts a part ("Part A: ...") is shown, but not listed.
• The sections, with their headings, paragraphs, and numbered and bulleted lists. A clause's lead-in ("2.1 What it is.") and a short label ("Company:", "Pay cycle.") are bold, as on a website's legal pages.
• Under a heading that names a signature block, each signer side by side in a table: the first line names the party, and the lines under it follow.

Esc, the close button, or selecting outside the reader closes it.

Writing and Publishing It

Owners and admins open Settings, Permissions, Team Agreement (action core.agreement.overview):

• Write and Publish, or Publish a New Version: a title, the agreement, an optional note on what changed, and, only if your company also posts the agreement on its website, the address of that Public Copy (action core.agreement.publish). Leave a blank line between paragraphs. Start a heading with # (## for a smaller one), a numbered list with 1., and a bulleted list with -. Two asterisks on each side of words make them bold. Preview opens your draft in the reader your team uses, before you publish. A published version never changes.
• Read Version: the current version in the reader.
• Who Accepted: everyone on the team, the version each accepted, when, the name recorded (the one on their account, or the name they typed before this step was a checkbox), their device, and their IP address, with each one's PDF.

MountDev Ops never adds agreement wording of its own: each company writes its own, ideally with its attorney.

Bringing It in from Another System

An agreement your company already uses comes in once, with its title, its text, and the address of its public copy if it has one (action core.agreement.import, in an import file's settings as team_agreement). It is published as version 1 by the workspace's owner, only while no version is published here, so importing again changes nothing and a version you published is never replaced. Everyone then accepts it as they would any version.

Private to Your Team

The agreement lives inside your workspace. MountDev Ops never puts it on your website, its legal pages, or any sitemap, and every workspace page tells search engines not to index it. If your company chooses to post a copy on its own website, that copy is yours to publish and keep up to date; the workspace only links to it.