There are two types of refile operations:

• Metadata: Affects only the metadata fields eligible for refile. During a metadata refile, these custom fields are aligned with the parent container. Refiling metadata ensures that users can easily retrieve content through searches. 

  NOTE:

  • Except for class and subclass, all the metadata fields are copied from the workspace. Class and subclass are copied from the immediate parent folder.
  • When changing workspace or folder metadata, the metadata refile operation updates all eligible metadata fields on an object when a metadata event is triggered. Therefore, each refile eligible metadata field is updated, including fields that might not have changed. For example, if a change is made to metadata field custom3 for a workspace, all refile eligible fields (potentially custom1 through custom30) for a document could be updated. This results in the document's metadata fields aligning with the metadata values for the workspace.

• Security: Affects the default security and the list of users/groups with permissions to access the item. During a security refile, the security of ‌the item is aligned with the parent container. Refiling security ensures that only ‌authorized teams or users can view and access the item. Security is refiled for items in the folders that inherit security.

  For additional information about interactions between Refile Service and Bulk Security Updates, refer to Considerations when using the Refile Service for security updates.

Each refile type is an independent event and only affects that one type. For example, a security refile only affects security-related fields and never modifies metadata. The events are enabled separately.