The destination organization’s requirements apply when you switch; the previous workspace’s policy does not override them.
Suppose Organization A does not require MFA and Organization B does. When you select B, CaseWyze checks whether your session satisfies B's requirement. If not, it directs you to setup or verification before activating protected access. Password sign-in to A alone is not enough to satisfy B.
Switching from B to A does not remove the authenticator from your login or disable B's policy. A does not add its own mandatory workspace challenge when it has no applicable MFA requirement. You may still have a verified session.
An already verified session may satisfy both. A prompt can still occur if the destination session needs verification after the switch, your session has expired, or the login context changed. Use the current code from the authenticator associated with that login.
If a workspace-wide setting appears optional but your role requires MFA, verification can still be required. Ask an administrator to review both settings instead of assuming the switch is malfunctioning.
Returning to a less restrictive workspace does not bypass the required workspace's security rules.