Changes for page Mandantenfähigkeit in acmp

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-Multi tenancy in acmp
	1	+Multi tenancy in ACMP

Content

...	...	@@ -2,15 +2,15 @@
2	2
3	3	= General =
4	4
5		-acmp is designed with multi tenancy and allows for the parallel operation of multiple tenants—separated from one another both organizationally and logically - within a single acmp installation on the same Server. A tenant represents a self-contained environment for managing IT systems and can, for example, represent an entire company, a single department, an organizational unit, or a customer.
	5	+ACMP is designed with multi tenancy and allows for the parallel operation of multiple tenants—separated from one another both organizationally and logically - within a single ACMP installation on the same Server. A tenant represents a self-contained environment for managing IT systems and can, for example, represent an entire company, a single department, an organizational unit, or a customer.
6	6
7	7	This strict separation enables a secure demarcation of data and responsibilities.
8	8
9	9	[[Selecting existing clients when logging in>>image:Mandantenfähigkeit_allgemein.png]]
10	10
11		-= **Multi tenant elements in **acmp =
	11	+= **Multi tenant elements in ACMP** =
12	12
13		-In acmp, not all functions or acmp plugins are automatically in a state of multi tenancy. This means that some elements are either visible exclusively to the tenant administrator, or some elements can be created on a tenant-specific basis.
	13	+In ACMP, not all functions or ACMP plugins are automatically in a state of multi tenancy. This means that some elements are either visible exclusively to the tenant administrator, or some elements can be created on a tenant-specific basis.
14	14
15	15	{{aagon.infobox}}
16	16	Non-multi tenant elements are plugins, solutions, or settings that standard ACMP users cannot view or that are generally hidden from them.
...	...	@@ -22,8 +22,8 @@
22	22	**Non-multi-tenant elements**
23	23	)))
24	24	|(% style="width:583px" %)(((
25		-acmp Kiosk (Kiosk content/appearance)
26		-)))|(% style="width:1109px" %)acmp Update
	25	+ACMP Kiosk (Kiosk content/appearance)
	26	+)))|(% style="width:1109px" %)ACMP Update
27	27	|(% style="width:583px" %)Clients|(% style="width:1109px" %)(((
28	28	License Management
29	29	)))
...	...	@@ -37,8 +37,8 @@
37	37	|(% style="width:583px" %) |(% style="width:1109px" %)Helpdesk
38	38	|(% style="width:583px" %) |(% style="width:1109px" %)Windows Update Management
39	39
40		-All other plugins are global and can be viewed and used by clients who do not have a specific tenant role. However, the visibility and editability of acmp plugins depend less on tenant affiliation and more on the role of the user or group, which is assigned by the tenant administrator.
41		-This distinction means that in acmp, there are two roles a user can assume:
	40	+All other plugins are global and can be viewed and used by clients who do not have a specific tenant role. However, the visibility and editability of ACMP plugins depend less on tenant affiliation and more on the role of the user or group, which is assigned by the tenant administrator.
	41	+This distinction means that in ACMP, there are two roles a user can assume:
42	42
43	43	|Tentant administrator|(((
44	44	A tenant administrator has access to all tenants. They are authorized to create, change, and delete tenants.
...	...	@@ -45,13 +45,13 @@
45	45	They can also view all plugins, whether global or client-specific.
46	46	They are able to assign rights to other users.
47	47	)))
48		-|acmp users without administrator privileges|This user can only log in to the tenant assigned to them by the tenant administrator. They generally have access only to tenant-specific content.
	48	+|ACMP users without administrator privileges|This user can only log in to the tenant assigned to them by the tenant administrator. They generally have access only to tenant-specific content.
49	49
50	50	= **User/Group Role** =
51	51
52		-It is possible to assign rights and roles to a user or an entire tenant group in acmp.
	52	+It is possible to assign rights and roles to a user or an entire tenant group in ACMP.
53	53
54		-However, only a tenant administrator can assign a user’s rights to a group or configure the visibility of various acmp plugins for a user. This means that permissions are assigned via a checkbox to determine which plugins are displayed to the specific user and to which groups they are assigned.
	54	+However, only a tenant administrator can assign a user’s rights to a group or configure the visibility of various ACMP plugins for a user. This means that permissions are assigned via a checkbox to determine which plugins are displayed to the specific user and to which groups they are assigned.
55	55
56	56	These settings are configured under //System > User Management//.
57	57
...	...	@@ -65,12 +65,12 @@
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="HMultitenancy"]] under //System > Settings > //acmp //Server > Multi Tenancy//.
	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//.
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="HExportandimportwithmultitenancy"]].
	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"]].
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.