For more information on multi-tenant object isolation, see the product documentation.
Project Duplication
Only global administrators can perform project applications when multi-tenancy is enabled.
Package Migration
Tenant Administrator
Tenant administrators can perform object migration within the same tenant.
Global Administrator
- Global administrators can perform object migration within the same tenant.
- Global administrators can perform object migration between different tenants. For example, you have a Tenant A and a Tenant B:
- If the package only contains Tenant A project objects, you can move the project objects to Tenant B.
- If the package contains Tenant A project objects and global configuration objects, and the target environment does not have the same GUID configuration in other tenants, you can move the project objects to Tenant B. The configuration objects will be kept global.
- If the package contains Tenant A project objects and Tenant A configuration objects, you can not import the objects to Tenant B. Strategy does not support changing tenant information of configuration objects during migration.
Search and Discovery
- Search results are limited to tenant-scoped objects and shared global objects.
- Tenant users cannot discover or access content that belongs to other tenants.
- Tenant isolation is supported in Global Search in Workstation and Library.
Environmental Level Settings
For multi-tenancy enabled environments, follow role-aware enforcement to control access to global objects and server-level related operations. Role refers to global and tenant users.
- Tenant users and tenant administrators can have related privileges, but privileges alone are not sufficient to authorize sensitive operations.
- By default, operations that impact environment-level settings, global objects, and system objects will be:
- Allowed only for global administrators.
- Rejected for tenant users and administrators, regardless of their assigned privileges.
