Shared Drive Management
Every Shared Drive in one register.
See who owns each drive, who is in it and whether it allows outside sharing, change members in bulk, and schedule archives without losing the trail.
Read the video as text
- Somewhere in your Workspace is a Shared Drive nobody can explain.
- Geeplo puts every Shared Drive in one register.
- Each row shows the owning team, the org unit, how many members it has, your own role, and whether it allows outside sharing.
- Open a drive to change its members, one by one or in bulk.
- Put a Google Group in front of a drive, and access flows through the group.
- When a drive reaches its end, schedule an archive date, or bring it back later.
- And every change you make here is written to the logs tab: what changed, who changed it, when.
- Changes made directly in Google are not captured; this is the trail of what Geeplo did.
- One register, so every drive has an owner and a story.
What it does
The register lists every Shared Drive your Workspace syncs, one row per drive: name, status, the team that owns it, its organizational unit, how many members it has, your own role on it, when it last synced, and its end-of-life and archived dates where they apply. From a row you can open the drive and work its member list: add, change or remove one member, or apply a bulk member change in one pass. Visibility groups let a Google Group stand in front of a drive, so access is granted through the group rather than to individuals. Each drive carries an external sharing stance you can read and change through Geeplo. Archiving is a first-class action: schedule an end-of-life date, cancel it, or unarchive a drive and restore its name in Google. The whole register exports to CSV, and the Logs tab lists what changed, filterable by action, resource, person and date.
Who it's for
Admins who inherit a Workspace where nobody knows which of forty Shared Drives still matter. Team leads who need to prove, for an audit or an offboarding, who could access a drive and when that changed. Anyone merging or winding down drives before a tenant move.
How it works
- Sync and read. The register fills from a sync of your Workspace's Shared Drives; each row carries its owning team and org unit.
- Manage members. Open a drive to add, update or remove members, or apply a bulk change across the list.
- Gate access with visibility groups. Add a Google Group as a visibility group on the drive, so membership flows through the group.
- Set the sharing stance. Read and change whether the drive allows outside sharing.
- Archive on a date. Schedule the end-of-life date, cancel it, or unarchive later; each action writes a log row.
What it doesn't do (yet)
The Logs tab records changes made through Geeplo; edits made directly in the Google Admin console or Drive UI are not captured. Scheduling an archive sets the date and the record; it does not delete or move the drive's content. Moving drives between tenants is Transfer Tool work, and sharing does not come across there either: cross-tenant copies skip permission copy by design. There is no per-drive storage or quota view in this module.
What access it needs
Drive member and permission changes through Geeplo need the Drive scope; member reads use the Directory scopes granted at connection. The scopes page lists every scope Geeplo requests today. See the scopes page.
Questions admins ask
- Can I see who changed a drive's members?
- Yes, for changes made through Geeplo: the Logs tab filters by action, resource, person and date.
- Does archiving delete anything?
- No. It records an end-of-life date; unarchive restores the drive name in Google.
- Can I stop a drive being shared outside?
- Each drive's external sharing stance is readable and changeable through Geeplo.
Related modules
Teams (drive ownership), Transfer Tool (moving drives between tenants), ShareGuard (outside sharing of files). The Teams page is not up yet.