Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Contact Us
  • Home
  • Migrations
  • Migration Jobs
  • Job Behaviors

Change Item Inspection Policy

Learn how to control the tracking level of content that exists on both the source and destination.

Written by Andrea Harvey

Updated at June 17th, 2025

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Insights
    Prebuilt Insights Custom Insights
  • Content
  • Accounts
  • Activity Log
  • Content Scans
  • Migrations
    Migration Jobs Migration Reports Maps Flagged Items Migration Tools
  • Connections
    Supported Platform Connections Creating Connections Connection Maintenance Connection Pools
  • Entity Types
    DryvIQ Available Entity Types Custom Entity Types Entity Type Maintenance
  • Action Sets
    Creating Action Sets Action Sets Maintenance
  • Settings
    License Performance Notifications Extensions Entity Types Settings Display Settings Configuration
  • API, CLI, and SDK Documentation
    REST API Documentation Command-line Interface SDK Development
  • POC Offering
  • Release Notes
+ More

Table of Contents

Overview None Filtered Shared All

Overview

The Item Inspection Policy enables you to control the level of tracking and reporting for content that exists on both the source and destination platforms, including content that has been configured to be excluded from transfer and content that already existed on the destination prior to the initial transfer. This feature categorizes items for reports on the job Validation tab. All job types and transfer directions support validation. 

By default, the Change item inspection policy toggle is turned off. With this setting, the job will use the default inspection policy of None. Enabling the inspection policy toggle allows you to set the policy to Filtered, Shared, or All. See below for more information about each inspection policy. 

If the connection does not have access to a given folder in a hierarchy, DryvIQ cannot track and report the items.

 

None

This inspection policy will not track all items but will offer additional tracking with performance in mind. It tracks all items on the source, except for filtered items (items ignored or skipped based on the job filters). All existing content in the Destination root is tracked as destination-only items and reported as ignored. For sync jobs, the destination will behave like the source.

Filtered

This inspection policy tracks only items on the source that are excluded from transfer based on the job filters. Content on the destination is not tracked for jobs that migrate in one direction from source to destination. For sync jobs, the destination will behave like the source.

Shared

This inspection policy tracks only shared items on the source. Filtered content configured to be skipped or ignored based on job filters will be tracked if it has been shared. Content on the destination is not tracked for jobs that migrate in one direction from source to destination. For sync jobs, the destination will behave like the source.

All

This inspection policy tracks all content on both the source and destination, including filtered items and items that existed on the destination before the initial transfer.

An inspection policy to track only flagged items can be set through the REST API. See Item Inspection Policy Using REST API for more information about this policy.  

 
inspection policy item tracking

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Item Inspection Policy Using REST API
  • Preserve File Versioning Between Locations
  • Allow Unsupported File Names to be Changed
  • Allow Truncation

Copyright 2025 – DryvIQ, Inc.

Knowledge Base Software powered by Helpjuice

Expand