Enterprise and BU MFA requirements
Manage requirements in Settings → Security → MFA. Administrators must enable their own MFA before changing a requirement and confirm changes with a fresh authenticator or recovery code.
Drushya security
Protect your account.
Control access to your team’s work.
Add an authenticator to your sign-in. Set clear access requirements for your Enterprise and Business Units.
For every account
Two-factor authentication (MFA)
Individual and Enterprise users can protect their accounts with two-factor authentication using Google Authenticator or Microsoft Authenticator.
After setup, a fresh sign-in requires your password plus a six-digit authenticator code. A password alone is not enough to sign in.
Extra protection when you sign in
- Use Google Authenticator or Microsoft Authenticator.
- Keep single-use recovery codes for when your authenticator is unavailable.
- Continue using a valid signed-in session without entering a code every time you reopen the app.
- Enable MFA yourself, or complete setup when your organization requires it.
- 01
Open Account settings
Sign in to Drushya, open Settings → Account, and choose Set up authenticator. Confirm your current password.
- 02
Connect your authenticator
Scan the QR code with Google Authenticator or Microsoft Authenticator. If you are using the same phone, enter the setup key manually.
- 03
Confirm and save recovery codes
Enter the six-digit code to enable MFA. Save your single-use recovery codes somewhere secure and separate from your phone.
Finish recording and save your work before setup: enabling MFA signs out other devices and connected services.
Enterprise security
Set the requirements for your organization
Enterprise Owners can require MFA across their Enterprise. Business Unit Admins can require it within the Business Units they administer. An Enterprise requirement takes precedence.
Required enrollment
Members must complete setup before accessing meetings when a policy requires MFA. The strictest applicable Enterprise or assigned BU requirement applies. Switching Business Units does not bypass it, and members cannot disable required MFA.
IP allowlisting
Enterprise Owners can restrict access to approved public IP addresses and ranges. Test the policy in monitor-only mode before enforcing it.
Roles and audit logs
Enterprise and BU roles control administration. Shared Workspace roles control collaboration. Review administrative activity, including MFA policy changes, in Settings → Security → Audit log. Visibility follows role and Business Unit permissions.
Encrypted connections
Drushya protects connections to its website and API using HTTPS with TLS 1.2 or TLS 1.3.
Read about privacy and data handling →Security questions, answered
Who can enable MFA?
Any Individual or Enterprise user can enable two-factor authentication in Settings → Account. It is optional unless their Enterprise or Business Unit requires it.
When will I need an authenticator code?
After enabling MFA, each fresh sign-in requires your password and an authenticator code, or a single-use recovery code. This includes signing in after signing out, after your session expires, or on another device. Reopening an app with a valid signed-in session does not require another code. Drushya currently has no ‘Remember this device for 30 days’ option.
What happens when my organization requires MFA?
Members who have not enrolled must set up an authenticator before continuing to access meetings. The requirement applies to existing sessions on their next request and to newly joined members. Users cannot disable MFA while an applicable Enterprise or Business Unit policy requires it.
What if I lose access to my authenticator?
Use one of the recovery codes you saved during setup in place of an authenticator code. Each code works once. Store them securely and separately from your phone. A password reset does not remove MFA. Contact support if you cannot access either your authenticator or your recovery codes; an automatic email-only MFA reset is not available.
Does making MFA optional turn it off for existing users?
No. Removing an Enterprise or Business Unit requirement leaves each user’s MFA enabled. Users may disable their own MFA only when no applicable policy requires it, using their password and a fresh authenticator or recovery code.
Questions about account security? Contact support@mydrushya.com.