Skip to content

Two stage user provisioning UI improvement #36696

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

Jtang-1
Copy link
Contributor

@Jtang-1 Jtang-1 commented Jul 9, 2025

Product Description

This PR has three UI changes:

This change affects two stage user provisioning:

  1. When confirming an account, the email field is now disabled. It is already prepopulated with the email set by the admin who created the user so it should not be editable.
    Screenshot 2025-07-09 at 3 32 47 PM

These changes affect both two stage user provisioning and two stage user provisioning by SMS FF:
2. When "Require account confirmation" is checked, the "password" field is hidden and "send account confirmation" field is shown.
3. When "Require account confirmation" is not checked, the "password" field is shown and "send account confirmation" field is hidden.

Screen.Recording.2025-07-09.at.3.31.18.PM.mov

Technical Summary

USH-6027
Tech Spec

Feature Flag

TWO_STAGE_USER_PROVISIONING
two_stage_user_provisioning_by_sms

Safety Assurance

Safety story

This change is purely a UI change.

Automated test coverage

no automated test

QA Plan

QA-7908

Rollback instructions

  • This PR can be reverted after deploy with no further considerations

Labels & Review

  • Risk label is set correctly
  • The set of people pinged as reviewers is appropriate for the level of risk of the change

Jtang-1 added 4 commits July 9, 2025 12:07
…firmation" is not toggled.

sending account confirmation has no relevance if the workflow does not require account confirmation
@Jtang-1 Jtang-1 added the product/feature-flag Change will only affect users who have a specific feature flag enabled label Jul 9, 2025
@dimagimon dimagimon added the Risk: High Change affects files that have been flagged as high risk. label Jul 9, 2025
@Jtang-1 Jtang-1 marked this pull request as ready for review July 11, 2025 16:39
@Jtang-1 Jtang-1 requested a review from esoergel as a code owner July 11, 2025 16:39
@Jtang-1 Jtang-1 requested a review from minhaminha July 11, 2025 16:39
@Jtang-1 Jtang-1 added the awaiting QA QA in progress. Do not merge label Jul 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting QA QA in progress. Do not merge product/feature-flag Change will only affect users who have a specific feature flag enabled Risk: High Change affects files that have been flagged as high risk.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants