Docs / LinkQR
Signup

Localization

Manage admin languages and translations.

Estimated reading: 2 minutes

Localization

The Localization section manages application languages and translation maintenance.

Menu items

  • Admin Languages: manage available languages and translation data.

Recommended use

  • Enable only languages that are reviewed and production-ready.
  • Scan for missing translation keys after adding modules.
  • Use translation tooling carefully for legal, billing, and support text.

Localization - Detailed Feature Guide

Feature Purpose

Manage admin languages and translations. This feature is part of the LinkQR workflow and should be documented as an operational tool, not just a menu item.

Main Capabilities

  • Provides a focused workspace for this product area.
  • Helps users complete the related task without switching modules.
  • Connects with plans, permissions, analytics, and workspace ownership where relevant.
  • Should be configured and tested before being included in customer workflows.

Typical Workflow

  1. Open the Localization page from the sidebar.
  2. Review the existing records, settings, or campaign state.
  3. Create or update the required item.
  4. Validate important fields before saving.
  5. Preview or test the public/user-facing result when applicable.
  6. Use analytics, logs, or reports to confirm the feature is working as expected.

Admin Configuration Notes

  • Confirm the feature is enabled in the correct plan.
  • Check workspace ownership when users work inside a team.
  • Review related limits such as credits, storage, QR count, scan count, or team members.
  • Clear cache and test again after changing global settings.

Customer-Facing Benefits

  • Reduces manual work and makes campaign setup faster.
  • Keeps campaign assets organized and easier to maintain.
  • Improves reliability by keeping important setup steps inside one workflow.
  • Supports better reporting and troubleshooting after launch.

Troubleshooting Checklist

  • If the feature is not visible, check plan permission and user role first.
  • If saved data does not appear publicly, verify publish/status settings.
  • If a public URL is involved, test the URL in a private browser session.
  • If team workspaces are involved, confirm the item belongs to the correct owner workspace.
  • If tracking or analytics is involved, confirm the visitor action uses the tracked dynamic URL.