Changes for page Mandantenfähigkeit in ACMP

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.SV
	1	+XWiki.SF

Content

...	...	@@ -61,16 +61,16 @@
61	61
62	62	= Creating Clients and Tenant Groups =
63	63
64		-To take full advantage of multi tenancy, you must first create [[clients and tenant groups>>doc:ACMP.610.ACMP-Solutions.System.Mandanten.WebHome]].
	64	+To take full advantage of multi tenancy, you must first create [[clients and tenant groups>>url:https://www.deepl.com/bin/view/ACMP/69/ACMP-Solutions/System/Mandanten/]].
65	65
66	66	= Enabling Multi Tenancy =
67	67
68		-Only after you have created these should you enable [[multi tenancy>>doc:ACMP.610.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HMandantenfE4higkeit"]] under //System > Settings > ACMP Server > Multi Tenancy//.
	68	+Only after you have created these should you enable [[multi tenancy>>url:https://www.deepl.com/bin/view/ACMP/69/ACMP-Solutions/System/Einstellungen/ACMP%20Server/#HMandantenfE4higkeit]] under //System > Settings > ACMP Server > Multi Tenancy//.
69	69
70	70	= **Clients and Containers** =
71	71
72	72	After activation of multi tenancy, special rules apply to containers and the clients they contain. A client can only be assigned to containers that belong to the same tenant. Global containers are an exception. Here, all clients can be assigned, regardless of their tenant affiliation. This affects both static and dynamic client assignments, as clients automatically restrict the filter conditions of dynamic containers.
73	73
74		-If a client’s tenant changes, that client is removed from all previous containers, even if a static mapping previously existed. Here, too, the exception applies to global containers. A container’s tenant can only be freely selected at the root level. All child containers automatically inherit the tenant from the parent container, and this inheritance cannot be broken. Please note the special considerations regarding the [[export of containers>>doc:ACMP.610.ACMP-Solutions.Client-Management.Container.Container verwalten.Container importieren und exportieren.WebHome||anchor="HExportundImportbeiMandantenfE4higkeit"]].
	74	+If a client’s tenant changes, that client is removed from all previous containers, even if a static mapping previously existed. Here, too, the exception applies to global containers. A container’s tenant can only be freely selected at the root level. All child containers automatically inherit the tenant from the parent container, and this inheritance cannot be broken. Please note the special considerations regarding the [[export of containers>>url:https://www.deepl.com/bin/view/ACMP/69/ACMP-Solutions/Client-Management/Container/Container%20verwalten/Container%20importieren%20und%20exportieren/#HExportundImportbeiMandantenfE4higkeit]].
75	75
76	76	When executing jobs, a cross-tenant prioritization logic applies. Jobs from global containers are always executed before jobs from tenant-specific containers, regardless of the configured priority. A special rule applies to file repositories, where containers that break the inheritance are considered first. Since a client can only ever be assigned to one tenant, prioritization between different tenants is not necessary.