Skip to main content

​
What a scan can open in Mitti

Starting an inspection is the common case, but a Link can point at any of these. Pick by what the person holding the phone actually needs.
Mitti’s own access rules still apply, and that is the point. Issue reporting is open by design; everything else in that table asks for a Mitti login, and asset profiles and files also want the mobile app. A code on a machine gives nobody a way past that — a stranger who scans meets Mitti’s sign-in, because protecting those records is Mitti’s job and it is still doing it.So a tag for a mixed audience is a design decision, not a risk. Decide what the public should be offered, put that on a QRtub Page, and list the Mitti destinations alongside it. Your crew taps straight through; everyone else gets what you chose to publish. One tag, both audiences, and nothing exposed that was not already.

​
An existing inspection

Mobile: iauditor://audit/<inspection_id> Web: https://app.mitti.com/inspection/<inspection_id> Use it for: a long handover or commissioning form that gets finished over several visits. The tag on the unit reopens the same inspection instead of starting a new one.

​
One question, or one page, inside an inspection

Web: https://app.mitti.com/inspection/<inspection_id>?item=<item_id> Web: https://app.mitti.com/inspection/<inspection_id>?page=<page_number> Mobile: iauditor://audit/<audit_id>/item/<item_id> Use it for: one long inspection covering a whole plant room, with a tag on each item of equipment that opens its own question. Nobody scrolls, and nobody answers the wrong row.

​
The latest inspection report

Web: https://app.mitti.com/report/audit/<inspection_id> With a URL template:
Store the current inspection ID in each Item’s inspectionID field, and every tag resolves to its own item’s most recent report. Use it for: proving a check happened. A client or an auditor scans the plate and reads the last inspection without anyone fetching a file for them.

​
A training course

Web: https://app.mitti.com/training/learn/course/<course_id> Mobile: iauditor://training/learn/course/<course_id> Use it for: the induction or operating course for the machine the tag is on — reachable at the machine, at the moment somebody is about to use it, rather than in an email from six months ago.

​
An asset profile

Mobile: iauditor://asset/profile/<asset_id> Web: https://app.mitti.com/assets/<asset_id> Use it for: history and open actions. A fitter scanning a pump sees what has been done to it and what is outstanding.

​
A file or folder

Web: https://app.mitti.com/documents/document/<document_id> Use it for: the manual, SOP or safe-work method that has to be the current version. Mitti serves the latest one, so re-issuing the document never means re-producing the tag.

​
Issue reporting

Issue QR codes are made in Mitti under Issues → QR codes, and they are the one Mitti destination a stranger can use. They have no URL pattern to build — create the code, copy its link, and use that link as your Destination. Use it for: the fault-reporting button on anything the public or a visitor can reach — a council bin, a bollard, a lift lobby, a hire item on a customer site.
Because there is no URL pattern, an issue link cannot be built per Item with field bindings the way the others can. Every Item pointed at one issue code shares it, unless you create a separate code in Mitti for each site or asset. Issue codes can be pre-filled in Mitti with a category, site or asset when you create them.

​
Which ones bindings can build for you

This is the difference that decides how much work a fleet takes.
  • Templates, inspections, questions, reports, courses, assets and files all have a URL with an ID in it. So you write one URL template with a binding — {{item.assetID}} — and every Link in the Collection resolves to its own record. One rule, whole fleet.
  • Issue codes have no pattern. You paste a link, one at a time.