Create Accountor Login
Docs

Records

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

MountDev Ops Workspace documentation | Updated November 18, 2026

A record is one entry in a module: one contact, one ticket, one invoice. Everyone in your company can work with the records in modules that are on.

Where Records Are

Each module your company adds has its own page in the Workspace menu. It lists the records (Search in the left menu finds them, and each list keeps its filters), and Add opens a form with every field that is on. Select a record to open it: change any value and Save Changes, see its history below, or delete it.

Every record has a number, such as SUB-100 for a subscription or CO-12 for a company, shown first: in its own Number column on the list, at the top of the record's page, in search, and in exports. See Record Numbers.

The Record Header

Every record page starts with the same header, so the back link, the number, and the pills are in the same place on a ticket, a company, a deal, or any record in your own modules. From the top:

  • The back link (such as All Companies, or Inbox on a ticket) is on its own row, with even space below it. On a phone the whole row is a full-size touch target.
  • The name comes next, a step smaller than a page title. A long name wraps to at most three lines.
  • One row of pills, then the number. The status and any flags, such as Admins only, then the record's number (CO-12, for example). A record with nothing to show here has no row.
  • A muted line of key facts, such as a ticket's sender, email, and company, and labeled pairs on one line, such as Assigned to and Project. The pairs wrap onto more lines on a phone. A fact with no value is left out, not shown empty.
  • The buttons (Status, Edit, Close Ticket, Delete, and the rest, depending on the record) come after a clear gap. In CRM they stay at the top right beside the name.

Nothing about the header changes what a person may see or do: the same buttons are there for the same people.

Working with Records

  • List records (action core.records.list): in the order chosen for the list (see Sorting Lists below), with search across every value and the record number, and pages of up to 200. Give sort (number, created, updated, or a field's key) and dir (asc or desc) to ask for an order. Each record comes with its number, and the answer says how the list is sorted (sort, in words too) and every way it can be (sorts). It can also list only the records that link to one record through a link field, which is how a ticket's page shows its messages and an invoice's page shows its lines.
  • Open a record (action core.records.get): its values and the fields they belong to.
  • Add a record (action core.records.create): every required field needs a value.
  • Change a record (action core.records.update): change any values; leave the rest as they are. If someone else changed the record after you opened it, nothing is saved and you are asked to open it again, so no one's changes are lost.
  • Merge a copy into the record you keep: for CRM companies and contacts, owners and admins. A record merged into another is left out of lists and searches, and an old link to it opens the record kept. See Merging Duplicate Records.
  • Delete a record (action core.records.delete): blocked while another record links to it, and the message says where. Its files are deleted with it (Files on Records), so an AI agent cannot delete a record that holds files.
  • See a record's history (action core.records.history): every change, who made it, when, and the value before and after, newest first, including changes kept in your company's monthly history archives. A login field's change shows only as "Login changed".
  • See what ran against a record (action core.activity.list): every action, by anyone or anything, including ones that were refused or changed nothing, with filters and search. See Activity.
  • Show or copy a saved login password (action core.records.login.reveal): the password of one Login field on a record. See Login Fields below.
  • List what a link field can point to (action core.records.choices): the records a link field's list offers, by name, only those you may see. For a field that follows another field (see Pickers That Follow Another Field below), give the record chosen in that field (within) to get only the records linked to it, and all to get every record anyway. Give the record chosen now (value) to learn its name and whether it is linked to the one followed.

Sorting Lists

Every list starts in an order that makes sense: records with a name (companies, contacts, websites, products) by name, A to Z, and dated records (invoices, tickets, subscriptions, leads, and the like) newest first. The order is worked out across every page, with your search, so the first page really is the first.

  • Sort by a column: select a column heading. The first time sorts A to Z (numbers lowest first, dates oldest first; Date added and Last changed newest first); select it again for the other way. An arrow shows which way. The Number column sorts by the record number, SUB-99 before SUB-100.
  • On a phone: the headings are hidden, so use Sort above the list. It lists every way the list can be sorted, both ways, and Default order to go back.
  • Your choice is remembered for you, for that list, on every device you sign in on (action core.records.sort.save, with sort and dir; an empty sort goes back to the default). It changes only your own list.
  • The default for everyone: owners and admins set it in the module's own Settings, under Numbers and Order, Default Order (action core.records.sort.default; see the order and every choice with core.records.sort.get). Each person's own choice still wins for them. A choice of a field that is later turned off, deleted, or hidden from someone falls back to the default.
  • Records with an empty value go last, whichever way. Records with the same value keep a steady order, by number, so nothing moves between pages.
  • You never sort by a field you may not see.

Pickers That Follow Another Field

A link field's list can follow another link field on the same record. On a proposal, Contact and Deal follow Company: once a company is chosen, their lists show only that company's contacts and deals, so you pick the right one quickly.

  • With no company chosen, the list shows every contact or deal, as always.
  • With a company chosen, a line under the field says so, such as "Showing only contacts at Pandeux." Show All lists every contact, for the rare case like a contact at a parent company; Show Only Pandeux goes back.
  • When the company changes and the chosen contact or deal is not at the new company, it is kept, never cleared. A plain note under the field says so, such as "Ivan Lamkin isn't at Pandeux. Choose another or keep it." Choose another, or save and keep it.
  • Only the lists change. Saving any contact or deal works as before, from every screen, import, automation, API key, and AI agent, and no saved value is ever changed by it. The lists show only records you may see.

Built-in modules that follow their Company this way: proposals' Contact and Deal; CRM deals' Contact, and tasks' and activities' Contact and Deal; Helpdesk tickets' Contact; contracts' and signatures' Contact and Deal; Partners referrals' Contact; and projects' Website. Owners and admins see and change what a field follows in its module's fields, with Only records linked to (see Modules and Fields), for your own modules too.

Login Fields

A Login field keeps a sign-in for something outside your workspace, such as a staging site, a hosting control panel, or a vendor's portal, right on the record it belongs to. Owners and admins add one to any module from the module's fields (Settings, or the app's own Settings): Add Field, then choose the type Login.

Each login has a web address (optional), a user name, a password, and notes (optional).

  • The password is sealed. It is encrypted with your company's own key before it is saved, so your workspace's database never holds it in plain text. No other company's key can open it.
  • It is masked on the record page. The record shows the address, user name, and notes, with the password as dots. Show fades the password in for a moment and Copy puts it on your clipboard. Both are there only for owners, admins, and people who can change the record.
  • Every Show and Copy is logged. Each one is written in the Activity Log with the person's name and the record.
  • Sharing it with a client. Helpdesk can send a login in a reply with Share Staging Access, for the same people who can Show and Copy it, and each share is logged the same way (Sharing Staging Access).
  • Changing it. Type a new password to replace the saved one. Leave the password blank to keep the saved one while you change the address, user name, or notes. Clear the user name to remove the whole login.
  • Where the password never goes. Lists, record pages, exports, search, the record's history, webhooks, automations, and notification emails show the login without its password (with has_password true or false). Search never looks inside a login at all.
  • Automations and website forms do not fill in logins. An automation cannot change a Login field, and a Forms form cannot ask for one, because a password is sealed only when a person, an API key, or an AI agent saves it.

Logins Through the API and AI Agents

Reading a record (core.records.get, core.records.list, or GET records/<module>/<id>) returns each login as { "url", "username", "notes", "has_password" }, never the password. To get the password, ask for it on purpose with core.records.login.reveal (module_id, id, field, and purpose of show or copy). It works only for owners, admins, and people (or keys, or AI agents acting for a person) who can change that record, and every call is written in the Activity Log.

An API key with edit access can save a login, so your other systems can keep one up to date:

PATCH /api/v1/records/projects.tasks/42 { "values": { "c_staging_access": { "url": "https://staging.example.com/", "username": "preview", "password": "..." } } }

Leave password out to keep the saved one.

Values Are Always Checked

Every value is checked against its field every time, from every screen and every AI agent: text has a length limit (500 characters for short text, 50,000 for long text), numbers must be numbers, dates must be real dates, choices must be one of the field's choices, email addresses and web addresses must look right, a link must point to a record that exists (given as the record's id, such as 12, or with its app in front, such as crm:12), and a login needs a user name (up to 200 characters), an address that starts with https:// when it has one, and a password of up to 500 characters. Fields that are turned off cannot be set, and their saved values are kept untouched.

For AI Agents

AI agents you connect work with records exactly as the person who approved them can, with the same checks. Every change they make is in the record's history, marked as made by an AI agent.

Records Only Some People See

An app can keep some of its records for owners and admins only, such as Helpdesk's admin-only and spam tickets. Everyone else never sees them anywhere: not in lists, searches, records, or history.

Ask Us Anything

We’d love to hear from you!