[$250] Give users on a domain the ability to join their colleagues when the company is already using Expensify

[anmurali]

Proposal: Allow a private domain sign up, whose company is already using Expensify to request to join relevant workspace(s)

Problem: One of the cool things about Expensify is that anyone can sign up without their company's permission or invitation. But this means when an employee signs up independently they are not aware their company is already using Expensify and so end up creating their own workspaces in error, causing a lot of confusion for themselves and their company

Solution: Mirror Classic when it comes to an employee that signs up with a private domain email of a company that already has one or more workspaces. It goes like this:

1. Sign-up with an email address on a private domain that has existing workspace owners
2. We ask for their first name/last name (Ice breaker)
3. Next, we show a step that:

• Let’s them know people on derp.com are already using Expensify.
• We’ve sent a magic code to validate their account so they can join them
• An input for said magic code to validate the account
• An option to skip and move on with onboarding as normal if they prefer

4. If they validate the account, the next step shown is a list of all the workspaces owned by members of their private domain.

• The CTA is Ask to join or Join based on the workspace JSON's automaticJoiningEnabled parameter being set to false or true respectivey
• They can only pick one workspace in the list

6. If they click on the CTA we do one of two things depending on if the workspace pre-approves join requests (Join), or an admin needs to accept (Ask to join):

• Pre-approval not required:
  • Add them to the workspace
  • Drop them in the LHN
  • populate their onboarding/ConciergeDM with the invited member set of tasks
• Pre-approval required:
  • Drop them in the LHN to continue exploring the product
  • Send the actionable message in the #admins room to accept or decline (just like policy join links that require approval)
  • On the workspaces page, show the workspace row they’re pending to be accepted to join with the “[Requested]” badge (just like a policy join request that needs to be approved)
  • If they select New Workspace in the + menu or Workspace page, have a warning just to let them know we’re waiting on their colleagues to still accept the request to join
  • Once accepted, they’ll get an email as they’re added to the workspace and we populate their onboarding/ConciergeDM with the invited member set of tasks.

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021832414536636098293
• Upwork Job ID: 1832414536636098293
• Last Price Increase: 2024-10-11

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @allroundexperts

[melvin-bot]

Current assignee @dubielzyk-expensify is eligible for the Design assigner, not assigning anyone new.

[dubielzyk-expensify]

Here's the overall flow:

Included workspace member count and owner after feedback in Slack. Btw, if there's no existing workspace that they can join, we continue with the intent picker like normal onboarding

cc @Expensify/design for thoughts and feelz

[shawnborton]

Looks solid to me!

[shawnborton]

How does this look on desktop?

[dannymcclain]

Looks solid to me!

Same!

How does this look on desktop?

Also curious 🙃 👀

[dubielzyk-expensify]

Here's the desktop mocks:

Do you think it's better if I don't stretch the validation code to be full-width with the modal?

[trjExpensify]

I like the full width version, personally! ❤️

[shawnborton]

Yeah, the full width does look nice. Thanks for the desktop mocks, they check out nicely ✅

[dannymcclain]

Agree! Stretch it baby! Desktop mocks looking good. 🫶

[dubielzyk-expensify]

The jury has spoken. Final Figma files can be found here: https://www.figma.com/design/ir27daDKHaB1g4iZCT22K5/Onboarding-v2?node-id=7147-9183

[anmurali]

@trjExpensify - can this be built by the contributor or do we need BE code? Curious for a second set of eyes. Asking you as you wrote down the steps in the solution

[trjExpensify]

I think this is mostly FE, but we might need some BE work for the "Select a workspace" page to get that list of accessibleDomainPolicies - I'm not quite sure if we have that available to NewDot.

@luacmartins & @mountiny we built the request to join stuff in simplified collect with the Share policyJoinLink a while back, so the #admins message to accept or decline (if pre-approval is required) should be in place and usable here already, right?

[luacmartins]

Yes, we have the system message in #admins when users try to join via the link

[trjExpensify]

Cool, so should be reusable to call that request to join from here when needed with Ask to join:

but we might need some BE work for the "Select a workspace" page to get that list of accessibleDomainPolicies - I'm not quite sure if we have that available to NewDot

Do you have any idea if we'd have a list of accessibleDomainPolicies available in NewDot or if that's going to need BE work here?

[luacmartins]

Do you have any idea if we'd have a list of accessibleDomainPolicies available in NewDot or if that's going to need BE work here?

AFAIK we don't have this data in NewDot yet, so we'd need to fetch it when we open that page.

[trjExpensify]

Kewl, so we do need BE here then yes?

[luacmartins]

yes

[mountiny]

Yeah, agreed we will need to fetch that; also, somehow, indicate which one is "Join now" and which one is "Ask to join". couple questions:

1. How do the "Join Now" and "Ask to join" changes when you click on them?
2. If user clicks skip for now, where will they access this modal/ list of workspaces to join with buttons later in the product?

[trjExpensify]

How do the "Join Now" and "Ask to join" changes when you click on them?

Join now = workspace doesn't require approval to join
Ask to join = workspace needs admin approval to join

That's the distinction between the two buttons, so I assume that's something on the policy object we store for use with policy join links.

As for what happens when you click them, that's outlined in the OP in step 5. Let me know if you have any qs on that!

If user clicks skip for now, where will they access this modal/ list of workspaces to join with buttons later in the product?

If we're mirroring the Inbox on OldDot, they don't. So maybe "Skip" is better than "Skip for now" which implies you can get back to it. We could look at something on the workspaces page with a list of available workspaces to join instead of the empty state when applicable, but I'm also fine to descope that to start and keep it to this one-time onboarding modal flow.

[anmurali]

That's the distinction between the two buttons, so I assume that's something on the policy object we store for use with policy join links.

I have clarified the exact workspace setting in the original description!

[anmurali]

Final mockuops

Mobile - Employee

Web - Employee

Actionable whisper in # admins (Exists)

[melvin-bot]

@parasharrajat, @allroundexperts, @isabelastisser, @marcaaron 12 days overdue. Walking. Toward. The. Light...

[parasharrajat]

In progress. Waiting on some updates from internal team.

[anmurali]

@allroundexperts - where did we land on this question?

Going to assign you @flodnv so we can see this last bit through.

[parasharrajat]

@allroundexperts What's new here?

[melvin-bot]

@flodnv, @parasharrajat, @allroundexperts, @isabelastisser, @marcaaron Eep! 4 days overdue now. Issues have feelings too...

[flodnv]

We are discussing here: https://expensify.slack.com/archives/C07HPDRELLD/p1737992562644379?thread_ts=1736817885.544729&cid=C07HPDRELLD

[melvin-bot]

@flodnv, @parasharrajat, @allroundexperts, @isabelastisser, @marcaaron Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[isabelastisser]

@allroundexperts, can you please provide an update? Thanks!

[allroundexperts]

@flodnv Are your changes deployed?

[flodnv]

As of 1 hour ago, yes they're in production!

[parasharrajat]

What is next here? @allroundexperts @flodnv. I don't have access to that Slack thread, so I can't tell what's happening in the background.

[flodnv]

I am done making the API that was blocking the issue. I don't know what else remains, @allroundexperts ?

[allroundexperts]

It's on me now. I'll try to add screen recordings tomorrow.

[parasharrajat]

Please tag me to the PR.

[allroundexperts]

Here's the draft PR @parasharrajat