If you query change logs for multiple corpora, use the includeCorpusRemovals parameter in Changes.list to disambiguate corpus moves from loss of access.įor definitions of different corpora, see Files and folders overview.Įxcept as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. When a file moves between user corpora it may also appear deleted even though the user still retains access to the file. If the item is deleted for all users, it will get marked deleted in all user change logs. However, the file is still available to other users who still have permission to access the file. If a user loses access permission to a file, the change log entry will say deleted. This behavior is the same as non-shared drive items that are shared directly with users. If a non-member is granted file access to individual items in a shared drive,Ĭhanges to those items are tracked in the user change log, not the shared drive change log. Change entry for individual items in a shared drive You should then query the shared drive change log to detect new changes to that item. Change entry after file moves to a shared driveĪfter a file is moved to a shared drive, that shared drive change log continues logging changes for that file, not the user change log. This guide provides more information about individual change log entries and tips for when to track changes in either the user change log or the shared drive change log. The user and shared drive change logs are defined in the Changes and revisions overview.

Google drive file stream changelog