Tools in dashboard: faster redirect and QR workflows for logged-in teams
How LinkShift tools are now available in the dashboard at /tools, so operations can validate redirects and generate QR assets without leaving workspace context.
Quick comparison
| Area | LinkShift | Public-only tool workflows |
|---|---|---|
| Entry point | Dashboard /tools hub with direct links from sidebar navigation | Separate public pages discovered manually or from bookmarks |
| Operational context | Runs inside authenticated workspace flow with nearby app resources | Outside core workspace navigation |
| Tool selection | Dedicated tools overview with practical use-case descriptions | Users decide from separate landing pages |
| Redirect diagnostics | Redirect Tester available at /tools/redirect-tester | Public tester only at /redirect-tester |
| QR operations | QR generator available at /tools/qr-code-generator | Public generator only at /qr-code-generator |
What changed in product navigation
LinkShift now includes a dedicated Tools section inside the authenticated dashboard.
After login, teams can open /tools and choose the QR Code Generator or Redirect Tester without switching to marketing-facing pages.
Why this matters for operations teams
During launches and migrations, teams often move between redirect setup, diagnostics, and campaign asset preparation.
Keeping these utilities inside dashboard navigation reduces context switching and shortens QA loops.
- One click from sidebar to tool selection
- Clear descriptions of when each tool should be used
- Practical instructions on tool pages instead of marketing copy
Public tool links still work
The existing public routes remain active: /qr-code-generator and /redirect-tester.
The dashboard version adds convenience for logged-in workflows, but does not remove public access paths used in docs, campaigns, or support materials.
Recommended usage pattern
Use /tools as the default entry point for internal operations, especially during migration windows and pre-release checks.
Share direct links to /tools/redirect-tester or /tools/qr-code-generator in runbooks so team members can jump into the right utility immediately.
When the competitor may be a better choice
- When your team intentionally prefers using only public utility pages without authenticated workspace navigation.
- When redirect and QR checks are ad hoc and not part of repeatable operational runbooks.
Sources
Want to test these scenarios on your own domain?
In LinkShift, you connect a domain and get HTTPS, hierarchical rules, and link maps for large-scale key mapping.