This guide contains tasks related to managing shared drives, such as creating shared drives and managing members and permissions.
Create shared drives
To create a new shared drive, use drives.create
.
Java
Python
Node.js
PHP
.NET
Calls to drives.create
are idempotent.
The requestId
parameter identifies the logical attempt to create the shared
drive. If the request times out or returns an indeterminate backend error, the
same request may be repeated. The requestId
and body of the request must
remain the same.
If the shared drive was successfully created on a previous request or as a
result of a retry, the normal response is returned. In some cases, such as
after a prolonged period of time or if the body of the request has changed,
a 409
error may be returned indicating the requestId
must be discarded.
Add or remove shared drive members
Add or remove shared drive members using the
permissions
API.
To add a member, create the permission on the shared drive itself. Permission methods can also be used on individual files within a shared drive to grant members additional privileges or allow non-members to collaborate on specific items.
See Share files and folders for additional details and sample code.
Delete a shared drive
Use the drives.delete
method
to delete a shared drive. All content in the shared drive must be trashed or
deleted prior to deleting the shared drive.
Manage shared drives for domain administrators
Use the useDomainAdminAccess
parameter with the
drives
and
permissions
resources
to manage shared drives across an organization.
Users calling these methods with useDomainAdminAccess=true
must have the
Drive and Docs
administrator privilege.
Administrators can
search for shared drives or
update permissions for shared drives owned by their organization, regardless of
the admin's membership in any given shared drive.
Recover a shared drive that doesn't have an organizer
The following example demonstrates how to use these resources to recover shared drives that no longer have an organizer.