Team Deletion Dependency Check
The following table lists the dependency checks that are performed by Privitar in response to a request to delete a Team from Privitar, together with the advised action to take.
Check | Advised action to take |
|---|---|
First check | The number of related Environments, Rules and Watermark investigations owned by the Team are displayed. You will be asked to delete these objects (Environments, Rules and Watermark investigations) before the Team can be deleted. |
Does the Team own any Environment? | |
Does the Team own any Rules? | |
Are there any outstanding Watermark Investigations? | |
Second check | The number of related Shared Environments are displayed together with the number of PDDs and Jobs that are dependent on this Shared Environment. (The details of each Shared Environment can be downloaded as a CSV file from a Download link.) You will be asked to delete these objects (PDDs and Jobs) before the Team can be deleted. (As the Environment is shared with other Teams it would not need to be deleted.) |
Does the Team own any PDDs? (Shared Environment) | |
Does the Team own any Jobs? (Shared Environment) | |
Third check | All related Schemas and Policies will be displayed. (The details of the Policies and Schemas can be downloaded as a CSV file from a Download link.) If you confirm the Team deletion request, then the Schemas and Policies will be deleted along with the Team. |
Does the Team own any Schemas? | |
Does the Team own any Policies? |