Early-access service

Managed QR codes for campaigns that keep changing.

Create QR codes once, update destinations later, group codes by campaign, and review scan activity without running your own redirect stack or static links file.

Ask about QR early access View planned plans Developer platform

Availability Early access

QR Codes is the first hosted LinkRidge Cloud service moving toward customer trials.

Best for Small teams

Product launches, menus, events, print collateral, and simple campaign tracking.

Setup Reviewed

New workspaces are approved before external redirects, imports, or customer access are enabled.

What it does

One place to manage QR destinations, campaigns, and scan history.

Create branded QR codes that can point to new destinations later.
Group codes by campaign, location, or customer-facing project.
Review basic scan activity before deciding what to optimize.
Import existing Open QR links after a human review pass.

Starter

For one small QR workspace

A lightweight plan for launch pages, print tests, and simple campaigns that need editable destinations and a modest scan history.

Growth

For teams with more campaigns

More active codes, longer scan retention, branded exports, and import review for teams moving from an existing QR link library.

Developer path

API and Terraform later

The same account and service model is being prepared for API-driven setup and Terraform management after the hosted service gates are ready.

Next step

Ask for early access

Share the QR workflow you want to move, the number of codes, and whether you have an existing Open QR export to review.

Implementation boundary

Internal service contracts stay documented for builders.

Account, user, membership, invite, billing, and entitlement records live in LinkRidge Cloud.
QR code domain records, redirects, scan events, and campaign grouping live in the QR service.
The seed Open QR app remains separately deployable; platform work should add adapters and contracts instead of copying the full app into this repo.

Workspace record

qr_workspaces

Planned service-owned workspace record created only after an account service is enabled by the platform.

id: Stable workspace identifier used by QR records, redirects, exports, and scan events.
account_id: Platform account boundary; must match the enabled account service before data is loaded.
account_service_id: Platform enablement record that proves the QR service is modeled, requested, enabled, or paused for the account.
service_id: Always qr-codes so shared platform jobs can route usage and audit events.
plan_key: Local plan selection such as starter or growth; billing-provider products and prices are not implied.
status: Workspace status derived from account service state; paused workspaces cannot redirect or mutate records.
created_by_user_id: Platform user or approved operator that caused the workspace to be provisioned.
created_at: Audit-friendly creation timestamp.
updated_at: Last workspace settings or status change timestamp.

Workspace provisioning evidence

service_workspace.id is stable and referenced by audit_event.metadata.service_workspace_id.
service_workspace.account_id, account_service_id, service_id, and plan_key match the packet account and selected QR plan.
service_workspace.created_by_user_id resolves to the local primary owner placeholder.
service_workspace.created_at and updated_at remain null while the workspace is planned and no database write has happened.
operator_review.decision_state is mirrored into audit_event.metadata.decision_state.

Redirect resolution

Planned replacement for static links.json redirects once the hosted service shell exists.

account_status: allow active; block account_not_active. Draft, pending approval, or suspended accounts cannot serve hosted QR redirects.
account_service_status: allow enabled; block account_service_not_enabled. Modeled, requested, or paused service records cannot load redirect destinations.
workspace_status: allow enabled; block workspace_not_enabled. Planned or paused QR workspaces cannot serve customer traffic.
qr_code_status: allow active; block qr_code_not_active. Planned, archived, or paused QR codes fail closed before destination URLs are used.
entitlement_checked: allow true; block entitlement_not_checked. Redirects cannot record scans or serve branded behavior until local entitlements are read.
external_redirect_approval: allow approved; block external_redirects_not_approved. Externally reachable redirects remain closed until Matthew approves hosted QR access.

Normalize the scanned slug and resolve it to exactly one qr_workspace_id plus qr_code_id.
Load the workspace through account_id and account_service_id before reading the destination URL.
Verify account, account service, workspace, and QR code status are enabled before redirecting.
Check local entitlements for monthly_scans and custom_domain before recording billable usage or branded host behavior.
Write qr_code.scan_recorded and qr_code.destination_changed audit or usage events with actor, account, service, workspace, and target context.
Return a safe not-found or paused response when the slug is missing, ambiguous, over limit, or outside entitlement.

Fixture evidence

Every planned route resolution carries account_id, account_service_id, qr_workspace_id, qr_code_id, and service_id from the seed packet records.
slug matches one planned QR code in the same workspace before any destination URL is read.
resolved_destination_url matches the planned QR code destination while redirect_performed remains false.
account_status, account_service_status, workspace_status, and qr_code_status mirror the local fixture state so disabled or planned records fail closed.
routeResolution.testVectors cover each denial matrix gate so the future adapter can replay account, service, workspace, QR code, entitlement, and external-approval failures before any destination URL is served.
entitlement_checked remains false and blocked_reason remains external_redirects_not_approved until hosted redirects receive explicit Matthew approval.

Policy test vectors

draft account blocks redirect: account_status=draft; blocked as account_not_active
modeled service blocks redirect: account_service_status=modeled; blocked as account_service_not_enabled
planned workspace blocks redirect: workspace_status=planned; blocked as workspace_not_enabled
planned QR code blocks redirect: qr_code_status=planned; blocked as qr_code_not_active
unchecked entitlement blocks redirect: entitlement_checked=false; blocked as entitlement_not_checked
missing Matthew approval blocks redirect: external_redirect_approval=not_approved; blocked as external_redirects_not_approved

Blocked until

Local database schema exists for accounts, account_services, service_entitlements, audit_events, and qr_workspaces.
Workspace creation runs only behind admin-only operator tooling.
Externally reachable redirects, customer login, invites, DNS, and billing writes receive explicit Matthew approval.
Platform account resolution exists.
QR workspace records exist.
Service entitlements can be read locally.
Operator approval allows externally reachable hosted redirects.

fixture-checked

qr_codes

Planned service-owned QR code record that replaces one links.json slug only after workspace, account service, entitlement, and operator checks exist.

id: Stable QR code identifier used by edit, archive, export, redirect, usage, and audit events.
account_id: Platform account boundary copied from the resolved workspace.
qr_workspace_id: Service workspace that owns the QR code and resolves to one account service.
campaign_id: Optional planned campaign that groups related QR codes inside the same workspace.
slug: Unique redirect slug inside the workspace; global uniqueness is not assumed.
destination_url: Redirect destination that can be changed without changing the printed QR code.
label: Operator/customer label used for dashboard search and export history.
status: Planned, active, archived, or paused state checked before redirecting.
style: QR render style copied from the Open QR seed app options.
created_by_user_id: Platform user or approved operator who prepared or created the QR code.
created_at: Audit-friendly creation timestamp.
updated_at: Last destination, status, style, or label change timestamp.

Fixture evidence

Every planned QR code carries account_id and qr_workspace_id that match the seed packet workspace.
campaign_id is null or resolves to one planned campaign inside the same workspace.
slug values are unique within the planned workspace.
destination_url is present but external redirect serving remains skipped.
style remains one of the seed app render styles: squares, dots, or round.
created_at and updated_at remain null while records are only fixture evidence.

Blocked until

Local QR CRUD schema exists behind admin-only tooling.
Route resolution reads qr_codes through qr_workspace_id and entitlement checks.
Externally reachable redirects receive explicit Matthew approval.

fixture-checked

qr_scan_events

Planned service-owned scan event evidence that maps one future redirect hit to the shared platform usage event envelope without enabling redirects or billing export.

id: Stable scan event identifier used for fixture checks and future usage-event joins.
account_id: Platform account boundary copied from the resolved workspace and QR code.
account_service_id: Platform service enablement record associated with the scan.
qr_workspace_id: Service workspace that owns the scanned QR code.
qr_code_id: QR code record that resolved the scanned slug.
service_id: Always qr-codes so shared platform jobs can route the usage event.
event_name: Always qr_code.scan_recorded for scan usage evidence.
quantity: Scan quantity that can later feed usage limits after entitlement checks exist.
billable: False while billing export and hosted redirects are not approved.
occurred_at: Null while this is only fixture evidence and no redirect has happened.
metadata: Slug, campaign, referrer, user-agent, coarse geo, entitlement-check, and billing-export context for the usage event.

Fixture evidence

Every planned scan event carries account_id, account_service_id, qr_workspace_id, qr_code_id, and service_id from the seed packet records.
event_name stays qr_code.scan_recorded and quantity stays one for fixture evidence.
billable is false and billing_export_status is not_enabled while billing integration is approval-gated.
occurred_at remains null because no hosted redirect or database write has happened.
metadata.slug matches one planned QR code slug inside the same workspace.
metadata.campaign_id matches the QR code campaign_id when a planned campaign is present.

Blocked until

Hosted redirect code can resolve account, account service, workspace, QR code, entitlement, and route status.
Local usage_events schema exists behind admin-only service tooling.
Billing export and customer-visible analytics receive explicit Matthew approval.

fixture-checked

qr_billing_export_requests

Planned service-owned billing export request that groups local scan usage for operator review without creating billing customers, subscriptions, invoices, or metered usage writes.

id: Stable request identifier used to connect local scan evidence, operator review, and future billing export audit rows.
account_id: Platform account boundary copied from the scan usage events.
account_service_id: Platform service enablement record associated with the requested export.
service_id: Always qr-codes so shared billing jobs can route the request.
scan_event_ids: Local scan usage events that would be exported only after billing integration approval.
quantity: Total scan quantity represented by the local scan events.
billable: False while billing export remains disabled and no customer subscription exists.
status: Blocked, ready_for_review, exported, or canceled state for the billing export request.
requested_by_user_id: Platform user or approved operator that prepared the request.
requested_at: Null while this is only fixture evidence and no export request has been recorded.
exported_at: Null until a future approved billing exporter writes usage to a billing provider.
metadata: Billing customer, subscription, export destination, approval, and blocked-reason context.

Fixture evidence

Every billing export request carries account_id, account_service_id, and service_id from the seed packet records.
scan_event_ids must resolve to local scan events inside the same account service.
quantity equals the sum of linked local scan event quantities.
billable stays false and status stays blocked while billing integration is not approved.
requested_at, exported_at, billing customer, subscription, and external usage write identifiers remain null.

Blocked until

Local usage_events and billing export review tables exist behind admin-only tooling.
Matthew approves billing provider customer, subscription, and metered export setup.
A future billing exporter writes audit evidence before any external metered usage is sent.

fixture-checked

qr_support_cases

Planned service-owned support and operator handoff evidence tied to QR account-service context before customer-visible support workflows or external ticketing exist.

id: Stable support case identifier used by review UI, audit events, and future support tooling.
account_id: Platform account boundary copied from the account service.
account_service_id: Platform QR service enablement record associated with the case.
qr_workspace_id: Service workspace related to the support or operator handoff case.
service_id: Always qr-codes so shared support workflows can route the case.
target_type: QR service object type under review, such as qr_code or qr_import_job.
target_id: Optional QR service object identifier inside the same account service.
category: Support category such as onboarding, import_review, billing_review, redirect_review, or access_review.
severity: Low, medium, high, or urgent local triage severity.
status: Draft, ready_for_review, blocked, open, resolved, or canceled state.
subject: Short operator-readable support case summary.
created_by_user_id: Platform user or approved operator that prepared the local case.
created_at: Null while this is fixture evidence and no support case has been recorded.
resolved_at: Null until a future support workflow closes the case.
metadata: Approval, blocked-action, customer-visibility, and notification context.

Fixture evidence

Every support case carries account_id, account_service_id, qr_workspace_id, and service_id from the seed packet records.
target_id is null or resolves to a QR code, import job, mutation request, billing export request, route resolution, or scan event in the same account service.
status stays draft or blocked and severity stays low or medium while the record is fixture evidence.
customer_visible is false and external_notification_sent is false before customer timelines or support notifications exist.
blocked_external_actions includes external ticket creation, customer notification, escalation, customer timeline publication, and service-status changes.

Blocked until

Local support_cases schema exists behind admin-only tooling.
Matthew approves customer-visible support timelines, outbound notifications, and any external support-system integration.
Support case audit events are written before any case changes service status or escalates operational work.

fixture-checked

qr_campaigns

Planned service-owned campaign record for grouping QR codes before customer dashboards, hosted CRUD, scan analytics, or exports exist.

id: Stable campaign identifier used by QR code records, scan metadata, exports, and audit evidence.
account_id: Platform account boundary copied from the resolved workspace.
qr_workspace_id: Service workspace that owns the campaign.
name: Operator/customer label used to group related QR codes.
status: Planned, active, archived, or paused state checked before campaign dashboards or exports are shown.
created_by_user_id: Platform user or approved operator who prepared or created the campaign.
created_at: Audit-friendly creation timestamp.
updated_at: Last campaign settings or status change timestamp.

Fixture evidence

Every planned campaign carries account_id and qr_workspace_id that match the seed packet workspace.
Every QR code campaign_id is null or resolves to one campaign inside the same workspace.
Scan and audit metadata can carry the resolved campaign_id without enabling customer-visible analytics.
created_at and updated_at remain null while campaign records are only fixture evidence.

Blocked until

Local QR campaign schema exists behind admin-only tooling.
Hosted QR dashboards resolve account, workspace, role, and entitlement context before campaign CRUD.
Customer-visible campaign analytics and exports receive explicit Matthew approval.

fixture-checked

qr_audit_events

Planned service-owned audit event evidence that maps QR mutations to the shared platform audit envelope without enabling customer access or external workflows.

id: Stable audit event identifier used for fixture checks and future audit-event joins.
account_id: Platform account boundary copied from the resolved workspace and QR code.
account_service_id: Platform service enablement record associated with the audited QR action.
qr_workspace_id: Service workspace that owns the audited QR code.
qr_code_id: QR code record targeted by the audited action.
service_id: Always qr-codes so shared platform jobs can route the audit event.
action: Normalized QR audit action such as qr_code.created or qr_code.destination_changed.
target_type: Service object type targeted by the audit event.
target_id: Service object id targeted by the audit event.
actor_user_id: Platform user or approved operator responsible for the future audited action.
occurred_at: Null while this is only fixture evidence and no mutation has happened.
metadata: Slug, campaign, prior destination, next destination, skipped external actions, and operator decision context.

Fixture evidence

Every planned audit event carries account_id, account_service_id, qr_workspace_id, qr_code_id, and service_id from the seed packet records.
action stays in the QR service auditEvents allowlist and target_type stays qr_code.
target_id matches one planned QR code in the same workspace.
actor_user_id resolves to the local primary owner placeholder while no external identity exists.
occurred_at remains null and metadata.external_actions stays skipped while this is only fixture evidence.
metadata.campaign_id matches the QR code campaign_id when a planned campaign is present.

Blocked until

Local audit_events schema exists behind admin-only service tooling.
QR CRUD and destination-change flows resolve account, account service, workspace, QR code, role, entitlement, and operator approval before mutation.
Customer-visible audit timelines and external hosted QR workflows receive explicit Matthew approval.

fixture-checked

qr_mutation_requests

Planned service-owned mutation request for QR create, destination-change, archive, restore, and export actions before hosted CRUD or external redirects exist.

id: Stable mutation request identifier used to connect operator review, service audit events, and later admin-only execution.
account_id: Platform account boundary copied from the resolved workspace and QR code.
account_service_id: Platform service enablement record associated with the requested mutation.
qr_workspace_id: Service workspace that owns the target QR code.
qr_code_id: QR code record targeted by the requested mutation.
service_id: Always qr-codes so shared platform jobs can route review and audit evidence.
action: Normalized requested action, such as qr_code.destination_change_requested.
requested_by_user_id: Platform user or approved operator that requested the future mutation.
requested_at: Null while this is only fixture evidence and no mutation request has been submitted.
status: Planned, pending_review, approved_local_only, applied, or blocked state for the requested mutation.
entitlement_checked: False until local entitlement reads exist behind admin-only service tooling.
operator_approval_required: True while Matthew approval and local operator review are still required before mutation execution.
external_effect_performed: False so the fixture cannot imply a redirect, DNS, billing, invite, or production route side effect.
metadata: Slug, campaign, prior value, requested value, blocked reason, and planned audit action.

Fixture evidence

Every planned mutation request carries account_id, account_service_id, qr_workspace_id, qr_code_id, and service_id from the seed packet records.
requested_by_user_id resolves to the local primary owner placeholder while no external identity exists.
requested_at stays null, status stays planned, and entitlement_checked stays false while this is only fixture evidence.
operator_approval_required stays true and external_effect_performed stays false until admin-only local execution is explicitly approved.
metadata.audit_event_action maps to one service audit event allowlist entry without writing an audit row for an executed mutation.

Blocked until

Local QR CRUD and mutation-request schema exists behind admin-only service tooling.
Mutation execution resolves account, account service, workspace, QR code, role, entitlement, and operator approval before changing service records.
Externally reachable redirects, customer-visible CRUD, and customer-visible audit timelines receive explicit Matthew approval.

Entitlements

active_qr_codes: limit; default 25. Maximum active, redirectable QR codes for one account service.
monthly_scans: metered-limit; default 5000. Monthly recorded scan events before soft-limit operator review.
scan_retention_days: limit; default 90. Customer-visible analytics retention window.
custom_domains: feature; default false. Whether an account can attach branded redirect domains.
branded_exports: feature; default true. Whether an account can export styled SVG and PNG assets.

adapter-planning

Usage and audit events resolve tenant context first.

QR writes local usage_events and audit_events after account, workspace, entitlement, and route status checks pass.

account_id
account_service_id
service_id
qr_workspace_id
qr_code_id
event_name
occurred_at

contract-ready

Hosted QR rollout stays adapter-first.

Next local phase: local_schema_ready.

Seed app boundary confirmed: Open QR stays a static browser app with localStorage and links.json while hosted QR work uses adapter contracts.
Workspace schema planned: qr_workspaces has account, account service, service, plan, status, creator, and timestamp fields.
Local seed records planned: Draft account, owner user, owner membership, account service, entitlement defaults, and activation audit records must exist locally before workspace preparation.
Seed packet contract defined: The local activation packet identifies account, owner, membership, account service, entitlements, QR workspace plan, external-action skips, operator review, and audit fields before any write is allowed.
Workspace provisioning fixture checked: The QR seed packet fixture now proves every manifest-declared qr_workspaces field, creator reference, pending timestamps, and audit metadata linkage before local schema work starts.
QR code record fixture checked: The QR seed packet fixture now proves planned qr_codes rows stay inside the account workspace boundary before hosted CRUD or redirects exist.
Campaign fixture checked: The QR seed packet fixture now proves planned qr_campaigns rows group QR codes inside the account workspace boundary before customer dashboards or exports exist.
Scan event fixture checked: The QR seed packet fixture now proves scan usage evidence resolves through account, account service, workspace, and QR code context before hosted redirects or billing export exist.
Audit event fixture checked: The QR seed packet fixture now proves QR mutation audit evidence resolves through account, account service, workspace, and QR code context before hosted CRUD or customer-visible timelines exist.
Route adapter blocked: Hosted redirects remain blocked until local account, workspace, entitlement, and operator approval checks exist.
Local provisioning rehearsal checked: The QR seed packet fixture now proves a rehearsal-only provisioning run can enumerate local records and blocked external writes without executing account, auth, billing, invite, DNS, redirect, or deploy actions.
Operator decision fixture checked: The QR seed packet fixture now proves the review outcome stays blocked pending Matthew approval, with approved actions empty and every activation-gated action still blocked.
Approval audit fixture checked: The QR seed packet fixture now proves operator decisions leave a platform audit row tied to the decision id, blocked actions, and skipped external action state.
Mutation request fixture checked: The QR seed packet fixture now proves planned destination-change requests stay local, approval-gated, and tied to the account workspace before hosted CRUD exists.
Import job fixture checked: The QR seed packet fixture now proves Open QR links.json or browser-library imports stay local, reviewable, and tied to the account workspace before tenant records or hosted redirects change.
Event adapter planned: QR create, scan, export, destination-change, archive, restore, and domain events map to the shared platform envelope.
External actions closed: Billing writes, invite sends, customer accounts, DNS, production deploys, and public access remain approval-gated.

fixture-backed

Seed packet checks keep QR activation local.

Local QR seed packet fixtures prove draft account, owner, membership, account service, plan-scoped entitlement values, workspace plan, planned campaign records, planned QR code records, route-resolution evidence, planned scan-event evidence, planned QR audit evidence, external-action skips, and audit target context before hosted QR work starts.

Fixture: src/content/platformSeedPackets.json
Check: npm run platform:seed-packets:check

Required mappings

account.id matches membership.account_id, account_service.account_id, service_workspace.account_id, and audit_event.account_id.
account_service.service_id and service_workspace.service_id match the QR service manifest id.
account_service.plan_key and service_workspace.plan_key match one modeled QR plan.
entitlements copy selected QR plan limits when present, fall back to QR manifest defaults for non-plan features, and keep billing_sync_status as not_created.
service_workspace stays planned and uses qr_workspaces before CRUD, redirect, analytics, or export code exists.
qr_campaigns stay planned, resolve through service_workspace.id, keep account_id aligned, and do not enable customer-visible analytics.
qr_codes stay planned, resolve through service_workspace.id and optional qr_campaigns, keep account_id aligned, and use seed-app render styles.
qr_route_resolutions stay fixture-only, resolve through the planned account, account service, workspace, and QR code, and keep redirect_performed false.
qr_route_resolutions are available only as read-only /v1 fixture responses with external_redirects_enabled false until hosted redirects are approved.
qr_route_resolutions use only manifest route-resolution blocked reasons while planned fixture states remain fail-closed.
qr_import_jobs stay planned, resolve through the planned account, account service, workspace, and QR code records, and perform no import effect.
local_provisioning_run stays rehearsal-only, references the source packet and planned workspace, lists local records to prepare, and blocks auth, billing, invites, DNS, production routes, and external QR redirects.
qr_scan_events stay non-billable, keep occurred_at null, and resolve through the planned account, account service, workspace, and QR code.
qr_audit_events keep occurred_at null, resolve through the planned account, account service, workspace, and QR code, and use only manifest-allowed QR audit actions.
qr_mutation_requests stay planned, resolve through the planned account, account service, workspace, and QR code, require operator approval, and perform no external effect.
approval_audit_events keep occurred_at and actor_user_id null, resolve through the operator decision fixture, and keep every activation-gated action blocked.
operator_review skipped actions cover billing, invite, external access, DNS, and production deploy blockers.

Fail-closed states

account.status other than draft
primary_owner.external_auth_provider_user_id present
membership.status other than planned
account_service.status other than modeled
service_workspace.status other than planned
qr_campaigns with active status, created timestamps, or a mismatched account/workspace owner
qr_codes with active status, created timestamps, duplicate workspace slugs, or a mismatched account/workspace owner
qr_route_resolutions with redirect_performed true, entitlement_checked true, missing blocked_reason, or mismatched account/workspace/code context
qr_import_jobs with performed imports, timestamps, approved/imported status, unsupported source artifacts, broken QR code links, or mismatched account/workspace/code context
local_provisioning_run with timestamps, approval, executed result, missing local records, or missing blocked external writes
approval_audit_events with actor_user_id, occurred timestamps, approved actions, missing blocked actions, or external actions not marked skipped
qr_mutation_requests with requested timestamps, approved/applied status, entitlement checks marked complete, missing operator approval, external effects, or mismatched account/workspace/code context
qr_scan_events with billable true, occurred timestamps, billing export enabled, or mismatched account/workspace/code context
any external action not marked skipped
billing customer, product, price, subscription, or metered export marked created

Roles

owner: Can manage the account service, workspace settings, QR records, exports, and future billing review screens.
admin: Can manage QR records, campaigns, scan reporting, and workspace settings, but cannot approve billing or external account changes.
editor: Can create, edit, archive, restore, and export QR codes within an enabled workspace.
viewer: Can review QR codes, campaigns, and scan analytics without changing destinations or exporting assets.

Operator gates

account_activation: manual; No customer account or first owner membership is created until Matthew explicitly approves activation. Evidence: account_identity_verified, membership_scope_reviewed, external_actions_skipped.
invite_sending: manual; Invite emails and external user access remain disabled until the platform has an approved invite flow. Evidence: membership_scope_reviewed, usage_audit_events_ready, external_actions_skipped.
billing_sync: manual; Stripe customer, subscription, product, price, and metered billing writes are outside this manifest. Evidence: entitlement_defaults_reviewed, usage_audit_events_ready, external_actions_skipped.
custom_domain: manual; Branded redirect domains require explicit DNS and production routing approval before enablement. Evidence: account_identity_verified, entitlement_defaults_reviewed, external_actions_skipped.

Modeled only

Starter

active_qr_codes: 25
monthly_scans: 5000
scan_retention_days: 90
team_seats: 3

Approval-gated

Growth

active_qr_codes: 250
monthly_scans: 50000
scan_retention_days: 365
team_seats: 10

Tenant isolation checks

Every QR code, scan event, campaign, and service setting carries account_id or resolves through qr_workspace_id.
Public redirect routes resolve the slug to exactly one account workspace before recording usage or redirecting.
Background export and analytics jobs include account_id, service_id, and workspace context.

Audit events

qr_code.created
qr_code.updated
qr_code.archived
qr_code.restored
qr_code.destination_changed
qr_domain.configured