Open anmurali opened 1 month ago
@parasharrajat I already updated my proposal before https://github.com/Expensify/App/issues/48189#issuecomment-2337102338. Could you provide some feedbacks?
@parasharrajat, @marcaaron Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
I will post next update in 1 hour.
@parasharrajat, @marcaaron 12 days overdue. Walking. Toward. The. Light...
@cretadn22 Conceptually, the proposal looks good to me. It will be great to have more technical steps in the proposal. Can you also modify your proposal on the backed changes suggested here https://github.com/Expensify/App/issues/48189#issuecomment-2339546858 onwards? Please try to explain each step from OP.
Back from OOO, but the backend PRs still in review here. This ticket required creating a new authentication related command and turned out to be a bit involved. Getting the accessible domain policies is a performance sensitive operation as well. But I think we are nearly there with @danieldoglas's great assistance.
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:
Ask to join
orJoin
based on the workspace JSON'sautomaticJoiningEnabled
parameter being set tofalse
ortrue
respectiveyUpwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @marcaaron