Course · Module 3: Setting the profile up correctly

Lesson 3.3: Ownership, access and control

Transcript

In the last lesson, we found the right profile and got Dave access to it. Now we need to decide who should control it, and who should be able to work on it.

A Business Profile can be managed by more than one person. The owner, staff, an agency or a consultant might all need access. So the question is simple: who gets what?

Google has two access roles for a profile: owner and manager. There can be several owners, but only one of them is the primary owner.

Owners have full control, including adding and removing people. Managers can do most of the everyday work. They can edit the information, reply to reviews and manage posts. What they can't do is add or remove users, or remove the profile.

My principle for agencies is simple. The business should keep control of its own profile. The agency should have the access it needs to do the work.

If manager access is enough for the work you've been hired to do, manager access is enough. Owner access is fine when you genuinely need to manage users. But primary ownership should stay with an account the business controls.

The easiest way to see why is to imagine the relationship ending. Say an agency creates a client's profile using an account only the agency controls, and makes itself the primary owner.

Three years later, the client decides to bring the work in-house. They discover nobody inside the business has proper control, and the person at the agency who set it up left long ago. What should have been a simple change of supplier is now an ownership problem.

Now picture it set up properly. The client owns the profile, and the agency has the access it needs. When the client moves on, you simply remove the agency's access.

The client still controls the profile. The reviews stay, the photos stay, and the posts stay. The business carries on. That's how it should work.

Here's a moment that happens with almost every new client. When we started with Harbour Roofing, Dave offered to send us his Google password so we could sort everything out. We said no thanks.

You never need the client's password. Google's owner and manager roles exist so everyone can use their own Google account. Dave keeps his account. The agency uses its own. Each member of staff uses theirs. If somebody leaves, you remove their access, and nobody else has to change a login.

Remember Harbour Roofing's nephew? He was still the primary owner, so the order mattered. First, he added Dave as an owner.

Google applies a seven-day restriction to new owners and managers. For seven days, they can't remove other users, delete the profile, or take over primary ownership. So we waited a week. Then primary ownership moved to Dave, Dave added our agency as a manager, and the nephew was removed. Now Dave controls his own profile, and we have exactly the access we need.

That order works for any badly set-up profile you inherit. Add the right people first. Let the seven days pass where needed. Fix primary ownership. Then remove access that's no longer required.

If an old agency is still listed, don't remove it until the client is safely in control. Get the right people in first, then tidy up the rest.

Access control should be boring. Every person on the list should have a current reason to be there. No shared passwords, no former employees, no old agencies, and no mystery account holding primary ownership that nobody can reach.

People leave, agencies change and roles change, so review access whenever that happens, and check it every so often anyway. Who is the primary owner? Does the business control that account? And is anyone still listed who shouldn't be?

Here's your task. Find one client where your agency holds the login, or holds primary ownership. Make sure the client has their own owner access, wait out the seven days if you need to, then move primary ownership to them. Keep the access your agency needs, and nothing more.

In the next lesson, we'll look at verification, and why too many changes at once can trigger re-verification. See you there.