Alex Beaman

Nice, ya i think so! So for the `External` part of this issue, it looks like basically just want to: 1. Give non-owner admins the ability to Leave workspaces 2....

> Are we implementing that as part of the approvals logic you're working on? That's why I was kinda' asking whether this should go in #wave-control and be tracked with...

I was basically just asking if we need any difference in warning messages for admins vs non-admins leaving the workspace :D If not, groovy!

OK so if I understand correctly, here’s what we want: 1. Leaving a workspace 1. Collect 1. NOT ALLOWED if You’re the current manager of any report (a.k.a. if a...

Huh I might be crazy but i thought we already prevent people from leaving workspaces in that case or some related case, in OldDot - I'll see if I can...

Ok I was off a bit - this is what i meant to mention, which is actually "we don't allow removing the default approver from the workspace". I'm not quire...

> Right, which you're already changing to be a confirmation before updating the default approver to be the workspace admin right? I believe you're talking about https://github.com/Expensify/Expensify/issues/404210 or https://github.com/Expensify/App/issues/43885 here,...

So far I love your `Confirmation modal suggestions:` section 👍 I think it mayyyy be missing a unique message for the case "Anyone on a domain that has "prevent workspace...

And as for the designated reimburser / technical contact / preferred exporter (when connected to an accounting solution) I also like those suggestions 👍

Yikes I'm very sorry for the delay! @dragnoir can you please pull main & fix conflicts & retest? Hopefully @situchan is also back to retest so we can get this...