How to Pause User Access in GoHighLevel Without Deleting

Reps go on leave, contractors finish a project, a client stops paying and you need to lock their team out until they do. In each case you want to pause user access in GoHighLevel, not delete the person and rebuild them later. HighLevel doesn't have a suspend button, so this guide covers the safe native workaround and how to bring access back exactly as it was.

Why not just delete the user?

Deleting is final, and a user record is attached to a lot: assigned contacts and opportunities, calendar availability, round-robin distribution, conversation history and workflow actions that assign to that person. If the rep is back in three weeks, you'll be recreating their account and their full permission set from memory.

Pausing keeps the user in place, so contact ownership and history stay intact, and the user just can't do anything.

What "pause" means natively

As of October 2026, HighLevel's sub-account users have a role (Admin or User), module permissions (Contacts, Conversations, Opportunities, Calendars, Automation, Marketing, Payments and more) and an Only Assigned Data toggle, all managed in the sub-account's Settings, under Users. There's no deactivate state; a request for one is open on HighLevel's ideas board.

So a pause is a combination of changes you make yourself:

How to pause user access in GoHighLevel

1. Record the current setup. Open the user in Settings, then Users, and screenshot every section of Roles & Permissions, including Only Assigned Data. This is your restore point.
2. Reassign live work if needed. If they own hot leads or open opportunities, reassign them with a smart list filtered by owner and a bulk action.
3. Change their password. This is the step that actually stops them logging in.
4. Switch their role to User if they're an admin, so settings access goes too.
5. Turn off module permissions. Work through each toggle in Roles & Permissions and save.
6. Take them out of distribution. Remove them from round-robin calendars and any workflow step that assigns leads to them.
7. Note the date and reason somewhere your team will see it.

For an agency-level user with access to several sub-accounts, you can also remove the sub-accounts from their access in Agency Settings.

A note on security

If the pause is about trust (a rep leaving for a competitor, a dispute), change the password first and do it immediately. Permission changes help, but the password is what blocks a login.

How to restore access

1. Set a new password and send it to the person securely.
2. Switch the role back if they were an admin.
3. Turn each module permission back on using your screenshots, including Only Assigned Data.
4. Add them back to calendars and round robins.
5. Ask them to log in and confirm they see what they used to.

If another user has an identical setup, HighLevel's Copy Permissions option can copy that configuration back to the returning user, which is quicker than toggling by hand. Otherwise, the screenshots are what make this step accurate.

Pausing a whole team

When a client stops paying, the request is usually "lock everyone out except the owner." The same steps apply, just at scale:

1. Export or screenshot every user's permissions first. Don't skip anyone.
2. Decide who stays active, usually the account owner, so they can still see their data and settle up.
3. Change passwords and turn off permissions for everyone else.
4. Pause any workflows that assign leads or send messages on behalf of paused users.

Keep a short log of who was paused and when. When the account is current again, that log plus the permission records lets you reverse everything in one sitting.

When to delete instead

Pause when the person might return or you're not sure yet. Delete when they're definitely gone and their contacts, opportunities and workflow assignments have been reassigned. Many agencies pause first, wait 30 days and then delete.

Where the native way gets slow

One user is manageable. The pain starts when you need to pause a whole team, for example a client who stopped paying or a seasonal floor that goes quiet in winter. Recording every toggle for ten people, flipping them off and later flipping them back exactly as they were is slow and error-prone. If one screenshot is missing, someone comes back with the wrong access. For setting people up in the first place, see how to bulk add users in GoHighLevel.

How Sub-Account Manager handles it

Sub-Account Manager's user and permission manager turns this into a pause and a restore:

1. Pick the sub-account and select the users to pause.
2. Choose Pause all access. Sub-Account Manager saves each person's current permissions first, then turns everything off.
3. When they're back, restore. Every setting goes back exactly the way it was, from the saved copy, not from memory.

The same screen also changes roles in bulk. It doesn't replace the password step above, so if the pause is about security, change the password too. And if you're onboarding new people at the same time, the bulk user creator creates them with a permissions grid in one pass.