ArtounisArtounis QR Code

Isolated QR development environment. Data and accounts are synthetic; real email and Push are disabled. Help Center

Back to home

Help Center

Get to know QR codes

Understand destinations, readability and the difference between static and dynamic QR codes before creating your first one.

19 topics found

What is the difference between static and dynamic?

A static QR stores data, such as a URL, in the image itself. Changing it usually requires a new image. A dynamic QR depends on an intermediate link that can redirect to another destination. That link must stay active and its domain must remain stable.

How can I improve scanning?

Keep sufficient contrast, a clear quiet zone and a suitable size. Before a large print run, test the actual output at its final size on several devices. Excessive shrinking or a large logo can prevent scanning.

What should I share?

Choose a clear, trusted destination and keep sensitive information out of a public QR. A printed QR can be copied by others. Check the displayed address before opening a scanned link.

Privacy and this preview

This environment collects no visitor analytics. Accounts are new, and access requires email verification and a valid server session. The account guide and mail-delivery status appear on this page.

Sign-in, recovery and account security

A new account needs email verification. Links last 10 minutes and work once. Five failed proofs lock the account until an authorized administrator unlocks it. Sessions expire after 10 minutes of inactivity; automatic requests do not extend them. With two-factor verification, a password alone is insufficient. Language, theme and time zone belong to your account. Email requires a configured delivery service, and there is no default account. An operator provisions the first Owner through an activation email; the user sets their own password. Provider acceptance does not prove Inbox delivery. A local link must open on a device that can reach the application. In this setup, email is enabled only for the approved Owner recipient; other addresses are not yet supported.

Sign in

User directory and search

In Users, enter a name, email or ID and press Search. Search covers all authorized records and only visible fields; without access to email, you cannot search other users by email. Results appear in pages of 25. Use Previous and Next; a new search starts on the first page. Pagination is not a database snapshot: data changes may appear on a later request. If your session or permissions change, restart the search from the first page. A search result link filters the directory to that record ID; it does not grant additional access. You can choose 5, 10, 25 or 50 rows per page; changing it restarts from the first page.

Create and edit roles

In Roles, create a role with a name and permitted grants, or open Edit for a custom role. Each role has a separate draft; closing its section does not clear it. Saving requires fresh security approval; cancelling approval stops the save. You can grant only your own permissions. Owner and Administrator are protected. A role change invalidates all existing sessions and security links or codes of its members; passwords and two-factor settings remain unchanged. Members sign in again to receive the new permissions. If you belong to the role, you are redirected to sign-in. Version conflicts and network errors preserve your form. Reload role and replace draft deliberately replaces the current input with the server version. The change is recorded in audit.

Themes and appearance

The floating Customize appearance button opens a drawer with 40 themes. Search by name, ID or color code. Selection and preview do not change the account until Save. Saving updates only the theme on your server profile; name, language and time zone remain unchanged, and a parallel profile draft is preserved. On a version conflict, deliberately load the saved theme and choose again. System stores the System preference and reacts to device light/dark changes. Another session receives the account theme after a fresh fetch or reload; other accounts remain independent. Closing keeps the draft within this session; sign-out or account changes clear it. Success and error colors retain their meaning; the drawer examples are previews only.

Factor enrollment and recovery

In Security, provide the current password and fresh approval, then register a passkey with device user verification. UV is checked by the server; raw biometrics are never sent. Successful passkey enrollment or TOTP confirmation rotates the session identifier and rejects old sessions. For TOTP, enter the displayed secret in your authenticator and prove its six-digit code; pending enrollment is not active. Valid passkey sign-in does not add OTP by default. Revocation takes effect on the server; removing the last key returns the preference to password. A long recovery code plus password replaces a second factor once, but cannot approve routine sensitive operations. A code alone grants only a restricted review flow. Existing sign-in paths remain until an approved gradual migration. After passkey enrollment, a password alone is insufficient. Save the eight new recovery codes securely when shown once; replacing the set revokes the previous one. Password plus recovery revokes prior sessions. A personal account can use its current password, select TOTP replacement after recovery, and prove the new factor. A privileged account has no administrative authority on this path and requires independent review. A localhost passkey cannot be used on the production domain.

600-second sessions and returning

All roles expire600 seconds after the last real interaction in that session, including background time. Closing Safari or backgrounding Home Screen does not itself sign out. Returning validates the session without renewing it. Phones show no timer; tablets and desktops show server remaining time in the header. Expiry requires sign-in. A long recovery code substitutes for the second factor only during password-based sign-in; it cannot approve a routine sensitive operation. While this tab is active, connection and session validity are checked again automatically. Save and delete operations are not repeated.

Notifications and devices guide

The bell shows only active unread notifications with event type and time. Read all empties its rows and count; history stays in the full center. Search event text or reference and use All, Unread, Archived or Deleted. All means neither archived nor deleted. Reading is distinct from opening; read-all does not change Never opened. Deleted has Never opened and Previously opened groups. Clear all confirms the count and account and includes archived items. Undo the batch or restore one; the source record is never deleted. Explicitly enable Push for this device; external copy is short and contains no secret or OTP. Clicking checks session and access first. Other-device reading syncs on the next return/connection; zero clears the badge. Explicit logout revokes this device binding and switching accounts hides the previous account. Session expiry alone does not withdraw Push consent; clicking may require sign-in again. Browser/OS support and Focus vary; real device tests are separate from queues and builds.

Mobile, Safari and Home Screen

On a phone in Safari, the header menu opens authorized destinations. An installed app at phone size uses only the bottom Home, Security, Sessions and More navigation. Home is the real account dashboard. More includes all permitted sections, Help and sign-out. Choose a destination, tap outside or press Escape to close. System back gestures are preserved and returning revalidates the session. The language icon lists فارسی, English, Deutsch and Français and saves only the account language on the server. After a409 conflict, reload and choose again. Save or explicitly reload profile drafts before changing language. Tickets are not enabled yet; notifications open the account center. Installation does not grant Push permission. Physical iPhone tests, visual review and deployment are separate.

Updates and preserving forms

On start and online return, the app checks the public deployed build identity without cache. The same build does not prove fresh data; the account and notifications revalidate separately. Automatic refresh waits during sign-in, recovery, Passkey, forms, dialogs, network requests and retained profile drafts. Save or explicitly reload the form, leave editing, then choose Get the update; automatic refresh is reconsidered on a safe return. Each build gets at most one automatic attempt in this tab. Network or browser storage failure preserves the current page and drafts; an explicit retry remains available. Updating does not sign out, clear caches or revoke Push. Installing A then B on a real iPhone requires separate device testing.

Choosing a new password

When setting, resetting or changing a password, values on the local common-password list are rejected. Existing length and format rules still apply. The server checks locally without sending the password elsewhere. If rejected, choose another phrase; the list is finite and acceptance alone does not guarantee security. Updating the list does not change existing passwords or prevent existing accounts from signing in. Rejecting a new password does not consume a valid link; choose another while the link remains valid.

Waiting and retrying

The halo appears while checking a session, loading a section or performing an action. Fast requests finish without flashing. No estimated percentage is shown. Connection failures preserve forms and drafts; retry the session check in the same place. Check the result before manually repeating a failed save or send. Reduced motion keeps the halo still.

Creating and managing QR

Choose a code type in My QR codes and enter its destination details. Configure colors, size, margin and logo; preview and PNG/PDF share the same renderer. Save keeps the data in your account; unsaved changes are marked. Editing or deleting a direct QR cannot change an existing print. Multi-link/business pages and dynamic mode are local previews until a final domain is selected. Trash is reversible with permission, from the library or deletion audit event. On a conflict, explicitly choose to load the server version. Wi-Fi images contain the network password: share them only with intended recipients. No scan analytics are recorded. View details is also available to read-only roles. Permission changes clear cached records and drafts, then reload authorized data from the server.

Hand over QR responsibility

In Users, open Manage user access and change roles or overrides. Review and save shows QR responsibilities without consuming security approval. Removing the last role or QR read access requires handing over all owned QR records, including Trash, in the same operation. Items are paginated. Search candidates by a visible name, email or ID. Only active, verified, unlocked users with a valid role and QR read/update/export/all-field rights are eligible; the replacement must differ from the departing user. Select a replacement and confirm the handoff, then complete fresh security verification for that exact request. A preview lasts five minutes; refresh it after data or form changes. Handoff and role changes are atomic. Creator, destination token, payload, appearance and trash history remain unchanged. Errors never leave a partial handoff; a consumed security approval cannot be reused after failure. Shared-role edits that would orphan records require individual handoff from Users first. This stage does not deactivate/delete the account or grant the replacement extra permissions.

Development administrator and local mail

This environment runs the full product with its own database and accounts; no previous data or credentials are migrated. Real email and Push are disabled. Only synthetic addresses ending in .test are accepted. An operator prepares a private administrator activation file. Its link expires after ten minutes and can be used once. The administrator personally sets a new password in the normal form; there is no default password. Never copy activation files or tokens into chat, reports or Git. Ask the operator to reissue an expired link. Registration, recovery and test codes go to this environment’s private mailbox, not a real Inbox. Neither the mailbox nor bootstrap is exposed through public HTTP. After signing in, the administrator can register a passkey for this domain; a localhost credential does not work on another domain. Backup and restore are separate from production.