Management API — Members
Management API — Members
Manage the members of a shared folder and their roles. All endpoints require a Management API Key and are scoped to its organization — see the Overview for authentication and error conventions.
Membership is managed only on shared folders you create. The organization folder (whose
membership is maintained automatically) and personal folders reject member operations
with 400.
A member’s role is one of viewer, member, or admin. A folder always keeps at least
one admin: demoting or removing the last admin is rejected with 400.
List organization members
GET /management/members
Lists the distinct users who belong to at least one folder in the organization, across
all folders, in ascending userId order. Use it to discover a user’s userId before
adding them to a folder. This is organization-scoped, not folder-scoped: a user appears
once regardless of how many folders they belong to, and folder association and role are
reported per folder by List members below.
Each member carries its userId plus the email and name resolved from the
organization’s identity provider. When a user’s profile cannot be resolved, email and
name are null and the member is still listed, so no folder member is ever omitted.
nextCursor is the after value to pass to fetch the next page, or null when the
last page has been reached. Keep requesting with it until it comes back null:
List members
GET /management/folders/{folderId}/members
Add a member
POST /management/folders/{folderId}/members
Responds 204. Adding a user who is not in the organization, or who is already a
member, is rejected with 400.
Change a member’s role
PATCH /management/folders/{folderId}/members/{userId}
Responds 204.
Remove a member
DELETE /management/folders/{folderId}/members/{userId}
Responds 204.