Product: Section 1 | SubFlow 1c: Guest Account Confirmation

[randelbrot]

🧩 Overview

Allow Guests to create an account after receiving an invitation from Coordinators so that Guests can confirm their Home Unite Us account, log in, and begin the application (Intake Profile) and onboarding process.

---

🧠 Problem Statement

Currently, Guests do not have a way to create an account for Home Unite Us. As a result, Guests cannot access Home Unite Us to create a profile, which is a required step to find housing on the platform.

---

🙋‍♀️ User Story

As a Guest, I want to confirm my Home Unite Us account, So that I can log in to Home Unite Us and begin the application (Intake Profile) and onboarding process.

---

🎯 Acceptance Criteria (Definition of Done)

Transfer information to Design to Engineering Issue to be checked off
These high-level criteria will be detailed further in Design and Engineering handoff templates

• Clear list of conditions to be met for this feature to be considered complete.
• Each should be testable and specific.

Example:

• [ ]Users can open the validation email and click the link
• [ ]The validation email will contain a temporary password
• [ ]Clicking the validation link will confirm the user account and redirect the user to a set password page
• [ ]After entering the temporary password, the user will be redirected to the set password page
• [ ]The set password page will have the same behavior as the reset password page in Product: Section 1 | Forgot Password, Reset Password #442
• [ ]The user flow can be completed across desktop, mobile, and tablet
• [ ]The user should see Guest Minimum expectations as specified on page 4 of the physical application before they can access the dashboard
• [ ]The user should acknowledge "I hereby certify that the facts contained in the Host Homes Pilot Application are true and complete to the best of my knowledge." before they can access the dashboard

---

🔍 Context / Background

Success is defined as Guests being able to receive an account creation invitation email from Coordinators and create an account on Home Unite Us after reading minimum expectations and acknowledging terms.
This feature is part of the Guest onboarding workflow where Coordinators invite Guests to the platform, and Guests must complete account confirmation before accessing the application process.

• Research Summary: [link]
• Previous Discovery Work: [link to doc]
• Related Epics or Projects: [link]

---

🖼️ Design Notes (Preliminary)

• Is this feature ready for design work? Yes / No
• Any ideas, inspiration, or existing patterns that should be considered?

Example: Use form components from the design system; style similar to Guest Intake Form.

---

📌 Scope Considerations (In/Out Scope)

• Feature List Add/Update Feature List
• Added to Feature List and completed information accordingly

In Scope:

• Responsive design across desktop, mobile, and tablet
• Email validation and account confirmation process
• Set password page integration
• User acknowledgment and certification process
• Integration with existing password reset behavior

Out of Scope (future or separate stories):

• Coordinator invitation sending functionality (separate story)
• Advanced account management features

---

🛑 Constraints / Risks / Workflow Dependency

*(Compliance / Regulatory information will be captured in the Feature List, this should be specific to the feature, where applicable)

• Must integrate with existing password reset functionality from Product: Section 1 | Forgot Password, Reset Password #442
• Depends on Coordinator invitation system being available
• After successfully logging in for the first time, the user will be redirected to the app (versus the default redirect to an AWS page). The rationale is that users will have a better first experience with the app if redirected to the app versus the AWS page. This will require additional dev effort - if significant dev effort is needed will revisit.

---

Action Items

• Assign and Prep
  • Product Manager: Understand, draft User Story and self-assign
  • Product Manager: Conduct the necessary research (if applicable), clarify any questions
  • Product Manager: Work with PM team/lead to clarify any questions about the User Story
  • Product Manager: Work with Product Team Lead to assign the appropriate size & complexity
  • Product Manager/Lead: determine if work should be split into multiple issues, if so, create issue(s) and link them in this issue (if applicable) or create as standalone.
• Draft and Review:
  • Product Manager: Change Issue Status to "In Progress"
  • Product Manager: Draft User Story
  • Product Manager: Change Issue Status to "For Review/Feedback Needed"
  • Product Manager: Add Label "Ready for: Design Peer Review"
  • Product 1st Level/Peer Review: Review to ensure the story captures the objective/goal of the feature to be developed and provides adequate for Design and Dev. Provide comment(s) in the comment section of the issue and tag assignee.
  • Product 1st Level/Peer Reviewer: Change Issue Status to "Questions/Clarification" and add label "Ready for Product.....Persona"
  • Product Manager (Assignee): Change Issue Status to "In Progress"
  • Product Manager (Assignee): Review issue comment(s) and resolve accordingly
  • Repeat above steps until all comments are resolved
  • Product 1st Level/Peer Reviewer: Change Issue Status to "For Review/Feedback Needed" and add label "Ready for: Product Lead"
  • 2nd final/Product Lead: Review and provide feedback (if any) in comment section below, add label "Ready for Product...Persona"
  • Repeat above steps until all comments are resolved

---

🔗 Related Tickets

• Add all related ticket(s) as sub-issues (add picture)
• Design Ticket: [876]
• Engineering Ticket: [link]
• QA Test Plan: [link]

---

📎 Resources & References

• Existing Research: [Link]
• Brand Guidelines / Design System: [Link]
• Previous or Related Designs: [Link]

[randelbrot]

Hi @fourmatte and @erikguntner, I updated the Acceptance Criteria in this issue based on our discussion earlier regarding the temporary password user flow. If anything needs to be edited, just let me know. cc @sanya301

[sanya301]

@edela0015 can you confirm if design for this was handed off (or if it is not necessary in this user story) along with date of hand off?