Create Accountor Login
Docs

Modules and Fields

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

MountDev Ops Workspace documentation | Updated November 17, 2026

Every app keeps its information in modules: Contacts, Companies, and Deals in CRM, Tickets in Helpdesk, Invoices and Payments in Invoices, and any module your company adds. Each module has fields: the pieces of information every record in it holds. Every app starts with a ready-to-use set of modules and fields, and every one of them can be changed to fit how your company works.

One Set of Rules for Every Module

The same rules apply to every module in every app, whether it came with the app or your company added it:

  • Change it: rename it, add fields, rename and reorder fields, change choices, and make fields required or not.
  • Turn it off: it is hidden from everyone except owners and admins, and every record in it is kept. Turn it back on any time and everything is where you left it.
  • Delete it: it and every record in it are removed for good. Deleting needs an export of the module first and typing the module's name to confirm.

Turning off and deleting are blocked while anything depends on the module, such as a field in another module that links to it. The message names each one, so you know what to change first. Fields follow the same rules.

Only owners and admins change modules and fields (permission core.manage_setup). Everyone in your company can see the modules that are on (action core.modules.list).

Where You Change Modules

Owners and admins change an app's modules on that app's own Settings page, the last item of the app's menu (Apps). Modules your company added for itself are on Settings (the Settings gear at the bottom of the menu), in the Your Own Modules card, where Add Module adds one; it appears in the Workspace menu right away.

Both places list each module with its icon, its number of records and fields, and whether it is on or off, with buttons to see its fields, turn it off or on, export it, and delete it. Each module's Fields page lists its fields in order, with buttons to move each one up or down, change it, turn it off or on, and delete it. Add Field adds one. Its back link returns to the Settings page you came from.

Deleting opens a window that first offers the export (the file downloads to your computer) and then asks you to type the name. The delete button stays off until both are done.

Module Icons

Every module has an icon beside its name in the app's menu: Companies a building, Contacts a person, Deals a dollar sign, Tickets an inbox, and so on. A module your company adds starts with a list icon. To choose another, select the icon beside the module on the app's Settings page (or on Settings for your own modules) and pick one from the set shown. The new icon shows in the menu for everyone in your company right away. Choosing an icon never changes any record.

A List That Belongs to an App

A list your company adds can live in an app. A list in an app follows that app's roles: a Manager in the app manages it, a Team member works with it as they do with the app's own records, a Viewer only looks, and a person with No access in the app does not see it, find it in search, or open it. An owner can change what any role may do with the one list in Settings, Permissions. Owners and admins always see every list. Search, the event choices for automations and webhooks, record numbering, and Export Everything file the list under its app.

A list in no other app lives in the Lists app, and follows Lists' roles. When Lists was added, everyone who could see your lists kept the access they had; people added later start with No access until someone gives them a role. Anything an AI agent adds is still saved turned off.

Add a List

Owners and admins add a list in the app it belongs to. Every app that has modules shows Add a List as the last item of its menu, after its lists and before Settings, and as a button on the app's Settings page, in Fields and Lists. Both open the same window: Name of One, Name of Many, and a line saying which app it is added to and who can use it. The list starts with a Name field and opens on its own page. People without the right to change setup never see Add a List, in the menu or in Settings.

A list added in CRM is in CRM's menu and in no other app's menu. It follows CRM's roles, so a Viewer in CRM looks, a Team member adds and changes, and a person with No access in CRM does not see it. An owner changes any role's level for one list in Staff, Permissions.

Manage List

A list you added has Manage List on its page (owners and admins). It opens: Fields, Icon, Rename, Move, Turn Off, Export, and Delete, with the same rules every module has. Move opens a window with the app to move to and the names of the people who will stop seeing the list. Moving changes only where the list shows and which roles apply.

Add a Field to an App's Own Records

On an app's Settings page, in Fields and Lists, each module an app comes with has Add a Field beside Fields. A field you add shows in the record's details and in Edit, and is marked Added by you on the module's Fields page. An app update never removes it or changes its values.

Modules That Are Not in the Menu

Some modules only make sense inside a record of another module: the messages of a ticket, the lines of an invoice, the items of a subscription, and the messages of a chat. These modules are not in the app's menu. You see them on the page of the record they belong to: each ticket shows its messages, and an invoice or a subscription shows its lines or items in a card with an Add button. A record of such a module goes back to the record it belongs to.

A module whose records the app's own page already lists works the same way: Partners on the Partners page, Proposals on the Proposals page, conversations on the Chat page, and folders on the Files page. It is not a second item in the menu, so no two items in a menu share a name. If you cannot see the app's page, the module is in your menu instead. Settings marks it "Listed on the Partners page, not in the menu", for example.

Both kinds are still modules like any other: search finds them, import and export include them, and the app's Settings page lists them (marked "Shown on each ticket, not in the menu", for example) so you can change their fields, choose their icon, or turn them off.

Modules

  • Add a module (action core.modules.create): give it a name and a plural, like Vendor and Vendors. It starts with a Name field. Give an app (such as crm) to put the list in that app, so it follows that app's roles; leave it out for a list in no app.
  • See what moving a list would change (action core.modules.move_check): where the list is, where it would go, and the people who see it now and would stop seeing it. It changes nothing.
  • Move a list (action core.modules.move): put a list you added into an app, into another app, or back into no app. Only where it shows and which roles apply change. Its records, fields, numbers, links, and history stay exactly as they are, and each move is one line in the Activity Log. Owners and admins only, never AI agents. The modules an app comes with cannot be moved.
  • Rename a module (action core.modules.rename).
  • Choose a module's icon (action core.modules.icon): one of the icons in the module icon set. Anything else is refused.
  • Turn a module off (action core.modules.turn_off) and back on (action core.modules.turn_on).
  • Export a module (action core.modules.export): every record, with every field, including fields that are turned off. A login field is exported without its password. To export every module of every app at once, with their files, owners use Export Everything.
  • Delete a module (action core.modules.delete): needs your own export of it from the last day, made after its last change, and its plural name typed to confirm.

Fields

  • Add a field (action core.fields.create) of any of these types: short text, long text, number, money, date, date and time, yes or no, one choice, several choices, email address, phone number, web address, a link to a record in another module, or a login (an address, user name, sealed password, and notes; see Login Fields).
  • Date and time fields show and are typed in each person's own time zone, and are kept as one moment in time, so everyone sees the same moment in their own time. Saving a record without changing a date and time keeps it exactly as it was.
  • Change a field (action core.fields.change): its label, whether it is required, its choices, and its place in the order. Changing a field never changes the values already saved.
  • New choices from an update: when an app adds a choice to one of its own fields (such as Waiting on Us in Helpdesk's Status), your field gets it once, placed beside the choices it belongs with, and your Activity Log says what was added. Rename or remove it like any choice; an update never adds it again.
  • Only records linked to (a link field; within on core.fields.change or core.fields.create, or any_record to list every record): the field's list follows another link field of the module. A Contact field set to follow Company lists only the contacts at the company chosen, with Show All to look beyond it (Pickers That Follow Another Field). It can follow a field only when the records it lists link to the same kind of record (contacts have a Company field). The fields list shows it, such as "Only Contacts linked to its Company". Your choice is kept through every update.
  • Turn a field off (action core.fields.turn_off) and back on (action core.fields.turn_on). While a field is off, its values are kept but not shown.
  • Delete a field (action core.fields.delete): removes it and its value from every record, for good. Needs an export of the module and the field's label typed to confirm. A module always keeps at least one field.

Updates Never Change Your Setup

When an app is updated, it only adds what is new: a module or field it now comes with that your company does not have. An update never changes or removes anything your company set up, and never brings back a module or field your company deleted.

For AI Agents

AI agents you connect can see modules, add modules and fields, rename them, choose their icons, change fields, and turn things off. Anything an AI agent adds is saved turned off until a person in your company turns it on. AI agents never turn anything on, never export, and never delete modules or fields. Every change an AI agent makes is marked as made by an AI agent in the activity log.

Ask Us Anything

We’d love to hear from you!