When Claude works in your clients' GoHighLevel accounts, "what happened?" needs a clear answer. The Activity log gives you one. It's also designed so that the log doesn't become a second copy of your clients' private data.
What each entry shows
Every request Claude makes, including the ones that were refused, creates an entry with:
- Who asked: the person's name and email.
- Where: the sub-account it ran in.
- What it did, in plain words, and whether it was a read, a change or a bulk change.
- The result: worked, failed, or refused, with the reason.
- How many records were affected.
- The GoHighLevel requests it made behind the scenes, with their status and timing.
- When it happened, and how long it took.
Changes people make on the platform itself, such as choosing a sub-account, appear in the same log.
What it leaves out
Some things should never sit in a log file. Before an entry is saved:
- Passwords, codes and tokens are replaced with "redacted".
- Message text (texts, emails, notes, page HTML and subjects) is stored only as a length, like "182 chars". You can see a message was sent without the log holding what it said.
- Email addresses and phone numbers in the request are partly masked.
- Long values are cut short.
So the log answers "who sent a text to which contact, from which sub-account, and did it work?" without storing the conversation itself.
Finding what you need
On the platform's Activity page, filter by person, by what was done, by result or by date. Refused requests are easy to spot, which helps when someone asks why Claude "didn't do anything".
Exporting
When a client asks for a record, export the filtered view to CSV and send it. It's also a simple way to keep your own archive.
Who can see it
Owners and admins can see the Activity log for their organisation. Members use Claude but don't sign in to the platform, so they can't browse the log.
Why it matters
A good log changes how comfortable people feel about letting an AI work in client accounts. When something unexpected happens, you can find out in a minute who asked for it and what it did, rather than guessing. And because the sensitive parts are left out, keeping the log doesn't create a new privacy risk.
Read more about keeping client sub-accounts safe.
