How MFA Works Across Multiple Organizations

MFA has two parts: an authenticator enrolled for your login and the security requirement applied when you enter a workspace.

The login and the policy are different

Your saved authenticator belongs to your CaseWyze login identity. The destination organization's policy and your role there determine whether MFA is required for workspace access. An organization can require MFA even when another organization you belong to does not.

What you may see

  • Required, no verified authenticator: you are guided through Set Up MFA.
  • Required, authenticator already enrolled: you may see Verify MFA and enter the current verification code.
  • Required, session already verified: the requirement may already be satisfied without another prompt.
  • Not required: that workspace does not impose its own MFA verification gate merely because another workspace requires it.

Keep the same authenticator

You generally do not need a separate authenticator enrollment for every organization accessed with the same login. Do not delete or reset your working authenticator when switching to an organization that does not require MFA.

A different email or separate login identity can have different MFA enrollment. Always check which account you are using. A new or expired session may require verification again.

Made with ProductLift
CaseWyze Website