Updates a collaboration. Can be used to change the owner of an item, or to accept collaboration invites. In case of accepting collaboration invite, role is not required.
The access token received from the authorization server in the OAuth 2.0 flow.
The ID of the collaboration.
The level of access granted.
editor, viewer, previewer, uploader, previewer uploader, viewer uploader, co-owner, owner "editor"
Set the status of a pending collaboration invitation,
effectively accepting, or rejecting the invite.
pending, accepted, rejected "accepted"
Update the expiration date for the collaboration. At this date, the collaboration will be automatically removed from the item.
This feature will only work if the Automatically remove invited collaborators: Allow folder owners to extend the expiry date setting has been enabled in the Enterprise Settings of the Admin Console. When the setting is not enabled, collaborations can not have an expiry date and a value for this field will be result in an error.
Additionally, a collaboration can only be given an expiration if it was created after the Automatically remove invited collaborator setting was enabled.
"2019-08-29T23:59:00-07:00"
Determines if the invited users can see the entire parent path to the associated folder. The user will not gain privileges in any parent folder and therefore can not see content the user is not collaborated on.
Be aware that this meaningfully increases the time required to load the
invitee's All Files page. We recommend you limit the number of
collaborations with can_view_path enabled to 1,000 per user.
Only an owner or co-owners can invite collaborators with a can_view_path of
true. Only an owner can update can_view_path on existing collaborations.
can_view_path can only be used for folder collaborations.
When you delete a folder with can_view_path=true, collaborators may still see the parent path.
For instructions on how to remove this, see
Even though a folder invited via can_view_path is deleted, the path remains displayed.
true
Returns an updated collaboration object unless the owner has changed.
Collaborations define access permissions for users and groups to files and folders, similar to access control lists. A collaboration object grants a user or group access to a file or folder with permissions defined by a specific role.
The unique identifier for this collaboration.
"12345678"
The value will always be collaboration.
collaboration "collaboration"
The file or folder to which access is granted. The field is
null when the collaboration status is pending or the
collaboration is created on an app item (see app_item field).
An app_item to which access is granted. The field is null
when the collaboration is created on an item (see item
field), or the app_item is inaccessible. The role cascades
to all items associated with the app_item.
A mini representation of a user, can be returned only when
the status is pending.
The email address used to invite an unregistered collaborator, if they are not a registered user.
The level of access granted.
editor, viewer, previewer, uploader, previewer uploader, viewer uploader, co-owner, owner "editor"
When the collaboration will expire, or null if no expiration
date is set.
"2012-12-26T10:53:43-08:00"
If set to true, collaborators have access to
shared items, but such items won't be visible in the
All Files list. Additionally, collaborators won't
see the path to the root folder for the
shared item.
true
The status of the collaboration invitation. If the status
is pending, login and name return an empty string.
accepted, pending, rejected "accepted"
When the status of the collaboration object changed to
accepted or rejected.
"2012-12-12T10:55:20-08:00"
The user who created the collaboration object.
[
{ "id": 33224412 },
{ "type": "user" },
{ "login": "[email protected]" },
{ "name": "Dylan Smith" }
]When the collaboration object was created.
"2012-12-12T10:53:43-08:00"
When the collaboration object was last modified.
"2012-12-12T10:53:43-08:00"