Tags
Tags are short labels attached to inspection cases (for example damage type, workflow stage, or customer category). Users can filter the Gallery by tag and apply tags during upload or inline editing.
What you can do
- Create tags with a name and optional colour
- Link terminals so a tag is available only at selected locations
- Configure auto destinations — tags can trigger automatic sends to EDI destinations when applied
- Enable or disable tags without removing historical data
- Delete unused tags
When to use tags
- Standardise vocabulary across shifts and sites
- Drive automated EDI routing (combined with auto destination settings)
- Restrict visibility for guest users via tag-scoped access
Mobile app
Tags are stored per terminal as a comma-separated list in the tenant database. The mobile app does not edit this list — it loads options from the API.
| Step | Behaviour |
|---|---|
Device calls POST /api/v1/mobile/tags | Passes terminal code |
Response tags[] | Split from tenant tag definitions scoped to that terminal |
| User selects tags on device | Stored on each uploaded picture / case metadata |
| Auto destinations | Tags configured with auto-send still trigger server-side EDI after upload |
| EDI actions on device | Not configured on Tags page — see EDI; mobile loads actions[] from /tags based on terminal-scoped destinations |
Tags with WEB_ONLY or input-gated EDI destinations are unrelated to tag chips — they affect actions (see Notes and EDI).
Tips
- Keep tag names short and meaningful — they appear on case cards and in exports
- Prefer a controlled list managed here rather than free-text variations in remarks
- Review auto-destination links when you change EDI setup