Section 1 | Subflow 1b: Coordinator Invite Guests

[rossbb]

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?

[rpradheap]

@erikguntner - Is it feasible to send the invite link via SMS too?

[erikguntner]

@rpradheap Yeah, it's possible to send the link via SMS too.

[KowDesign]

Hi @rpradheap, what are the criteria for the placement of the 'add guest' and 'add event' buttons?

[randelbrot]

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

[sanya301]

@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

[erikguntner]

@rpradheap @sanya301 Did we decide on how we want to resend invites?