Skip to content

Account, Settings, Support, And Admin-Adjacent Flows

Last audited: 2026-06-26.

Current Screens

Account routes:

  • /account
  • /account/profile
  • /account/address
  • /account/preferences
  • /account/payment
  • /account/bank-account
  • /account/bank-account/add
  • /account/bank-account/[accountId]
  • /account/legal
  • /account/terms-of-service
  • /account/privacy-policy
  • /account/support
  • /account/data-export
  • /account/delete-account

Support routes:

  • /support
  • /report-problem

Admin-adjacent mobile surface:

  • Problem reports are submitted from mobile and reviewed from admin/backend tooling.

Current Behavior

Account flows cover current user display/update, address/profile fields, language and telemetry preferences, payment/subscription entry points, bank accounts, legal documents, support links, data export, and account deletion.

Payment/subscription and bank-account management are owner-only account surfaces. Tenant navigation hides the payment entry, and tenant deep links to /account/payment, /account/bank-account, or /account/bank-account/add redirect to /account/profile instead of exposing subscription, payout, Stripe Connect, or bank-account controls.

Integration QA on 2026-06-26 verified owner and tenant address screens on the deployed integration app. Owner address edits persisted through PUT /v1/users/current 200. Tenant address edit/cancel exited edit mode without sending a user update request.

Integration QA on 2026-06-26 verified owner and tenant legal screens on the deployed integration app. /account/legal rendered accepted legal-document state, /account/terms-of-service and /account/privacy-policy rendered for both roles, and the backend legal fetches returned GET /v1/legal/terms-of-service 200 plus GET /v1/legal/privacy-policy 200.

The preferences surface includes optional diagnostics/product analytics consent. Environment-level telemetry disable still overrides the local opt-in.

Report-problem supports user-submitted problem reports with optional screenshot/photo handling through the backend problem-report endpoint. Integration QA on 2026-06-26 verified the account support Zgłoś problem CTA routes into /report-problem, and verified the report form at a short desktop viewport after fixing the submit action layout: the optional screenshot picker no longer covers Wyślij wiadomość, and a submitted owner report returned POST /v1/problem-reports 201.

Current Backend Touchpoints

  • GET /v1/users/current
  • PUT /v1/users/current
  • PATCH /v1/users/current/settings
  • GET /v1/users/current/data-export
  • DELETE /v1/users/current
  • GET /v1/legal/terms-of-service
  • GET /v1/legal/privacy-policy
  • GET /v1/subscriptions/current
  • GET /v1/subscriptions/portal
  • GET /v1/bank-accounts
  • POST /v1/bank-accounts
  • PUT /v1/bank-accounts/{id}
  • DELETE /v1/bank-accounts/{id}
  • POST /v1/problem-reports

What To Check

  • Cognito identity and backend user record when profile data is missing.
  • Local telemetry preference and public env flags when analytics are unexpectedly disabled.
  • Subscription portal and current subscription responses when owner account payment looks wrong.
  • Tenant role state and account-route guards when owner payout or bank-account controls appear for a tenant.
  • Legal document endpoint responses and accepted-document state when /account/legal, /account/terms-of-service, or /account/privacy-policy looks empty or stale.
  • Problem report backend logs/admin endpoints when support submissions fail.