-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We created multiple workspaces for user in onboarding #52519
Comments
I think @carlosmiceli is working on moving the policy creation to the |
Interesting. Carlos, how does that work if you create an account on new.expensify.com directly where there's no signUpQualifiers to choose? 🤔 |
What @marcaaron says is correct, that's what I'm working on. @trjExpensify so far, we would just not create a workspace for any signup that hasn't selected a qualifier. In fact, creating an account will not fail if for some reason the workspace fails to get created. But let's check with @anmurali to see if we'd like to add/change some logic about it. |
Okay, which means they would then see the onboarding modal and selecting the manage my team path would create a workspace? |
Oh, that's a good question (and sounds like a good idea) but I don't know about that being discussed anywhere and it's definitely outside of the scope of the issue I'm working on (which is all BE and happening before ND is loaded). |
I haven't got to this point yet, but I think as Marc said, we're going to remove the current CreateWorkspace logic of creating the policy in App during onboarding (at least temporarily so we don't create duplicates).
To clarify, I'm not working in anything that would change any logic that happens after/during signup through new.expensify.com, other than replacing the logic as I mentioned above. You will see whatever you see while signing up now. This means that no workspace will get created when signing up through new.expensify.com until we actually want to implement some logic around that. I hope I'm understanding the question 😅 |
Got it, so yeah.. if you remove the logic to create a workspace in the onboarding modal completely, you're going to break creating a workspace during onboarding for:
So I don't think we should remove it completely. Rather, if you come from expensify.com or use.expensify.com and a workspace is created for you because of the signUpQualifier selection, we skip the "How many employees do you have?" screen and creating a workspace on completion of the onboarding step. If you don't have a signUpQualifier selection, we show it and create a workspace like today. |
Ah, gotcha! Yup, that sounds good, we can do that. By the way, while it's an edge case, we should consider this again then. I think with this new situation, it's justified to just hide the back button instead of having to implement more complicated logic to skip the workspace creation if they happen to go back. |
This is being discussed here so I'm just creating a tracking issue for us to get to the bottom of it with @marcaaron @trjExpensify
https://expensify.slack.com/archives/C07HPDRELLD/p1731537294677189
The text was updated successfully, but these errors were encountered: