Good day.
Platform overview & user guide
New to CMOps? Start with the platform overview, then work through the full step-by-step guide — both open in a new tab and are kept up to date.
Pending company admin requests — approve to release a new company
| Type | Company | Status |
|---|
Organisations — provision a client and license their modules
| Name | Licensed modules | Active |
|---|
Create organisation
Add a company admin — the person who runs a company
They open the link, fill in their own details, and appear under Pending company admin requests above for you to approve. Nothing is granted until you approve them.
Creates the company admin now and emails a set-password link — no approval step. Use this when you already know who they are.
Analytics — activity by organisation, for review
| Organisation | Projects | Permits | Requests | Users | Active |
|---|
Data & backup — export a full copy of your CMOps data
Downloads every organisation, project, permit, request, H&S and facilities record plus settings as one JSON file you can keep safe. Read-only — it changes nothing.
Reset to clean slate removes every organisation, project, company and user (and all their data), leaving only your owner account — for clearing test data before going live. Back up first; there's no undo.
Users — everyone with an account; approve, assign or remove
| Name | Organisation | Status | Created | ||
|---|---|---|---|---|---|
| Loading… | |||||
Remove deletes the account and login permanently, and detaches them from every project.
Invoicing — track what each company has paid
Log a payment
Payments
Ownership handover — work through this before you hand a client their CMOps space
Data protection & security — subject rights, retention and the audit trail
Subject requests (DSAR)
Handle a person's right of access (export a copy of their data) or right to erasure (remove their personal contact data). Enter the email they were recorded under.
Retention schedule
How long each type of data is kept before personal fields are stripped or the record is purged. Running the sweep applies these windows immediately.
Audit trail — most recent 100 recorded actions
Enquiries — messages from the website "Get in touch" form and demo
Platform architecture — private to the owner
Feedback & bug reports — from everyone using the platform; action them and mark done
Send feedback
Tell us what would make CMOps better, or report something that's not working. It goes to the team, and you'll be told when it's actioned.
Dashboard
Site plan
Permit activity
Permit types
Needs your attention
Recent permits
| Permit | Type | Holder | Company | Status | Issued |
|---|---|---|---|---|---|
| Loading… | |||||
My work — everything assigned to you, across every module
Project chat — message everyone on this project
QR codes — posters to print and put up on site
Daily coordination —
Items on this plan
| Label | Layer | Type | Added by |
|---|
ⓘ How it works
Extend permit
Mark
Requests awaiting approval — from the public request links and internal entries
| Type | Name | Company | Details | Dates | |
|---|---|---|---|---|---|
| Loading… | |||||
User approvals — people requesting to join this project
| Requested | Give role | ||
|---|---|---|---|
| Loading… | |||
Health & Safety sign-off — reports closed out and awaiting your verification
Permit Register — every issued permit for this project
| Permit no. | Type | Name | Applicant email | Company | Registration / ref | Valid | Status | |
|---|---|---|---|---|---|---|---|---|
| Loading… | ||||||||
Permits by company
| Company | Active | Expiring ≤7d | Cancelled / Expired | Total |
|---|
Inductions by company
| Company | Pending | Completed | Total |
|---|
Induction settings
The link people are emailed to complete their induction (a video, quiz or external course), and how long a completed certificate stays valid.
Add person
Register someone for the induction. They go through the same flow — approve → link → certificate.
Raise a Health & Safety report
Assign to
An external person can't log in — the admin and delegates are notified to drive it to close-out.
Safety performance by company
| Company | Open | Overdue | Closed | Total |
|---|
Close job
Record what was done and, if you can, a photo of the result. This feedback is sent to the person who reported it.
New QR point
QR points
Facilities activity by point
| Point | Awaiting | Dispatched | Closed | Total |
|---|
Reports — daily activity by module, exportable to CSV or PDF
Assign a task
Tasks
| Task | Assigned to | Due | Status |
|---|
Notify team
Request form links — send these to drivers, visitors and companies
Overview — this project at a glance, and what still needs setting up
Responsibility matrix — who owns each type of work, who backs them up, who it escalates to
| Responsibility | Primary | Backup | Escalates to | Target (hrs) |
|---|---|---|---|---|
| Loading… | ||||
Each card has its own Send now — it saves and sends that one email immediately to its recipients (works even if the scheduled toggle is off), and reports back so you can verify it landed.
Times are UTC (server time) — e.g. 06:00 UTC ≈ 07:00 UK. Deliveries send as a PDF manifest; the others as a summary list.
Live Google Sheets export
Optional — send this project's records to a Google Sheet register in real time (rows update in place). Leave blank to disable. H&S and Induction export URLs are set on their own settings tabs; Permits and Facilities are set here.
Projects — every project in your organisation
| Code | Name | Location | Active |
|---|
Modules for — what this project uses; unticking removes it
Backup — download a full copy of this project's data
Exports everything in the selected project — settings, team, companies, zones, requests, permits, H&S, facilities, inductions and tasks — as a single JSON file you can keep off-platform. Run it before any big change. Photos/files aren't included (they stay in secure storage), but every record and its links are.
Danger zone — affects the selected project (—)
Reset settings clears logos, rules, modules and branding back to defaults — permits and records are kept. Delete removes the project and everything inside it. Both require a typed confirmation and cannot be undone.
Add a project
Site zones — draw a named area on the plan, or add one here; these are the location options everywhere
Drawing a named Area on the plan automatically creates a zone with its map location.
Team roster — who's on this project, and what they can do
| Name | Role on this project | ||
|---|---|---|---|
| Loading… | |||
Add a user — we email them a link to set a password and sign in
Invite via link — grab the signup links from the Share links tab and send them
Pending access requests
| Requested | Approve as |
|---|
User registry — everyone in your organisation
| Name | Role on this project |
|---|
Set role to save project access. Remove deletes the user from your organisation entirely.
User groups — teams used for facilities routing & email alerts
Create groups (Traffic Marshals, Logistics, Cleaning…) and add people by name + email — they don't need an account. Facilities QR points route to these groups, and Admin → Email & alerts sends to them.
Companies — people pick their company on the request form; its logo shows on permits
| Logo | Name | Contact | Cap |
|---|
Add a company
H&S delegates — internal people who receive every H&S report and own follow-up
External approver emails — people outside the app who should also be emailed on every H&S report
Auto-routing rules — when a new report matches, auto-assign a company and/or require sign-off before it can be completed
Due-date targets — auto-set the correction deadline by risk level (days from raise)
On-site QR capture — print & display so anyone can report a hazard without an account
Branding & documents — logos, permit document look, site address, zones and per-module setup
/ Client rep
your company logo
Approval workflows — build the approval chain for each permit type
How it works
A request for this module is submitted (with induction if required), then routes through your steps in order. Each step is an internal role (approver / security / admin) or a named external reviewer who approves via a secure one-time link — no account needed. When the final step approves, the permit is issued into the register. With no steps and no induction, permits auto-issue on submission.
Permit Builder — fields drive the request form and the permit
| Label | Type | Req'd | On form | On permit | Headline |
|---|
Until you save a permit type here, it uses the built‑in default fields. Name and Email are always kept (needed for the permit and the email). Headline is the big field shown on the permit.