Account context across a visible transition

Review account switching without losing track of the active identity

Record both sides of an account change and review whether the switcher, header, and destination tell the same story.

  • ✓The header names the previous account
  • ✓Pending looks settled
  • ✓Unavailable routes lack a destination

A grounded review of the active-account signal

Transition evidence

Show the pending state as well as the final destination instead of relying on an isolated header capture.

Conflicting labels located

Use annotations to identify where old and new account names disagree.

Route expectations agreed

Define whether switching should preserve a page or return to an account landing screen.

Review a deliberate context change

A consultant uses two test identities in your application and switches from a sample agency account to a sample client account. The page content changes, but the header keeps the previous account name until another navigation. Review whether the active identity is consistently represented throughout that transition. This is your app's switcher, not a promise that Retick manages multiple external account sessions for you.

Make the transition observable

Use synthetic identities with clearly different names and harmless sample records. Capture the open switcher, selected destination, pending state, and settled header and page. Keep personal avatars, real account addresses, and unrelated customer records out of view. Note the starting route, browser, build, and whether switching is expected to preserve that route. Supported browser recording or an authorized uploaded video can show the sequence.

Keep label lag separate from access claims

In Retick, inspect AI candidate findings and annotate the conflicting header and page labels. A concrete issue is Header retains the previous identity after account switch. Edit unsupported explanations about cached permissions or leaked records out of the draft. If the media does show unexpected content, describe the visible sample record and ask the application owner to investigate rather than presenting a visual suspicion as a confirmed authorization defect.

Example acceptance criteria

Once the switch has settled, the account indicator and destination page should identify the selected synthetic account consistently. While the change is pending, the interface should not present the previous identity as an unqualified current state. The switcher should mark the selected entry according to the approved design. Check switching back and verify whether the agreed route is preserved or replaced by the intended landing page.

Follow up across the context boundary

Group both directions of switching in a review cycle and repeat with a long account name and a route unavailable to the destination test account. Download reviewed findings or send a selected individual-media issue set to Trello. Retick does not verify account isolation, alter permissions, or execute switching tests for the application. Technical access checks remain essential; matching labels explain the visible context but do not prove that underlying data and actions belong to the right identity.

Keep identity context clear through the switch

Review two safe accounts and make the settled destination explicit.