Home/HighLevel/Features/Phone System/HighLevel mandatory two factor authentication for phone updates

Conversations and Inbox

HighLevel mandatory two factor authentication for phone updates

In short

HighLevel now requires a verification step whenever a profile phone number is changed. Users must confirm the change with a code sent to an already verified email, an existing verified phone, or a TOTP authenticator app. The process adds a security layer and follows the same flow used for email updates.

AreaPhone System · Phone Numbers
Used forDigital marketing agency, Solo SaaS Founder, Customer support center
Setup steps14 steps in 2 tasks
Last updatedNovember 17, 2026

01Who this is for

  • Agency admins who manage team member contact info and need to keep account takeovers from happening.
  • Solo Founders who rely on a single phone for SMS notifications and want to protect their login credentials.
  • Customer support managers responsible for updating client numbers while maintaining compliance.

02Mandatory 2FA for phone number updates, explained

The feature adds a mandatory two factor authentication challenge whenever a user edits the phone number field on their profile. After entering the new number, HighLevel prompts a modal that lists only the verification channels already trusted for that account, a verified email address, a verified phone, or a configured authenticator app.

The selected channel receives a one time code, which the user must enter to complete the update. The code is never sent to the new phone number, preventing attackers from hijacking the account by swapping numbers. Daily limits of five change attempts per user apply, and attempts beyond that are blocked until the next day.

Both self service users and admins follow the same verification flow, but the OTP is delivered to the person whose number is being changed. The setting lives within the user’s profile page or the team management area under Settings.

03How businesses use mandatory 2FA for phone number updates

  • Digital marketing agency. An admin opens Settings > Team, selects a marketer’s profile, edits the phone field, chooses the marketer’s verified email in the verification modal, inputs the received OTP and saves the change. The OTP goes to the marketer, not the admin.
  • Solo SaaS Founder. The Founder navigates to Settings > My Profile, updates the personal phone number, selects the existing verified email in the verification modal, enters the email OTP, and confirms the change. This secures the Founder’s login without involving a new device.
  • Customer support center. A support manager edits a team member’s phone number from Settings > Team, selects the member’s authenticator app as the verification method, the member supplies the six digit TOTP, and the manager finalizes the update.

04The numbers and rules that matter

  • Maximum of 5 phone/email change attempts per user per day.

05Before you start

  • At least one verified channel (email, phone, or authenticator app) must be set up on the user’s profile.
  • The user’s role must permit editing their own profile, or the admin must have permission to edit team member profiles.

06How to set up and use mandatory 2FA for phone number updates in HighLevel

Self service phone number update

  1. Open Settings > My Profile (or the user profile page).
  2. In Personal Data, click the edit button for the phone number.
  3. Type the new phone number and press Update Profile.
  4. When the Choose how to verify modal appears, select Email, Text message, or Authenticator App.
  5. Click Continue.
  6. Retrieve the OTP from the chosen channel and enter it in the prompt.
  7. Confirm the change and view the success message.
  8. If SMS is not shown, verify the current phone or use Email or Authenticator App.

Admin update team member’s phone number

  1. Navigate to Settings > Team and open the target team member’s profile.
  2. Edit the Phone number field and enter the new number.
  3. In the Choose how to verify modal, select an available verification channel.
  4. Enter the OTP (or have the team member supply the TOTP) and click Continue.
  5. Observe the success message confirming the updated number.
  6. OTP will not be sent to the new number being added.

07What it looks like in HighLevel

08Settings that matter

  • Choose how to verify. Controls which already verified channel (email, SMS, or authenticator app) receives the one time code for phone number changes.

09Things to know before you rely on it

  • A maximum of five phone or email change attempts per user is allowed each day.
  • When the daily limit is reached, further attempts are blocked until the counter resets.
  • Verification codes are never sent to the newly entered phone number.

10If something goes wrong

  • No verification options available. Set up an authenticator app or verify the email address first; at least one trusted channel is required.
  • SMS option missing. Verify the current phone number on the profile, then the SMS channel will appear.
  • OTP not received. Check spam or junk folders for email, ensure mobile network coverage for SMS, and request a new code after the resend timer expires.
  • Daily limit reached. Wait until the next day for the attempt counter to reset before trying again.
  • Lost access to both email and phone. Use backup codes if they are set up, or ask the account owner or admin for assistance.

11How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

Wondering if the new 2FA requirement will slow down your team’s day to day workflow? It adds a quick step. Pick a trusted channel, grab the code, and confirm. But it stops a whole class of account takeover attacks that happen when someone hijacks a newly added phone number.

If I were rolling this out, I’d first make sure every user has at least one verified channel, preferably an authenticator app, so the process never stalls. A quick check of the daily attempt limit also helps you avoid surprise lockouts during busy periods.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 17, 2026

Common questions

Common questions about mandatory 2FA for phone number updates.

Why can’t I send the OTP to my new phone number?

For security, OTPs are delivered only to channels that are already verified on the account, which stops attackers from adding a new number and receiving the code.

I don’t see SMS as a verification option, what should I do?

SMS appears only if the existing phone on file is verified. Use Email or the Authenticator App instead, or verify the current phone first.

How many times can I attempt a change per day?

You can try up to five phone or email changes per user each day. After that, attempts are blocked until the next day.

Who receives the OTP when an admin updates a user’s phone number?

The OTP is sent to the team member whose profile is being edited, not to the admin performing the update.

Can I use my authenticator app instead of Email or SMS?

Yes, if a TOTP authenticator app has been enabled for the account, you can select Use Authenticator App and enter the six digit code.

What if I’ve lost access to both my email and phone?

Use backup codes if they are set up, or contact your account owner or admin for identity verification and recovery support.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.