Open petertgiles opened 4 months ago
We want to add a work email field for users.
@petertgiles what is the use case for collecting a user's work email? what kind of user would want to be contacted at their work email address when applying for jobs that are for another employer?
what is the use case for collecting a user's work email
I really don't know know - that's more of a desfam question. I'm guessing this is intended to be used by people on the hiring side of the application or for gov employees who are interested in movement within the organization.
Work email verification doesn't do anything until we have a "Career planning" module built. This will be added with Talent Management. I'm gonna ice-box this issue until then.
@petertgiles what is the use case for collecting a user's work email? what kind of user would want to be contacted at their work email address when applying for jobs that are for another employer?
We're not contacting them at their work email, hence why we ask for contact email separately. We collect work email addresses for current GoC employees because it is the only reliable way to verify their status as an employee, something we need to do in order to provide them GoC specific hiring and career tools, as well as verifying requests for hiring manager access.
✨ Feature
This adds a flow to verify your work email during registration and on the profile. We also add in the verified/not verified chips on the profile.
🕵️ Details
The work email should already be collecting during registration and visible on the profile (see #10363), but here we are adding a verification step to the registration flow.
🎨 Design File
https://www.figma.com/design/L3TpcR1boZNXoSEZ4022zu/Registration-form-(All-users)?node-id=1-3&t=E520U8xrOCRY3yL8-0
🧑🎨 Designer
@substrae
📸 Screenshot
✅ Acceptance Criteria
A set of assumptions which, when tested, verify that the feature was properly implemented.
🛑 Blockers