Invitation acceptance in the customer's application

Review workspace invitations before a customer joins the wrong context

Show the workspace, invited role, and current test identity at the acceptance decision so the review does not lose account context.

  • ✓The wrong identity is easy to miss
  • ✓Switching loses the invitation
  • ✓Arrival does not identify the workspace

Make joining context visible without claiming permission proof

Identity before commitment

Keep the signed-in identity visible in the evidence surrounding acceptance.

Destination continuity

Connect the invitation's workspace name to the screen reached after joining.

Permission questions routed correctly

Separate a displayed role explanation from the technical verification of membership.

Start at the invitation decision

A contractor opens an invitation to your application's sample workspace while already signed in with another test identity. The acceptance page shows a workspace name but hides which identity will join. Review the decision before acceptance, the mismatch guidance, and the destination after joining. These invitation screens belong to your app; the scenario does not describe workspace invitation functionality supplied by Retick.

Use controlled people and workspaces

Prepare fictitious workspace names, synthetic addresses, and an authorized invitation fixture. Keep usable invitation links and real member lists outside the recording. Capture the acceptance page, the identity-switch option, and the resulting destination using supported browser capture or upload authorized media. Note the invited role, current test identity, app build, and whether membership already exists so the receiving team can reconstruct the branch.

Describe the decision the screen obscures

An example issue is Invitation acceptance hides the currently signed-in identity. Annotate where account context should be visible and keep the workspace title in view. Review Retick's AI candidate findings and edit assertions about unauthorized access unless separate evidence establishes that behavior. A missing identity label, unclear role description, and incorrect post-acceptance destination should remain separate findings with their own expected results.

Example acceptance criteria

Before acceptance, the screen should identify the destination workspace and the current test identity according to the approved display policy. If the identities differ, the agreed account-switch or sign-out route should be understandable and return to the intended invitation state. After controlled acceptance, the destination should visibly identify the joined workspace. Have the permissions owner verify the role separately rather than accepting the displayed label as proof.

Check the branches after the copy changes

Keep new-member, existing-member, and identity-mismatch evidence distinct within a review cycle. Repeat the approved acceptance journey on the revised build and inspect the landing context, then export reviewed files or selected individual-media Trello cards. Retick does not issue invitations for your application, validate membership grants, or prove authorization boundaries. Those behaviors need direct application tests. Visual review should explain the decision a person sees without implying that a readable invitation establishes correct access control.

Review the decision before joining a workspace

Capture a fictitious invitation and clarify identity, destination, and role language.