(Re) Configuration of entities - data visibility to users

Re-Configuration of Entities

With the onboarding of more business areas into the software, some restrictions come up with security profiles.

To meet these requirements, the current 'entities' will be renamed and new entities will be configured. 

 User permissions can be set up individually for each entity. The security concept itself is part of another chapter.

Example: Invoices for AMG institutional clients will be in the same entity as Invoices for AMG group clients. 

Each team (group clients and inst clients) can see all data in the instance and filter out what they need to focus on their 'own' work.

Although we separate invoices in different entities, they may share common data (products, invoices, fee types etc).

Current entities	Current users	Target Entity structure	Target user
MEAG AMG	Group clients	AMG_GC_IC	MEAG Group clients MEAG Institutional clients
		AMG_AA	MEAG Alternative Assets
MEAG KAG	Group clients	KAG_GC	MEAG Group clients
		KAG_IC_AA	MEAG Institutional clients MEAG Alternative Assets

We are keeping the concept of data sharing across entities as it does exist today. This will allow that both AMG and KAG can invoice based on the same shared data (example SCD import is available for both AMG and KAG.KAG).

DataGroup Visibilityclient -users Data(User sharingrole  = Invoice manager) can see all data in all instances, regardless whether the data is linked to an agreement or not.

Users

fromAlternativeAssetsInstitutionalClientsrole=SME(subjectexpert).Canonlyviewinvoicesintherelativeinstancestheyhavebeengrantedaccess

	AMGor GC_IC	AMG_AA	KAG(User GC	KAG_IC_AA
AMGmatter GC_IC	-	-	x	-
AMG_AA	-	-	-	-
KAG GC	x	-	-	-
KAG_IC_AA	-	-	-	-

to, 

 

 

	imported via	AMG GC_IC	AMG AA	KAG_IC_AA	KAG Group clients
SCD import Group clients	AMG GC_IC	x			x
SCD Import Inst Clients		x		x

 

 

 

Based on the rule that the group clients team will have access to ALL entities,