Skip to content
My GoHighLevel MCP
Security

Switch off the tools you don't need, and turn off deletes in one click

Claude can do a lot in GoHighLevel. The Tools and permissions page lets you narrow that down to what your team actually uses.

Product team

3 min read

Claude can work with contacts, pipelines, calendars, conversations, workflows, websites, forms, courses, products and more. Every one of those abilities is included in your plan. But "can" isn't the same as "should": most teams only need a part of it, and a smaller set of abilities is easier to reason about.

The Tools and permissions page on the platform lets an admin decide.

Turn off anything that deletes

At the top of the page is a single switch: hide every tool that deletes or removes things in GoHighLevel.

With it on, Claude simply can't delete a contact, an opportunity, a workflow, a page or anything else. If someone asks, Claude explains that deletes are switched off for your organisation, and the refused request appears in the Activity log.

This is a good default for many agencies. Deleting things is rare, and when it's needed, an admin can switch it back on for a moment or do it in GoHighLevel directly.

Turn off individual abilities

Below the switch is the full list, in plain words, grouped by area: contacts, calendars, workflows, websites and so on. Search for what you're looking for and turn off anything you don't want Claude to use.

Some examples we see often:

  • Sending messages switched off for an organisation that only uses Claude for reporting.
  • Website publishing switched off for everyone except the web team's organisation.
  • Course and membership abilities switched off for agencies that don't sell courses.

A switched-off ability disappears from what Claude can use in your organisation. There's nothing for someone to talk it into.

What can't be switched off

A few basics always stay on, because without them nobody could sign in to GoHighLevel, pick a sub-account, or find out what is paid for. They don't change anything in your clients' accounts.

Checks that stay on regardless

These switches sit on top of the protections that are always there:

  • Claude only reaches sub-accounts your organisation has chosen and paid for (or your trial sub-account).
  • Each person uses their own GoHighLevel login, so GoHighLevel's own permissions apply.
  • Claude is instructed to confirm before sending messages, deleting, or changing many records.
  • Every request is recorded in the Activity log.

A simple starting point

  1. Turn on "hide every tool that deletes".
  2. Turn off the areas you know you won't use.
  3. After two weeks, look at the Activity log for refused requests. If people keep asking for something you switched off, maybe it's worth turning back on.

Control that fits the way you work is better than an all-or-nothing choice.

  • #permissions
  • #settings

Written by

Product team

Guides and product news

The people who build My GoHighLevel MCP. We write practical guides for agencies and businesses running GoHighLevel from Claude, and we keep them up to date as the product changes.

More from Product team →

Keep reading

All articles →