DriveFolder
A folder in a drive: the tree plnnrly's file browser draws under a project, a customer, the organisation drive or a user's personal drive.
- Summary view
- DriveFolderList, 16 fields. What a list returns by default.
- Detail view
- DriveFolder, 16 fields. The default for a single read and for every write.
A folder holds drive items and other folders, and it is where the drive's access rules are anchored: an item or a subfolder that inherits permissions takes them from the nearest ancestor folder that does not.
Used by
Fields
- Detail only
- Only in the detail view.
- Only with include
- Only when you ask for it with include.
- Server-assigned
- Set by plnnrly, never by a request.
The folder this one sits in; absent for folders at the drive root.
The kind of record owner points at; it says which branch of owner applies.
projectcustomerorganizationuser
New values may be added.
The project, customer, organisation or user whose drive this folder lives in. An organisation-owned folder renders as a bare {"id": N} reference.
Which form you get depends on owner_type.
projectProjectSummarycustomerCustomerSummaryorganizationRefuserUserSummary
Sort position within the drive and level, as shown in the drive tree. Positions count per drive and level, so the sequence is only meaningful once the collection is narrowed to one drive and one level. It is not assigned on create, so a folder created through the API stays at 0 until it is positioned in plnnrly; reordering is not exposed in v2.0.
Author; always the authenticated user at create time. Null on legacy rows and where the author has since been deleted.
Baseline sharing tier, consulted only while inherits_permissions is false.
everyone_editeveryone_viewrestricted
New values may be added.
The calling user's effective access level on this folder, after the permission for the owner type, the access inherited from folders and any per-folder grant.
viewedit
New values may be added.
Live drive items directly in this folder that the caller may see. Archived items are not counted, and neither are items in subfolders.
Variants
DriveFolderList 16 fields
What a collection returns, and what ?view=summary returns on a single record.
The same fields as the detail object.
DriveFolderSummary 2 fields
The embedded form: what you get when another resource carries this one and you did not include it.
Leaves out: parent_id, parent_folder, owner_type, owner_id, owner, order, created_by, inherits_permissions, general_access, access, created_at, updated_at, drive_items_count, links
DriveFolderLinks 2 fields
The links object on this resource.
Keys: self, drive_items
Polymorphic fields
ownerWhich form you get depends on owner_type.Something wrong or missing on this page? Tell us