Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Google Drive mempertahankan histori modifikasi otomatis, yang dapat membantu pengguna melacak perubahan file dan revisi konten. Dalam histori revisi, pengguna dapat melihat hasil edit yang telah dilakukan dan dapat mengembalikan file ke versi tertentu dengan hasil edit tertentu.
Istilah berikut relevan dengan resource perubahan dan revisi
Google Drive API:
Daftar Kontrol Akses (ACL)
Daftar semua resource izin yang terkait dengan file, folder, atau drive bersama.
Ubah
Perubahan yang dilakukan pada konten file atau metadata file atau drive bersama.
Log perubahan pengguna
Catatan semua perubahan yang dilakukan pengguna pada setiap file yang dapat diedit di My
Drive mereka, seperti Google Dokumen, Spreadsheet, atau
Slide. Untuk anggota drive bersama, log perubahan pengguna juga menyertakan entri tentang keanggotaan drive bersama, tingkat akses pengguna ke item di drive bersama tersebut, dan perubahan nama drive bersama.
Log perubahan drive bersama
Catatan semua perubahan pada drive bersama, seperti penambahan atau penghapusan pengguna, dan semua perubahan pada item di drive bersama tersebut. Perubahan pada item dalam drive bersama akan muncul di log perubahan pengguna dan log perubahan drive bersama.
Entri log perubahan
Catatan perubahan yang dilakukan pada konten file atau metadata file atau drive bersama. Entri log perubahan menunjukkan pengguna yang melakukan perubahan, stempel waktu, dan ID. Hanya ada satu entri per file atau drive bersama dalam log perubahan pada satu waktu. Setiap kali file atau drive bersama tersebut berubah, ID baru akan dibuat untuk entri tersebut, dan ID ini akan menggantikan entri sebelumnya.
Revisi
Versi file yang merepresentasikan perubahan pada konten file (bukan metadata). Setiap revisi dapat diakses menggunakan resource revisions dalam Drive API.
Revisi utama
Versi file yang paling baru. headRevisionId dapat diakses menggunakan
resource files dalam
Drive API. headRevisionId hanya tersedia untuk file blob di Drive.
Revisi blob
Versi file biner yang tidak dapat diubah, seperti gambar, video, atau PDF. Jika revisi blob adalah satu-satunya revisi file biner, revisi tersebut tidak dapat dihapus. Blob baru dapat diupload sebagai revisi baru, yang menjadi
revisi utama baru untuk file tersebut.
Revisi file blob apa pun, selain revisi head, yang tidak ditetapkan
sebagai "Simpan Selamanya" dapat dihapus. Revisi yang dapat dihapus biasanya dipertahankan selama 30 hari, tetapi dapat dihapus lebih awal jika file memiliki 100 revisi yang tidak ditetapkan sebagai "Selalu Simpan" dan revisi baru diupload.
Catatan semua revisi file dalam urutan kronologis. Perubahan pada file Dokumen, Spreadsheet, atau Slide akan mendapatkan revisi baru. Setiap kali konten berubah, Drive akan membuat entri histori revisi baru untuk file tersebut. Namun, revisi file editor ini dapat digabungkan, sehingga respons API mungkin tidak menampilkan semua perubahan pada file.
[null,null,["Terakhir diperbarui pada 2025-08-21 UTC."],[],[],null,["# Changes and revisions overview\n\nGoogle Drive maintains an automatic history of modifications, which can help\nusers track file changes and content revisions. In the revision history, users\ncan see what edits have been made and can revert to a specific version of a file\nwith specific edits.\n\nThe following terms are relevant to the changes and revisions resources of the\nGoogle Drive API:\n\n*Access Control List (ACL)*\n: The list of all permission resources associated with a file, folder, or shared\n drive.\n\n*Change*\n: An alteration made to a file's content or metadata of a file or shared drive.\n\n*User change log*\n\n: A record of all changes that a user made to every editable file in their My\n Drive, such as a Google Docs, Sheets, or a\n Slides. For members of a shared drive, the user change log\n also includes entries about shared drive membership, user access levels to\n items in that shared drive, and shared drive name changes.\n\n | **Note:** Even if several users can access the same file, not all changes to that file are reflected in every users' change log. For example, when a user opens the file for the first time, or marks the file as Starred, those changes only appear in that users' change log. As another example, when a file's ACL is changed, it's only reflected in the change log of the following users: The file's owner, any service accounts on the ACL, and any users directly impacted by the ACL change.\n\n*Shared drive change log*\n\n: A record of all changes to a shared drive, such as additions or removals of\n users, and all changes to items on that shared drive. A change to an item\n within a shared drive appears in both the *user change log* and shared drive\n change log.\n\n*Change log entry*\n\n: A record of a change made to a file's content or metadata of a file or shared\n drive. A change log entry indicates the user who made the change, the\n timestamp, and an ID. There can only be one entry per file or shared drive\n in the change log at a time. Each time that file or shared drive changes, a\n new ID is created for that entry, and it replaces the previous entry.\n\n*Revision*\n\n: A version of the file representing a change to the file's contents (not\n metadata). Each revision can be accessed using the [`revisions`](/workspace/drive/api/reference/rest/v3/revisions) resource within the Drive API.\n\n*Head revision*\n\n: The most current version of a file. The `headRevisionId` can be accessed using\n the [`files`](/workspace/drive/api/reference/rest/v3/files) resource within the\n Drive API. The `headRevisionId` is only available for blob files\n in Drive.\n\n*Blob revision*\n\n: A version of an unmodifiable binary file, such as an image, video, or PDF. If\n the blob revision is the only revision of the binary file, it cannot be\n deleted. A new blob can be uploaded as a new *revision* , which becomes the\n new *head revision* of that file.\n\n Any blob file revision, other than the head revision, that's not designated\n as \"Keep Forever\" is purgeable. Purgeable revisions are typically preserved\n for 30 days, but can be purged earlier if a file has 100 revisions that\n aren't designated as \"Keep Forever\" and a new revision is uploaded.\n\n For more information on setting blob revisions as \"Keep Forever\", see\n [Specify revisions to save from auto\n delete](/workspace/drive/api/guides/manage-revisions#specify-revisions).\n\n*Revision history*\n\n: A record of all revisions of a file in chronological order. A change to a\n Docs, Sheets, or Slides file\n gets a new revision. Each time the content changes, Drive\n creates a new revision history entry for that file. However, these editor\n file revisions may be merged together, so the API response might not show\n all changes to a file.\n\nRelated topics\n--------------\n\n- To identify where the change you want to track is recorded, see [Identify\n which change log to track](/workspace/drive/api/guides/about-changelogs).\n- To set up change tracking for users and shared drives, see [Track changes\n for users and shared drives](/workspace/drive/api/guides/about-changes).\n- To download a blob file content revision or to export a Google Workspace document content revision, see [Download and export\n files](/workspace/drive/api/guides/manage-downloads).\n- To publish a revision, see [Manage file\n revisions](/workspace/drive/api/guides/manage-revisions).\n- To set up change notifications, see [Notifications for resource changes](/workspace/drive/api/guides/push)."]]
