Give branch staff access without exposing every location

Start with a responsibility map

List each branch and the people who should edit its hours, answer reviews, or maintain its contact details. Separate someone responsible for one storefront from someone responsible for the entire business group. A job title such as 'manager' does not tell you which Google permission scope is appropriate.

Then open the location list and business-group settings. Identify which profiles are grouped together and which accounts already have group or individual-profile access. An account may receive access through more than one route, so inspecting only the individual branch can miss a broader permission.

Understand the scope before choosing a role

Google's business-group manager role can add, edit, and delete profiles in the group, but it cannot manage the group's other users. An individual-profile manager is a different scope with its own capabilities. The similar names make it easy to grant more access than a branch staff member needs.

Keep an access matrix with the account email, location or group, role, and business reason. It is a practical review tool, not a replacement for checking Google's live settings. Include pending invitations, because an unused group invitation may still be accepted later.

Invite and test at the intended scope

• Confirm whether the person works on one location or every profile in a defined group.
• For one branch, use an appropriate individual-profile invitation instead of defaulting to a business-group role.
• For legitimate group-wide work, have a group owner manage the relevant group permission.
• Ask the recipient to accept through their own Google Account and confirm the correct location list.
• Review overlapping group and profile access before removing an obsolete permission path.

Avoid permission shortcuts during busy periods

Do not share the main owner's login with a branch supervisor or grant group-wide ownership just to correct today's closing time. An authorized owner can make the urgent factual edit while arranging a properly scoped invitation. This keeps emergency maintenance separate from permanent account control.

Do not assume removing someone from a branch removes their group access. Likewise, transferring an individual profile between groups can change who can manage it. Check the business group's member list and the profile's People and access list when location responsibilities change.

Review access when branches change

When a branch opens, closes, is sold, or receives a new supervisor, update the responsibility map and then compare it with the live account settings. Ask the retained owner to confirm that each location still has the intended management continuity and that notifications reach a responsible person.

Measure success by access matching real duties: a branch helper can work on the intended profile, group administrators have a documented reason for broader control, and departed staff have no remaining permission route. Do not judge the access setup by map rankings; it is an operational control task.

Worked example

For example, Pine Laundry operates three branches in one business group. A new supervisor should update only the east branch's hours. The owner uses an individual-profile invitation rather than making the supervisor a manager of the entire group. During the check, an old group invitation to a former supervisor is found and canceled. The new supervisor confirms the intended branch in their own account. The example illustrates permission scope; it does not claim that any particular organization must use one grouping structure.

Questions about this task