File Activity Triggers Incremental Scan

Activities that trigger a file to be scanned or re-scanned by Cloudlock

Changes made to a file can include changes in its permission settings. Permission changes included in the list are platform-dependent and typically include changes like the following:

• Changes to Link Sharing settings
• Sharing with additional users and/or groups
• Removing users and/or groups from sharing
• Moving the document to a different location, folder, or to the trash
• Editing the document

A change or update to a files content is not the only thing that can trigger a scan. There are a number of activities that can queue a file up to be scanned (or rescanned) against your policies:

• File Created
• Content modification
• Name change
• ACL modification
• Location change

There are also some events that are not logged in the Activity History that can queue a file up to be rescanned:

• Modification of Parent Folder ACL
• File is "Starred" or favorited/unfavorited