Skip to main content
A tag installed somewhere public gets scanned by people you did not plan for. A resident, a delivery driver, a client’s site manager, someone who simply noticed it. The common failure is a permanent tag that opens one thing only your team can use. The tag is installed, expensive and idle: everyone else meets a sign-in screen and leaves, and nothing is captured from the one moment they were paying attention.

​
The shape

One Page, carrying every Destination either audience might want. Everyone who scans sees the same buttons and picks what they came for.
Your crew taps through to the tools they already use. Anyone else reads what you published and uses the reporting route.

​
The slots

Each row is a role in the pattern. Fill it with whatever you already run — the examples are not a closed list.

​
Nothing is exposed by putting the buttons side by side

The reflex is to worry that a public tag showing operational buttons leaks something. It does not. QRtub holds the address, never the data, so every Destination keeps its own permissions exactly as they are. Someone outside your organisation who taps the inspection button meets your tool’s sign-in, because protecting those records is that tool’s job and it is still doing it. Putting a code on something grants nobody anything they did not already have. So the decision is not about risk. It is about what you want to offer the people you did not plan for. See What Is a Destination?.

​
What it costs

One Page and one open form. No extra Links, no second tag, and nothing produced twice — a tag already in the field can be given the public route by editing its Page. The one thing worth deciding before you produce a Batch: whether the reference slot is readable by an outsider. A file set to your organisation only is fine as the team’s copy, but it should not be the only thing a public scan can reach.