Global Guardrails

Marketeer

  • Can view/create segments, but cannot delete existing segments.
  • Can view XDM Schemas, but can not create or delete them.
  • Can access Customer Journey Analytics (CJA), Destinations, Event Forwarding, XDM Schemas, and Sources. 

OE Admin

  • Can view and edit segments, however recommended to follow due caution before deleting.
  • Can view XDM Schemas, and has the rights to add/extend OE_Custom field group for the schema, but cannot delete them. 
  • Can view and report on license usage and monitoring.
  •  
As per Allianz Global TIE model, each OE gets access to one standard sandbox and all relevant use cases for them will be deployed to this specific sandbox environment. For OEs with multiple domains or sub BUs, we intend to have inner sandbox virtual partitioning to provision privacy and data separation in future. 
OEs are allowed to add additional destinations based on need for use cases. However, they are strongly advised to not delete or alter existing destination without prior alignment with AzTech.
AzTech enables some key data sources during the rollout and onboarding of the OE onto the AEP, like Adobe Analytics, AEP web SDK, and one OE Specific Data Source using the AWS S3 Bucket as data landing zone. Allianz OEs are not initially supposed to manage and integrate additional data sources. However, the expectation here is again to ensure data hygiene on this new platform and not to make this a blocker. With more experience and maturity, the OEs are expected to take over the role for more integrations where needed based on use cases.
To begin with, we intend to rollout pre-defined schemas, that will enable the rollout of pre-planned use cases as the standard onboarding for the OEs. We have also established a Community of Excellence, where the OEs can together decide additions to the default standard schemas, and with more experience and maturity on this new platform we intend to enable the OEs to extend the schemas to meet and deliver their use cases.