Asset QR Codes
Asset QR Codes let you print a branded QR code for any asset so that anyone standing next to it can act in a single scan — either report a problem or log a security patrol visit — without hunting for the right place in the app. Each scan is tied to the exact asset, so issues land in the right list and patrol rounds are recorded automatically.
Every asset can produce two kinds of code. A Report an issue code opens a short form to describe a problem and attach photos, creating a task in the per-organization "Asset issues" project linked to that asset. A Security patrol code is zero-tap: scanning it simply records a patrol visit with a timestamp, building an audit trail of who checked the asset and when. Both codes carry your organization's logo and the asset's name, code, and location on the printed poster or label.
The Report an issue code has two visibility modes. An Internal code requires the scanner to be signed in to Flowtly, so the report is attributed to that employee. A Public code can be scanned and submitted by anyone with no login at all — useful for shared spaces, tenants, or visitors — with the option to leave a name and email. Public submissions are protected by invisible reCAPTCHA and rate limiting to keep out spam. Security patrol scans never require a login and are recorded immediately, with a short debounce so an accidental double-scan only logs one visit.
You manage codes from an asset's QR codes tab, where you can generate each code, switch a feedback code between Internal and Public, and preview the branded result. From there you can Print poster (a table-tent style sheet with a large code, asset name, code, location, and an action badge) or Print labels (a compact, brandable label for tagging many assets), then print or save to PDF straight from your browser.
Example use cases
- Public issue reporting: Stick a Public "Report an issue" code on a meeting-room projector or a lobby printer so any colleague, tenant, or visitor can flag a fault in seconds — no account needed — and the report lands in the Asset issues project linked to that exact asset.
- Attributed internal reports: Keep codes Internal where you want every report tied to a named employee, so accountability and follow-up are clear.
- Security patrol rounds: Place Security patrol codes along a guard's route; each scan logs a timestamped visit, producing a verifiable record that the round was completed.
- Photo evidence: Let reporters attach photos of the problem (camera-first on mobile), so maintenance sees the issue before they arrive.
- Bulk tagging: Use Print labels to tag a whole fleet of assets at once from a single A4 sheet, each label carrying its own scannable code and asset details.
How a scan works
- Each printed code points to a short link,
https://workspace.flowtly.eu/s/<organization>/<token>, that opens a full-screen, mobile-first scan page. - Report an issue (Public): the scanner sees the asset, fills in what's wrong (and optionally a name, email, and photos), and submits — creating a task with no login required.
- Report an issue (Internal): an anonymous scan shows a "please sign in to report" prompt; once signed in, the report is attributed to that employee.
- Security patrol: the visit is logged the moment the page opens, with a confirmation and timestamp; repeat scans within a minute are de-duplicated.
