DriveItem
A file or document in a drive: the rows plnnrly's file browser lists under a project, a customer, the organisation drive or a user's personal drive.
- Summary view
- DriveItemList, 27 fields. What a list returns by default.
- Detail view
- DriveItem, 27 fields. The default for a single read and for every write.
A drive item is the envelope (title, folder, tags, sharing tier), and its body, where it has one, lives on the drive document it points at through content_record. Access is decided per item: the permission for the owner type, then the folders it inherits from, then any per-item grant.
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.
What this item is. Everything created through the API is a document; the other kinds come from uploads in plnnrly.
documentpdfimageaudiovideoofficeother
New values may be added.
Where the item came from: builtin for an editor document, upload for a file uploaded in plnnrly.
builtinupload
New values may be added.
The folder this item sits in; absent for items 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 item lives in. An organisation-owned item renders as a bare {"id": N} reference.
Which form you get depends on owner_type.
projectProjectSummarycustomerCustomerSummaryorganizationRefuserUserSummary
The kind of record content_record points at; it says which branch of content_record applies.
drive_document
New values may be added.
The body this item points at: a drive document for an editor document, null for an item with no body yet. Renders as a bare {"id": N} reference; read the body from GET /api/v2/drive-documents/{drive_document}.
Which form you get depends on content_record_type.
drive_documentRef
Sort position, assigned by the server. Positions count per drive and folder, so the sequence is only meaningful once the collection is narrowed to one drive and one folder. 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.
The user who archived this item; set on delete and cleared on restore.
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 item, after the permission for the owner type, the access inherited from folders and any per-item grant.
viewedit
New values may be added.
When this item was archived, or null while it is live.
Files attached to this item, counting the attachments list in plnnrly, the single uploaded file and the images embedded in the document body.
Variants
DriveItemList 27 fields
What a collection returns, and what ?view=summary returns on a single record.
The same fields as the detail object.
DriveItemSummary 5 fields
The embedded form: what you get when another resource carries this one and you did not include it.
Leaves out: group, kind, source, folder_id, drive_folder, content_record_type, content_record_id, content_record, order_column, created_by, archived_by, inherits_permissions, general_access, access, created_at, updated_at, deleted_at, comments_count, files_count, tags_count, tags, links
owner narrows from Ref or ProjectSummary or CustomerSummary or UserSummary to Ref.
DriveItemLinks 3 fields
The links object on this resource.
Keys: self, comments, files
Polymorphic fields
ownerWhich form you get depends on owner_type.content_recordWhich form you get depends on content_record_type.Something wrong or missing on this page? Tell us