Renaming a shared drive and reorganizing its contents involve different capabilities and risks. Plan the new structure with members, keep important original links, and check limited-access boundaries before moving folders.
Separate the requested changes
Google’s role table gives Managers the ability to rename the shared drive. Content managers have broader within-drive organization capabilities than Contributors, but they do not receive every drive-management action.
Confirm who is authorized to perform each part. A request for a clearer drive name does not require deleting content, changing all membership roles, or creating a replacement drive.
Plan the structure and communication
Record important folders, file links, direct recipients, and any limited-access boundaries. Choose clear names and a simple hierarchy, then tell active collaborators what navigation will change and when.
Use supported rename and move controls for the selected items. Start with a small reviewed set rather than dragging an entire complex hierarchy without checking access.
Verify the resulting project
Confirm original contents, intended locations, and collaborator access. Limited-access folders can affect what ordinary members or content managers can inspect, so involve the Manager when necessary. Large moves may take time to appear consistently; avoid repeating them while processing is unresolved. Keep personal shortcuts and shared originals distinct. A renamed drive does not automatically update every team’s written instructions or application navigation, so correct those references after verifying the new arrangement. Do not remove old-looking items until their purpose, owner context, and migration status are understood, and retain a narrow record of changes for any required correction.
References
- Create a shared drive
- Add files & folders to a shared drive
- Learn about limited access to files and folders in Google Drive
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.