Getting started
A quick orientation to the Auditmark admin app at app.auditmark.io.
Auditmark is an inspection platform. As an inspection company, you build templates, schedule inspections for your team to complete in the field, and give your clients a branded portal to track the results.
This documentation has two parts. The guides explain how to run the platform from the admin app at app.auditmark.io. The developer reference covers the public API, authentication, and webhooks.
Signing in
You reach the admin app at app.auditmark.io with the credentials for your organization. What you can do once you are in depends on your role. Admins have full access, approvers see only the Approvals area, and inspectors are sent to the field app to complete their assigned work. The admin overview describes the areas each role can reach.
The three surfaces
Auditmark runs as three separate experiences on one platform. These guides cover the admin app; the other two are introduced here so you know how the pieces fit together.
| Surface | Who uses it | What it does |
|---|---|---|
| Admin | The inspection company | Build templates, schedule and track inspections, manage the team and client accounts, configure integrations, and review results. |
| Inspector | Field workers | A mobile-first app that completes assigned inspections on site, with photo, GPS, and signature capture and offline sync. Several inspectors can fill different sections of the same form at once. |
| Portal | End clients | A read-only, white-labeled view where a client tracks their own inspection results, findings, and corrective actions. Portal users are never charged. |
A client only ever sees their own organization's data, and the portal carries the inspection company's brand, never the Auditmark brand.
What you manage from the admin app
The admin app is where the inspection company runs everything. The sidebar groups the areas into Workspace, Records, Knowledge, People, and Admin.
| Area | What it covers |
|---|---|
| Dashboard and Ask AI | Charts over your inspection data, and plain-language questions about it. |
| Inspections | The work itself, from scheduled to completed, plus the approvals it needs. |
| Schedules | Recurring rules that create inspections automatically. |
| Clients and Locations | The end clients whose inspections you run and the sites where they happen. |
| Templates and Response sets | The forms inspectors complete and the reusable option lists behind them. |
| Documents and Notices | An internal file library and broadcast messages for your team. |
| Users | The people in your organization: roles, invites, and directory sync. |
| Marketplace | Connections to external systems such as Monday. |
| Report design | Themes and branding for generated reports. |
| Settings | Organization-level configuration, including roles and permissions, API keys, and webhooks. |
The admin overview is a full directory of every area and where it lives.
A note on terminology
The words you see depend on your shell, the configuration layer that adapts Auditmark to your industry. One shell calls a job an "inspection" and a customer a "client"; another calls them an "audit" and a "site". These guides use the default terms. Core, shell, and the three surfaces explains how the shell maps them to your own vocabulary.
Where to go next
New to the platform: read Core, shell, and the three surfaces.
Ready to set up: start with the admin overview.
Building an integration: see the developer docs.