File sharing / PRODUCT DOSSIER

Google Drive

Shared file storage and access management; document editing remains scoped to separate editors.

Investigation: Where should a small team keep shared knowledge? →

Official website ↗Explore in graph →7 cited claims ↓

Google Workspace Drive, including shared drives where enabled; excludes Docs, Sheets and Slides editing engines. · Not established · Google Workspace service terms; applicable agreement depends on account and renewal.Revision 2026-09-15.1 · unreviewedNeeds recheck · recheck 2026-10-150 attestations · checked 2026-09-15

What we do not know yet · 4 open gaps

Which client versions, plan and administrator policies apply to the team?
What survives a representative export: links, attachments, comments, permissions and history?
How do simultaneous edits, temporary disconnection and member departure behave on the chosen setup?
Document editing, offline editing and document revision recovery are not inherited from Google Docs in this Drive dossier.

Applies to: Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use. · Google Workspace Drive, including shared drives where enabled; excludes Docs, Sheets and Slides editing engines.

Applicability, 2 recheck triggers & verification plan

Applicability

Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use.

Google Workspace Drive, including shared drives where enabled; excludes Docs, Sheets and Slides editing engines.

Excludes: Executed collaboration, recovery or migration tests; Unlisted third-party plugins and integrations; AI quality, security certification and performance rankings; Unlisted editions and plan entitlements

Recheck when

Changes to app versions, plan entitlements, sharing policies or license terms.
Changes to offline caching, synchronization, recovery retention or export formats.

Needs recheck · due 2026-10-15

Verification plan

Use the small-team-knowledge investigation to specify the required collaboration and access boundaries.
With explicit authorization, create an isolated synthetic workspace and named test accounts; do not invite real colleagues or upload private knowledge.
Test editing, viewer restrictions, recovery and export with pinned clients and plan; retain sanitized artifacts before drawing conclusions.

Provenance & review

Testedknowhow collaboration research

Commissioned by a Nimbalyst maintainer. Public-source synthesis; no independent review or product execution.

Revision 2026-09-15.1 · unreviewed · checked 2026-09-15

0 attestations · Content: Unlicensed prototype; redistribution decision pending

Capability claims · 7 / 17 sourced

Standing condition: these are documentation claims at the source capture date, with outcome “claimed”; no runtime execution is recorded. Dossier applicability and limitations apply throughout. Expand a row for its statement, specific scope and contradictions. Numbered citations resolve to the source locator and capture date below. Missing evidence means Unknown, not No. Sources are unpinned unless marked “Pinned”; this marks source stability, not stronger support or runtime verification. Reuse counts refer to claims in the full dossier; repeated citations do not represent independent sources.

Yes Documented within scope Partial Limited form of the feature No Explicit evidence of absence Unknown No evidence recorded. These are support assessments, not quality scores or runtime verification.

Collaboration

Shared knowledge spaceYes

Explore Shared knowledge space →

Shared drives retain team files when a contributor leaves.

Scope: Work or school accounts with shared drives enabled.

[2]

Access control

Distinct collaborator rolesYes

Explore Distinct collaborator roles →

Provides distinct shared-drive member roles.

Scope: Manager, content manager, contributor, commenter and viewer privileges differ.

[2]

Per-document accessYes

Explore Per-document access →

Supports file sharing and limited-access folders.

Scope: Parent and drive-level restrictions affect effective access.

[3]

External collaboratorsYes

Explore External collaborators →

Can share files with external people or eligible visitors.

Scope: Administrator and shared-drive policies must permit external sharing.

[3]

Organization

Content searchYes

Explore Content search →

Searches file names and text within supported files.

Scope: Indexed content only; corpus completeness and relevance untested.

[5]

File attachments or storageYes

Explore File attachments or storage →

Stores and shares uploaded files.

Scope: Storage capacity and file limits depend on the chosen plan.

[1]

Continuity & portability

Web publication or public linkYes

Explore Web publication or public link →

Offers public or anyone-with-link file access.

Scope: Account and administrator policy determine available options.

[4]

Unknown · 10 capabilities without evidence

Interface images & local attachments

Screenshots & attachments

Image index

Official project screenshots and your own reference images. Images illustrate a UI; they do not verify feature behavior. Uploads stay in this browser.

No screenshots gathered yet.