CRM Login or Access Problems: Restore Access Without Sharing Credentials

A CRM access problem can mean one of three things: you cannot authenticate, you can sign in but cannot open the correct account, or you can open the account but a feature is hidden by permissions. Identifying which stage fails helps restore access without weakening security.

First, protect the account

Use only your organization’s approved login URL, reached from a trusted bookmark or known website. Do not send a password, one-time code, backup code, authenticator QR code, or full browser export to support. No legitimate administrator needs your password to adjust access. If the page shows a certificate warning or redirects to an unfamiliar domain, stop and report it.

If you cannot sign in

1. Copy the exact error and take a screenshot that does not expose codes or personal data.
2. Confirm the login email address and check Caps Lock, keyboard layout, and accidental spaces.
3. Use Forgot password once, then check inbox, spam, quarantine, and corporate mail filtering. Do not trigger many reset emails; use the newest approved link.
4. If two-factor authentication is required, verify the device has the correct automatic date and time. Try an already configured backup method if your organization permits it. Never ask another person to forward their code.
5. Test the approved URL in a private window or another supported browser. Ensure cookies are allowed for the login site.
6. If the page is stuck, clear data for that site only, close all its tabs, and retry. HighLevel’s official login guide recommends allowing cookies and clearing affected site data for a page that does not redirect.[1]

If the security code does not arrive, give the administrator your login email, the time of the attempt, delivery method, and masked destination such as the last two phone digits. HighLevel advises users to check spam for an email titled “Login Security Code” and may require an administrator to confirm the user phone number.[1]

If you are in the wrong account, or features are missing

Do not create a second user with a variation of the same email as a workaround. Ask an agency or sub-account administrator to review the existing user. In HighLevel, agency administrators manage users under Agency View → Settings → Users; sub-account access is managed under the relevant Sub-Account → Settings → Users.[2]

Provide the administrator with:

• your login email;
• the exact sub-account or location name;
• the feature or record you need;
• the business task you must complete; and
• how long access is needed.

HighLevel distinguishes Agency users, who can access client accounts broadly, from Account users, who can be limited to selected accounts.[2] Roles and permission scopes can also control available areas, actions, accounts, or assigned data. Request the least access needed rather than full agency access.

For administrators

Check that the person is active, assigned to the correct account, and has the required role and permission scope. Avoid changing the owner account for routine troubleshooting. Confirm identity through an approved channel before changing a login email or 2FA destination. HighLevel supports verification methods including email OTP, SMS OTP, and authenticator-app TOTP depending on the user’s verified methods.[2]

Document who approved the change, what was granted, and whether it should expire. Review access when responsibilities change and remove access promptly when no longer required. HighLevel’s own best practices recommend least privilege and periodic access reviews.[2]

What to send support

Include the approved login URL, login email, error text, screenshot, time and time zone, browser/device, whether private browsing worked, whether password reset or 2FA delivery succeeded, and the required sub-account. Mask phone numbers and never include secrets.

Official references

1. HighLevel: Troubleshooting login issues
2. HighLevel: User Access