When using a tenant hierarchy, document type configurations are maintained in the parent tenant and inherited by one or more sub-tenants. This setup simplifies configuration management, improves security, and allows changes to be tested before being deployed to production.
Changes made to a document type in the parent tenant are not automatically applied to sub-tenants. This is the expected behavior and prevents untested or unintended configuration changes from affecting production environments. After modifying a document type in the parent tenant, you must re-inherit the updated version in each sub-tenant.
Before updating a sub-tenant:
- The document type configuration must be completed in the parent tenant.
- The document type must be visible to sub-tenants.
Updating Document Type
Switch to the target sub-tenant, and open Document Types.
- Click the Live button to deactivate the currently active version of the document type, and change status to Deactivated.
- Locate the updated document type using the Owner column. The updated document type will display the ID of parent tenant. If it is not visible, refresh the page.
- Click the Live button to activate the document type with the parent Tenant ID.
The platform automatically creates a new version of the document type in the sub-tenant using the latest configuration from the parent tenant.