About checking in files and binders

If you check in an asset, you automatically check in all files within the asset. (For binders the contents depend on the filters set in the binder's properties.) You have the option of checking in any files located in subfolders of the asset as well (recursive check-in).

The binder filters affect what gets checked in.

When a binder is checked in, the files in the binder are checked against the filters (which are set in the binder's properties). This means that new files that have been added to the binder while it was checked out get added to the checked in binder only if they meet the filter criteria for inclusion.

For example, suppose a file was included, the binder was checked out, and then the filter was changed in a way that would exclude that file. When the binder is checked in, the excluded file would not be in the latest version. The file would still be in earlier versions of the binder in Archive.

In another scenario, suppose a file was added to the binder (in the working folder of the binder on the user's computer) while it was checked out, on check-in the file would be in the new binder version if the filters were set up to include it.

Also, if you check a binder out, change the filter, and then undo the checkout, the binder content AND the filter would be as they were before the check-out.