hackforla
Product: Section 1 | Subflow 1b: Coordinator Invite Guests
🧩 Overview
[Provide a brief description of the feature, outlining its purpose and expected outcome see the related user story - We need to do X for Y reason.]
🧠 Problem Statement
What problem are we solving, and why is it important? Example: Hosts currently lack an easy way to share information about themselves and their homes for the matching process.
🙋♀️ User Story
As a [type of user],
I want [some goal or capability],
So that [reason or value it delivers].
Example:
As a Host,
I want to fill out a Profile with details about myself and my home,
So that I can be accurately matched with a guest.
🎯 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
Any relevant links, decisions, research, or history.
- 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:
- Initial release of host profile questions and storage.
Out of Scope (future or separate stories):
- Matching algorithm
- Admin dashboard for reviewing profiles
🛑 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: [link]
- Engineering Ticket: [link]
- QA Test Plan: [link]
📎 Resources & References
- Existing Research: [Link]
- Brand Guidelines / Design System: [Link]
- Previous or Related Designs: [Link]
Problem Alignment
The Problem:
Currently, Coordinators do not have a way to invite Guests to create an account. As a result, Guests cannot create an account or profile on Home Unite Us, which are required steps to find housing on the platform.
User Story:
As a Coordinator, I want to create an account for the Guest and invite the Guest to Home Unite Us, so that the Guest can begin the application and onboarding process.
High Level Approach:
Allow Coordinators to create accounts for Guests and invite Guests to confirm their Home Unite Us accounts.
Solution Alignment
Considerations:
Goals & Success:
Success is if Coordinators can create Guest accounts and send Guests invitations to confirm the account.
Key Features:
- A button on the Coordinator home page to invite Guests
- Field to enter a Guest email address
- A verification email containing a verification link that is sent to the Guest email address
Acceptance Criteria:
- Coordinators can invite Guests via email from the Coordinator homepage
- A verification email will be sent to the email address containing a verification link
- The verification link expires after 2 weeks maximum
- The user flow can be complete on desktop, mobile, and tablet
Designs:
- [ ] Review existing designs on Figma
- [ ] Edit existing designs as needed and share a link to the updated designs in this issue
Key Decisions:
Open Questions:
- Support email, SMS, or both in the first version?
- What happens after the link expires?
- Option to request a new link from the Coordinator?
- What are the data tables that are needed and associated schemas?
- Are these blocking for this phase of work?
Hi @rpradheap, what are the criteria for the placement of the 'add guest' and 'add event' buttons?
The overall goal is to make it easy for Coordinators to view and take action on Guest or Host applications.
Below are the options that I see for the add Guest placement choice.
Considering the pros and cons of each, my take is that Option 2 is better to start. Putting the Guest functionality on the Guest tab feels logical. If it turns out this feature is used heavily by Coordinators, can always display in additional places in the future.
This is my take - am open to ideas and perspectives.
Option 1: Overview tab
Pros
- Impossible to miss, Coordinators will see it right away
Cons
- If it is included on the overview tab, does it also need to be included on the Guest tab? It may be confusing for the user if the invite functionality is not also on the Guest tab. This would detract from the simplicity of the app.
- We don't know how often this functionality will be used and it takes up space on the Overview tab that may need to be used for other functionality in the future
Option 2: Guest tab
Pros
- Aligns best with the information architecture - Guest functionality is under the Guest tab
- Allows us to avoid taking up space on the overview tab, esp if the functionality is not used often
Cons
- Coordinators will need to click into the tab to see the Add Guest functionality
@rpradheap @edela0015 do we know if the design for this was finalized? Can we please check off the design sections if they were? And would be great to know rough dates when design was completed as I am trying to come up with timelines of completion for issues
Issue re-opened to perform sanity check and review to align Figma and User. @pixellady FYI, we will further discuss in our team meeting.
This issue will be replaced by Issue #520 but we're keeping this open for reference.
