SSO selection in the customer's app
Help customers choose the right sign-in route in your SSO picker
Review the choice and return states of your own provider picker while keeping identity configuration outside the visual review's claims.
- ✓Similar labels conceal different routes
- ✓Returning removes the instructions
- ✓A visual symptom becomes a protocol claim
A focused handoff before the external sign-in step
Recognizable routes
Connect provider labels to the distinction a customer actually needs to make.
Cancellation context
Preserve evidence of what the picker shows after an abandoned redirect.
Clear owner boundaries
Separate wording and layout findings from identity configuration questions.
Frame the choice before the redirect
An employee opens your application's sign-in page and sees several organization-specific options with nearly identical labels. They choose the wrong route, cancel, and return to a picker that no longer shows the original guidance. Review how a customer recognizes the right option and recovers from cancellation. This is a review of your application's SSO selection screen, not a claim that Retick connects to those identity providers.
Capture controlled provider states
Use fictitious organization names and an authorized test environment. Record the initial picker, selection feedback, and return after a controlled cancellation. Avoid live provider sessions, account lists, redirect URLs carrying sensitive parameters, and organization secrets. Where an external transition is simulated, state that explicitly. Include viewport, configured test options, and the app build so another reviewer can recreate the visible choice.
Separate recognition from connection failures
Bring the media into Retick through supported upload or browser capture. AI candidate findings may help draft observations, but inspect each one. For Duplicate provider labels hide organization differences, annotate the labels and explanatory text. Edit out any assertion that federation failed if the recording stops before authentication. A naming defect, a missing return message, and a connection error require different evidence and different owners.
Example acceptance criteria
Each available route should display the agreed distinguishing organization or method label without clipping at the reported width. After cancellation, the picker should restore its explanatory context and allow a different selection. The chosen route should show appropriate visible progress without leaving competing actions ambiguous. Have the identity owner confirm expected routing; the reviewer should check the actual destination only in the approved test setup.
Check the picker after configuration changes
Keep captures for a short option list, a longer label, and a cancelled transition in the same review cycle. Follow up after copy or layout changes using those conditions, then download reviewed issues or export selected individual-media findings to Trello. Retick does not configure identity providers, execute sign-in tests, or establish federation correctness. Protocol behavior, tenant routing, and account authorization need separate application testing beyond what a captured picker can show.
Make your provider choices distinguishable
Review labels, cancellation, and visible progress using an approved test picker.