---
title: "Integrity Manager"
canonical: "https://help.agiloft.com/space/HELP/43719600/Integrity+Manager"
format: markdown
---
The integrity manager (IM) is a feature in Agiloft that lists dependencies that might be affected if you modify or delete an object. It appears if you attempt to delete data that is used elsewhere in your KB, and can also be triggered manually for fields, actions, and saved searches.

# Manual Checking

You can preemptively check dependencies for fields and actions in the table wizard.

To check the dependencies for a field:

1. Go to Setup [Table] and open the Fields tab.
2. Select one field from the list.
3. Click Check Dependencies.

To check the dependencies for an action:

1. Go to Setup [Table] and open the Actions tab.
2. Select one action from the list.
3. Click Check Dependencies.

To check the dependencies for a saved search:

1. Go to the table, click the saved search drop-down, and click Manage.
2. Select one saved search from the list.
3. Click Check Dependencies.

# Deleting Objects

The integrity manager can be triggered by deleting fields, columns, rules, actions, tables, email templates, reports, searches, views, permissions, and other objects. In short, the integrity manager will trigger any time you attempt to delete something that relates to another part of the KB.

> ⚠️ Some objects in your KB are considered system objects and cannot be deleted even by changing the Deletable value to Yes. An example is the ID field for the Contract table. When you try to delete a system object, you receive a warning instead of being directed to the Integrity Manager.

When you attempt to delete an object with dependencies, the KB automatically checks the object against a dependencies graph, and then opens the Ensure Data Integrity window. This window might include some or all of the following tabs, depending on the object being deleted:

- Cannot delete: This tab shows the dependencies that currently have a Deletable value of No. If you want to proceed with deleting the object, you need to modify the dependent objects to have a Deletable value of Yes, and then delete these objects.
- Data in use: This tab shows the dependencies that need to be deleted before the object you are attempting to delete can be deleted.
- Unlink: This tab shows you all the dependencies that will automatically unlink from the object you are attempting to delete after that object is deleted. You don't have to delete any of these objects, but it may be a good idea to check them after removing the object.
- Other: This tab shows you any other dependencies that don't fall under the other tabs.

Each of the tabs shows a bullet list of tips for addressing the dependencies.