> ## Documentation Index > Fetch the complete documentation index at: https://help.qrtub.com/llms.txt > Use this file to discover all available pages before exploring further. # Mitti (formerly SafetyCulture / iAuditor) > Point a Link at any Mitti destination — an inspection, a report, a course, an asset, a file, or issue reporting for people with no Mitti account. Mitti was called SafetyCulture, and iAuditor before that. Point a QRtub Link at a Mitti destination and a scan lands straight on the right record — the inspection for this machine, its last report, its asset history, or a form a visitor can use without a Mitti account. ## If you know it as SafetyCulture or iAuditor Same product, three names. It launched as **iAuditor**, was renamed **SafetyCulture**, and became **Mitti** in August 2026. SafetyCulture remains the company; Mitti is the platform. Nothing you have already set up stops working: * The mobile app kept its identifiers, so the **`iauditor://` deep link scheme still works**. You will see it throughout this page, and it is correct — not a leftover. * **`app.safetyculture.com` URLs still resolve.** Examples below use `app.mitti.com`, but you do not need to go back and change anything. ## Overview Mitti (formerly SafetyCulture) is a workplace operations platform. Used with QRtub, you can: * Open a specific inspection template by scanning the equipment it belongs to * Carry each Item's own data into the link, which Mitti uses to pre-fill answers * Offer several Mitti destinations on one code, so whoever scans picks what they came for * Reach destinations Mitti has a URL for but does not make a QR code for — a training course, a report, or one question inside a long inspection * Change which record a code opens without producing the tag again, including if you switch platforms later ## Integration Method QRtub connects to Mitti using **deep links** — URLs that open Mitti directly at a specific inspection, template or report. No data is exchanged between the two systems; QRtub builds the URL and Mitti handles the rest. Mitti supports two deep link formats: * **Mobile app** (`iauditor://`) — opens the Mitti app. The scheme still carries the old name * **Web app** (`https://app.mitti.com/`) — opens in a browser. `app.mitti.com` also works ## Getting Your Template ID Before setting up deep links, you'll need your Mitti Template ID: 1. Open the Mitti web app 2. Navigate to your inspection template 3. Copy the Template ID from the URL 4. Example: `template_fcbc86fd41a74180921347e4be53bdf2` See [Mitti's guide on getting entity IDs](https://help.mitti.com/en-US/000076/) for detailed instructions. ## Basic Setup: Start Inspection ### Mobile App Deep Link In your Item's Page, add a new Destination: **Destination Name:** Start Inspection **Destination URL:** `iauditor://template/new_audit/` **Example:** ``` iauditor://template/new_audit/template_fcbc86fd41a74180921347e4be53bdf2 ``` ### Web App Deep Link Alternatively, use a web app deep link for users who prefer desktop/browser access: **Destination Name:** Start Inspection (Web) **Destination URL:** `https://app.mitti.com/inspection/new?templateId=` **Example:** ``` https://app.mitti.com/inspection/new?templateId=template_fcbc86fd41a74180921347e4be53bdf2 ``` ### Using QRtub URL Templates Use QRtub's URL Template feature to automatically insert template IDs from your Item data: **Destination URL:** `iauditor://template/new_audit/{{item.templateID}}` **Why this matters for bulk deployment:** Configure the Destination once with a template placeholder. Each Item in your Collection can have a different `templateID` field value—some use the forklift inspection template, others use the excavator template. One Destination configuration serves all equipment types, with each QR code routing to its specific inspection template automatically. This allows different Items to use different Mitti templates based on their Item data—no manual configuration per Item. ## Advanced: Pre-Fill Inspection Questions Mitti allows you to pre-fill specific inspection questions using question item IDs. ### Mobile App Pre-Fill Format ``` iauditor://template/new_audit/?= ``` **Example with QRtub URL Templates:** ``` iauditor://template/new_audit/template_fcbc86fd41a74180921347e4be53bdf2?8f2f287e-be6e-470c-a2e2-a0fd8ab966ae={{item.assetID}} ``` Where: * `template_fcbc86fd41a74180921347e4be53bdf2` is your Mitti template ID * `8f2f287e-be6e-470c-a2e2-a0fd8ab966ae` is the question item ID in your template * `{{item.assetID}}` is the QRtub field binding — replaced with that Item's own asset ID before the link opens **Bulk deployment benefit:** Configure this URL once. Deploy to 500 pieces of equipment. Each scan substitutes that Item's own asset ID into the link, and Mitti reads the parameter and pre-fills the matching question. No manual setup per Item. ### Pre-Fill Multiple Questions Use `&` to pre-fill multiple questions: ``` iauditor://template/new_audit/?=&= ``` **Example:** ``` iauditor://template/new_audit/template_fcbc86fd41a74180921347e4be53bdf2?8f2f287e={{item.assetID}}&a2e2a0fd={{item.location}} ``` **Important notes:** * You need the specific **question item ID** from your Mitti template (not arbitrary parameter names) * To get question item IDs, see [Mitti's entity ID guide](https://help.mitti.com/en-US/000076/) * QRtub inserts field values exactly as stored and never URL-encodes them. A value containing a space, `&` or `#` will break the deep link — store it pre-encoded in the Item field * Very long deep links may not work consistently ## App Not Installed? Set a Fallback URL `iauditor://` deep links only work if Mitti is installed on the device. If someone scans and doesn't have the app, the link does nothing. QRtub handles this automatically. When you enter an `iauditor://` URL as a Destination, an amber notice appears in the editor prompting you to configure a fallback. **Recommended setup:** | Field | Value | | -------------------------- | --------------------------------------------------------------------- | | App link (Destination URL) | `iauditor://template/new_audit/{{item.templateID}}` | | Fallback URL | `https://app.mitti.com/inspection/new?templateId={{item.templateID}}` | **What happens at scan time:** * Mitti installed → app opens directly to the inspection template * Mitti not installed → after 2.5 seconds, QRtub redirects to the web version The Fallback URL supports `{{item.field}}` bindings, so you configure it once and it adapts to each Item automatically — just like the app link itself. You can also set a **Fallback Message** instead of a URL if there's no web equivalent (e.g. "Please install Mitti to access this inspection template"). See [App Links & Fallback URLs](/destinations/app-links) for full details on how fallbacks work. ## 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. | What it opens | A concrete use | Who can open it | | ------------------------------------- | ---------------------------------------------------------------------------- | --------------------------------------- | | **A new inspection** | The pre-start checklist for this excavator | Mitti user, template access, app | | **A new inspection, pre-filled** | Serial, site and asset number already answered before the operator starts | Mitti user, template access, app | | **An existing inspection** | Resume the half-finished handover form on the crane | Mitti user | | **One question inside an inspection** | The plate on the switchboard opens its own question, not page 1 of 90 | Mitti user | | **The latest report** | A hire client scans the plate and reads the last check before signing for it | Mitti user, report access | | **A training course** | The plate on the boom lift opens its operating course before anyone gets in | Mitti user | | **An asset profile** | Service history and open actions for this pump | Mitti user, **mobile app** | | **A file or folder** | The current SOP for this machine, always the latest version | Mitti user, file access, **mobile app** | | **Issue reporting** | A visitor or a delivery driver reports a damaged bollard | **Anyone — no account** | **Only issue reporting works for someone without a Mitti account.** Everything else in that table needs a Mitti login, and asset profiles and files also need the mobile app installed. This matters most when you are producing a tag for a mixed audience. A plate in a public place, on a hire item, or anywhere a contractor or visitor might scan it should not have a Mitti document as its only Destination — they will reach a wall. Put the public-facing version on a QRtub [Page](/pages/pages-overview) and keep the controlled copy in Mitti. One tag, both audiences. ### An existing inspection **Mobile:** `iauditor://audit/` **Web:** `https://app.mitti.com/inspection/` **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/?item=` **Web:** `https://app.mitti.com/inspection/?page=` **Mobile:** `iauditor://audit//item/` **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/` **With a URL template:** ``` https://app.mitti.com/report/audit/{{item.inspectionID}} ``` 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/` **Mobile:** `iauditor://training/learn/course/` **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/` **Web:** `https://app.mitti.com/assets/` **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/` **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](/destinations/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. ## Troubleshooting **Mobile app doesn't open:** * Ensure Mitti app is installed on the device * Verify Template ID format is correct * Check that the user has access to the template in Mitti **Web link doesn't work:** * Verify user is logged into Mitti web app * Check that the user has permission to access the entity (template, inspection, asset) * Confirm the entity ID is correct **Data not pre-filling:** * You need the specific **question item ID** from your Mitti template (not arbitrary field names) * Ensure Item fields in QRtub contain data * Test that URL encoding is correct for special characters * Verify deep link isn't too long (keep it under \~2000 characters) **Users need access:** Deep links only work if users have permission to access the relevant entities in Mitti. Ensure your team has appropriate access before deploying. ## Resources * [Mitti deep link documentation](https://help.mitti.com/en-US/000149/) * [Get Mitti entity IDs](https://help.mitti.com/en-US/000076/) * [Create issue QR codes](https://help.mitti.com/000165) — the one Mitti destination that needs no account * [Create asset profile QR codes](https://help.mitti.com/002882) * [Create QR codes for files and folders](https://help.mitti.com/005378) — note the access requirements * [Share inspection QR codes](https://help.mitti.com/002257) * [App Links & Fallback URLs](/destinations/app-links) * [Pages Overview](/pages/pages-overview) * [Key Concepts](/key-concepts) *** **Ready to get started with QRtub?** [See plans and pricing →](https://qrtub.com/pricing) Questions? Email us at [hi@qrtub.com](mailto:hi@qrtub.com)