hackforla
Product: Section 1 | Subflow 1d: Host Account Creation
🧩 Overview
Create a Host account creation system that allows potential Hosts to create accounts on Home Unite Us so they can login and apply to be a Host in the program.
🧠 Problem Statement
Currently, Hosts do not have a way to create an account for Home Unite Us. As a result, Hosts cannot login to create a profile, a required step to host Guests on the platform.
🙋♀️ User Story
As a potential Host, I want to create an account on Home Unite Us, So that I can login and apply to be a Host.
🎯 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:
- [ ] Host can access the Profile from the dashboard.
- [ ] All required profile questions display correctly.
- [ ] Hosts can save progress and resume later.
- [ ] The data is stored in the appropriate backend repository.
🔍 Context / Background
Success is defined as Hosts being able to create a user account from the Home Unite Us website. This is a foundational feature required before Hosts can begin the application and onboarding 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
- [x] Added to Feature List and completed information accordingly
In Scope:
- Basic Host account creation functionality
- Email verification process
- Responsive design across all devices
- Password validation
Out of Scope (future or separate stories):
- Must integrate with existing authentication system (AWS Cognito)
- Email deliverability concerns for verification emails
- Must ensure proper password validation and security measures
🛑 Constraints / Risks / Workflow Dependency
*(Compliance / Regulatory information will be captured in the Feature List, this should be specific to the feature, where applicable)
- Known data dependencies?
- Technical limitations?
Example: We must collect data in a way that meets GDPR and local data privacy laws.
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: [883]
- Engineering Ticket: [link]
- QA Test Plan: [link]
📎 Resources & References
- Existing Research: [Link]
- Brand Guidelines / Design System: [Link]
- Previous or Related Designs: [Link]
Issue re-opened to perform sanity check and review to align Figma and User. @pixellady FYI, we will further discuss in our team meeting.
Hi @lola3736, I have completed the sanity check on this Issue 403. No issues noted, (except for strike-through of the option for selecting Coordinator) good to pass on to Design to create Wireframes.
