About ignoring files
You may have files which you want to synchronize only occasionally or which you do not want to synchronize at all.
These files can be:
These files can be:
-
Files which your team members don’t need to have
for example temporary files (*.tmp) or log files
-
Very large files which may take some time to synchronize frequently
for example movies or webinar recordings
-
Files which you do not want to share with others
for example confidential files
For each Vault, you can specify the files or file types which must be ignored during synchronization, either permanently or temporarily.
To specify files to ignore for synchronization
-
Click the
button (Windows) or the
button (Mac OS) of your Vault and choose Ignore Files > Manage.
-
Decide whether you want files to be ignored permanently or temporarily (“Quickly ignored files”) Quickly ignored files are files which you can later quickly include or exclude from the synchronization process, simply by selecting or deselecting them from a shortcut menu
-
Permanently ignored files are files which you will never want to synchronize
-
Do one of the following: if you want to ignore a specific file, click 'Browse' and select the file
-
If you want to ignore types of files, type a “pattern” in the text box and click Add.
Example of patterns are: *.tmp, *recover*.*, *.backup.* and *.iso
2. Click OK
To select or deselect temporarily ignored files for synchronization
Once you have specified files or file types as “quick ignores”, you can quickly select or deselect them for synchronization.
-
Do one of the following: in the Notification area of the taskbar (Windows), right-click the Filecloud icon
-
In the menu bar (Mac OS), click the Filecloud icon
-
Choose Quick Ignores and select a Vault. You can now see a list of files or file types:
-
The files without a checkmark will be synchronized.
-
The files with a checkmark will be ignored when the Vault is synchronized.
2. Select or deselect the files which you wish to be ignored during synchronization.
Comments
0 comments
Article is closed for comments.