-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Workspace page upgrades for a user that asked to join one or more available workspaces during signup #54483
Comments
Triggered auto assignment to @shawnborton ( |
@shawnborton assigned you to help me with figma mockups for those two. @jamesdeanexpensify - can you help us with the copy for the warning message? The intention is to prevent an employee that is waiting to join an existing workspace from creating a new one in error. |
Something simple like this? Create new workspace? (alts: "Heads up!" or "Are you sure?") |
Yeah so maybe like: Create workspace |
That looks good. If we agree, I can write down the steps as a proposal and start. |
Let's see what @anmurali thinks! |
Thanks for the mock @parasharrajat - let's see if this is what @anmurali had in mind. cc @Expensify/design for visibility too One thing to call out - before we make this change, should we wait until the workspace confirmation modal is merged? That might actually kind of solve this problem and maybe we could just close this? |
@shawnborton It will not solve this problem. I know this cause I am reviewing that PR. Can I take over this issue as C+ since I have some context over workspace creation? |
@parasharrajat Please fix the |
Why every? Requirement does not mention that particularly. |
Yes, but I believe that was @anmurali's intention. To show the prompt if every workspace has the status as requested. This will be cleared up when we heard back from her about this. |
@shawnborton Whoops! This issue is 2 days overdue. Let's get this updated quick! |
I like the mockup and the proposal. Re: the every vs. some - it's a good call out. Basically if I am already in a workspace, and have one pending on a request and go to create another, should there be a warning or not - that's the question?
@shubham1206agra why won't this cover this case? Is it cause this PR only triggers a warning if the user is already a part of another workspace, i.e. not pending joining? |
Cause I don't see any warning modals in that PR. |
I guess I don't feel too strongly but agree with Shawn that the workspace confirmation might help with this issue. I feel like we had a very very similar issue not too long ago that we decided to close because we felt like the workspace confirmation would be enough. But if we really want a warning, I like what you guys have with the confirmation dialog. Could we make the button say "Create workspace" though instead of just "Create"? |
Related to #48189 (comment)
Workspace page for a user that asked to join one or more workspaces in the sign up flow
Working on the mockups
The text was updated successfully, but these errors were encountered: