Grouping and Entitlement Approach

The alignment of staff to one or more segments of control is not a cookie cutter process. Within Communication Management; however, there are some broad grouping and entitlement approaches that can be used as a starting point to consider how to align Entitlements to enable Users with the appropriate rights.

The Financial Services Cloud Entitlements provides the necessary details on how Transaction Groups associated to User Groups create Entitlements. One way of looking at this is to consider a Transaction Group to define the capabilities that can be assigned to one or more User Groups.

Users who are responsible for creating or editing Content are entitled to create, edit, read, and potentially delete Content Configuration items. Only a limited number of Users should be entitled to perform deletes. The Content creators can apply styling to the content, but they are entitled to use only existing Styles created by brand designers to ensure compliance. Brand designers may only be allowed to create, read, update, and delete Styles, but they would have no access to Content Configuration. Brand designers are granted Assembly entitlements that allow them to create an assembly of content built by others, to view and confirm the final output.

An approach that provides flexibility is to align Transaction Groups to Configuration items and Assembly. These groups can then be associated to the User Groups as needed, based on the distribution of responsibility. Separating the Delete Transaction Types gives a higher level of control.

Group all Package-related, Document-related, Layout-related transactions to enable proper level of control across User groups.

Example Grouping

Each of these groups would be assigned to a Transaction Group containing transactions that enable them to do the required activities. See Transaction Type Listing topic to identify the appropriate Transaction Types.

User Groups:

Content Contributors: Legal, compliance, graphic artists, and other subject matter experts who contribute text or graphics for use in output
Content Creators: Staff responsible for the creation and management of text and graphic content
Layout Designers: Staff responsible for the way content should be laid out within document containers for presentation in HTML.
Stylists: Staff responsible for defining styling that meets corporate branding requirements and ensures output readability
Document Owners: Product managers, marketers and other staff responsible for defining the communications
Package Designers: Product managers and other staff who are responsible for grouping communications documents into logical packages that can be assembled based on client system needs
Assemblers: Testers, external systems and other entities that need to create instances of outgoing communication

Environment

Each Financial Services Cloud customer receives a non-production, pre-production and production tenancy. The Transaction Groups and users listed above may be used in the non-production environment where Configuration is built.

The number and variety of User and Transaction Groups and subsequent Entitlements is different in pre-production and production.

In Pre-production, Configuration creation, deletion, or updating does not occur and the environment is primarily used for Assembly by QA testers and test systems.
In Production, only authorized Users and authorized Client Systems are allowed access and only to Assembly functions.

Automation

Transaction Type, Transaction Group, User Group and Entitlement configuration can be done using the user interface. These configurations can also be done in bulk through automation using APIs. Oracle Consulting and trained Partners can assist organizations by automating configuration through spreadsheets or other methods.