A Google Group can provide membership to a shared drive without every person appearing as a direct member entry. When access is wrong, identify whether the shared-drive manager or group manager controls the relevant change before adding duplicate invitations.
Inspect how membership is supplied
Ask the shared-drive manager to check Manage members for the relevant group address and assigned role. Confirm the user’s exact account address with the group manager where necessary.
A person belonging to several groups can have more than one access path. Removing a direct entry or one group relationship may therefore leave another membership in place.
Match the request to the controller
The shared-drive manager controls the group’s role on that drive. The group’s authorized manager controls who belongs to the group. A group change can affect many resources besides the one shared drive, so describe the intended scope clearly.
For missing navigation, check an original authorized link as well. Google documents conditions where large-group shared drives are hidden by default, so a missing sidebar entry is not by itself proof that membership failed.
Verify without multiplying permissions
After a targeted change, have the person open the intended drive with the correct account and check the required task. Avoid adding an individual Editor or Manager invitation just to work around uncertainty about the group. That can create a second permission path that remains after future group removal. Review limited folders and drive restrictions separately, and document the final access arrangement. When membership ends, verify all relevant paths and remember that revocation does not retrieve independent copies already delivered.
References
Reviewed against the linked official product guidance on November 3, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.