# Multi-Organization Access Rights

## Tolerance Correction

| The view of individual objects independent of organizational units is usually generated using structure definitions. If - for example - elements of the item structure are deleted, some organization links may be affected. In order to ensure best performance, this change is usually not tracked in real time within Agile e6. In order to update these changes, a regular (e.g. every night) Agile e6 tolerance correction (batch execution) can be run. A background task checks if the diffusion value in an organizational unit is >0. In this case, an automatic batch execution will be started and the correction run is performed for an organizational unit and all subordinate organizational units. However, it is also possible to execute tolerance corrections for items, documents and folders during the current work session (select Manager > Tools > Correction of PDW Entries).
| The functions triggering diffusion and the diffusion threshold counter settings for a correction process are fully customizable.
| The tolerance value is defined in the EDB-PDW-INS-STR parameter!
| When performing a tolerance correction, the following behaviours should be taken into account: When deleting a structure relation, the primarily/explicit relation (organization driven working relation) is deleted first. The tolerance correction checks all objects that are assigned only implicitly to an organizational unit. If there's no longer a need for the visibility of an object (e.g. due to a changed use case of the object), the implicit relation will be deleted by the tolerance correction (batch process). Only when the implicit relation has been deleted as well, the visibility to superordinate organizational units is deleted. For the reading access the following behaviour is valid: When the structure relation to a primarily organizational unit is deleted, then any explicit relation of this object will be changed into a primarily relation. If there's no explicit relation any longer, then there's no use case as well. In this case the deletion of the use case is not permitted, i.e. only the object itself can be deleted.