Drive overview

Drive stores working files and deliverables for people and agents. A Drive belongs to one Socra Account. Its owner can give other principals in that Account reader or writer access through the Drive API or CLI; the first Drive web app does not manage grants. A Workspace sign-in alone does not grant access to a Drive. Grants do not cross Account boundaries.

Files retain their identity when renamed or moved through the Drive API or CLI. Folders organize files, and immutable versions keep a content history. Drive rejects a content update based on an out-of-date version so one editor cannot silently overwrite another editor's work.

Normal deletion moves an entry to trash, where it can be restored. The current release has no permanent-delete action. Restoring an entry fails if another live entry has taken its name. Restore a trashed parent folder before restoring a child that was individually trashed. To recover older content, download that version and upload it using New version; the older versions remain in history.

Each file is limited to 16 MiB.

Use Drive for files used or produced during work. Use Cortex for adopted knowledge that governs how agents should work.

Start with your first Drive file.