Multi-Tenancy Considerations

Consider the following information when using CACF in a multi-tenancy environment:

Managed attributes, verification policies, Change Orders, and change specifications are tenanted.
Tenants up their hierarchy can view all CACF objects.
For example, if a tenant creates a managed attribute, this action may block a tenant in the hierarchy from creating a duplicate managed attribute. The hierarchy requires unique policy sequence numbers.
To determine the policy that manages a change to an attribute, consider only policies from the tenant hierarchy of the object (CI).
A subtenant can create a policy that overrides the supertenant by assigning a lower sequence number to their local policy.
CACF only considers policies at the tenant level and its parents in the hierarchy.
CACF does not consider the tenant of that contact that performs the change.
Note: Verification policies are specific to your system and do not vary by user or role.