Building Reports
Part of the MountDev Ops Reports documentation. Updated November 6, 2026
MountDev Ops Reports documentation | Updated November 6, 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 3,243 automated checks before it ships, plus screen tests on 9 screen sizes for everything it changes.
What a Report Is
A report is a list of blocks. Each block is one of these:
- Number. One figure: how many, the total, the average, the lowest, or the highest of a number or money field. It can show how that compares with the period before.
- Chart. A bar, line, or pie chart of a figure grouped by a field, or by day, week, month, or year.
- Table. Rows with up to eight columns you choose, in the order you choose, up to 500 rows.
- Text. Your own words.
- Image. A small picture you add (PNG, JPEG, or WebP, under 60 KB), such as a logo.
A report is saved as plain choices, never as code. Nothing a report holds can run, and anything it shows is always shown as text.
Where the Numbers Come From
Number, chart, and table blocks read the records of any app your company has, and the records of any module your company made itself, including modules your workflows fill. Each block can be narrowed with up to eight filters (is, is not, is more than, is less than, contains, is empty, or has a value) and by a date field. The report has one date range for everything: the last 7, 30, or 90 days, this or last month, this or last quarter, this or last year, or dates you pick. Dates are worked out in your company's time zone. You can compare with the period before or with the same days a year earlier.
A report shows only what the person running it may see. A block over an app you do not have, or over data you may not see, says so instead of showing anything, and the rest of the report still works.
For Your Team or for One Client
A Team report shows what the person running it can see. A Client report is for one client record, such as one company. Each block reads only the records linked to that client. A block over data that has no link to the client is left out of the report and says so. It is never shown unscoped.
Starting from a Template
Start From a Template makes a report in one step from a module you choose: Activity Summary, Breakdown, or Client Update. You can change everything afterward.
Running a Report
Run shows the report as a page. The page follows your device's light or dark setting. Each table has Download CSV, a spreadsheet file in which any cell that starts with =, +, -, or @ is made safe so a spreadsheet never runs it. Download PDF shows "Preparing..." until the file is ready, then downloads it. PDF is made with your workspace's engine token, so if your account has none yet it says "PDF is not on yet" and the page and spreadsheets work as usual.
Running a report leaves a row in its history (when, which dates, and who ran it). It does not keep the report's numbers.
Branding
A report uses your company name and logo from Settings, Company, and your brand color. When the Brand Kit is part of your account, reports follow it.
The Actions
- See the reports and the templates (action
core.reports.list) and open one (actioncore.reports.get). - See the data a report can be built on (action
core.reports.sources) and find a client to make a report for (actioncore.reports.clients). - Add a report or change one (action
core.reports.save), start one from a template (actioncore.reports.start), and remove one (actioncore.reports.remove). A removed report is kept as removed and its history stays. - Run a report (action
core.reports.run), download a table as a spreadsheet (actioncore.reports.csv), and make a PDF (actioncore.reports.pdf).
Removing a report and the PDF are a person's own. AI agents and API keys cannot use them. Running and downloading count as bulk reads, so someone whose group does not allow bulk reads of client records cannot run a report.
