Create Accountor Login
Docs

MountDev Ops Meetings

How MountDev Ops Meetings works, page by page. Updated October 14, 2026

MountDev Ops Meetings documentation | Updated October 14, 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.

Every update passes all 1,932 automated checks before it ships, plus screen tests on 9 screen sizes for everything it changes.

Tested Every Release

All 50 of Meetings's own automated checks run on every update, plus 27 screen tests whenever Meetings's screens change.

What they cover: AI agents and API keys | Roles and permissions | Records and fields | Projects and tasks

What Meetings Is

Meetings keeps every meeting with your clients and prospects in one place: when it was, who came, the agenda, your notes, what was decided, and who does what next. A meeting links to a CRM company, contact, and deal, and to a project once Projects is added. You can hold it by video right in the browser, with guests who need no account. Its recording and transcript sit on the meeting's own page, where you can watch the recording from any point and read the transcript beside it.

Recordings and transcripts are encrypted with your company's own key before they are stored, and every play and download is written in your Activity Log. After the meeting, you can send the attendees a summary, and nothing goes out until you have seen it and chosen who gets it.

Meetings comes with CRM, so adding Meetings adds CRM too.

In These Docs

Starting Modules

Like every module, each can be changed, given its own icon, turned off, or deleted on Meetings' Settings page, the last item of its menu (Modules and Fields), and members' access comes from their Meetings role, set in Settings, Permissions (Permissions).

  • Meetings: title, starts, ends, status (Scheduled, Held, or Canceled), company, contact, deal, where, agenda, notes, decisions, and summary.
  • Attendees: name, meeting, kind (Team member, Contact, or Guest), email, and contact.
  • Action Items: action item, meeting, who, due, status (Open or Done), and Projects task.

Who Sees What

Meetings uses the same roles as every app, given to each person in Settings, Permissions (Roles, Permissions):

  • No access (anyone without a Meetings role): Meetings is hidden for them, and every Meetings action refuses them.
  • Owners and admins see every meeting.
  • Manager: sees and changes every meeting.
  • Team member: sees and changes only the meetings they own (the ones they added, or that were given to them).
  • Viewer: sees every meeting, plays its recordings, and changes nothing.

Whoever may see a meeting may play its recordings and read its transcripts. Whoever may change it may upload, rename, and delete them. A meeting someone may not see does not show anywhere for them.

A role can also hide a field or make it read only, such as a meeting's Notes or an attendee's Email. A hidden field never shows for them in Meetings: not on the Schedule, a meeting's page, its attendees, or the summary they look at, and a search never finds a meeting by it. A read-only field shows and cannot be changed.

Contacts and projects are picked by typing: start typing a name and choose from up to 8 matches, only ones you may see.

For AI Agents

An AI agent you connect can read meetings (meetings.home, meetings.meeting.get), draft the agenda, notes, decisions, and summary (meetings.notes.save), add action items and mark them done, link a meeting to a project, and look at a summary email before a person sends it. It can never send a summary, add or remove attendees, delete a meeting, or open, play, download, or upload a recording or transcript. Everything an agent does is marked "AI agent" in the meeting's history and the Activity Log.

Ask Us Anything

We’d love to hear from you!