Audit Who Can Touch the Account
Command note: every account you inherit has more people in it than the client remembers.
Access is the one audit nobody schedules. Old staff, a former agency, a contractor from a project that ended two years ago — they keep working logins until somebody looks.
The command I run on every sub-account:
"List every user on this sub-account with their role and permissions. Then show me which of them are assigned to contacts, opportunities or calendars, and which appear in any workflow's internal notification step."
What usually comes back:
• Users nobody has thought about in a year
• Admins who only ever needed read access
• Notifications routed to someone who left
• A calendar owned by a person who no longer takes calls
Do it now:
1) Pull the user list and read it with the client, name by name
2) Ask one question per person: does this person still need to be in here today?
3) Reassign before you remove — contacts, opportunities and calendars follow the user
4) Fix every workflow notification pointing at anyone who is leaving
5) Note the date in the account and repeat it quarterly
Removing a user takes five minutes. Explaining to a client why a stranger still had admin on their CRM is a very different conversation.
An account is only as private as its longest-forgotten login.
0
0 comments
Jerry Relth
3
Audit Who Can Touch the Account
powered by
GHL Command
skool.com/ghl-command-5986
The AI operator's room for GoHighLevel agencies.
Build your own community
Bring people together around your passion and get paid.
Powered by