Version History on My Drive
S
Selected Crane
The file folder is helpful in which to store docs to link, but it appears the system does not offer version control. The system does allow replacing the doc, but the prior doc is not viewable. For continuity, the system should provide, store and be able to view prior documents for auditing purposes; now we have to utilize an external system to store information within those files for documentation purposes.
Log In
K
Kavya
Hi Selected Crane,
Thank you for sharing this request.
To better understand the requirement and the expected version-control workflow, could you please clarify a few points?
What types of documents are you typically storing in the Drive and linking to articles?
How frequently are these files updated or replaced?
Do you need to retain every previous version, or only the most recent few versions?
What information should be available for each version (e.g., version number, uploaded by, date, change notes)?
Should users be able to view and download previous versions, or is maintaining them only for audit purposes sufficient?
Who needs access to previous versions — admins/editors only, or readers as well?
Is the primary use case audit/compliance, tracking changes, or recovering/restoring an earlier version?
Approximately how many files would require version history?
How are you currently managing these previous versions in the external system, and what limitations are you facing with that approach?
This will help us understand the required versioning and retention model.