Oracle^® Marketing Segmentation Guide > Installing and Administering Segmentation and List Generation > Configuring Marketing Segmentation >

Manage Configuration Settings

This section covers:

• Setting Permissions for Marketing Server Groups
• Verifying Database Privileges for Marketing Segmentation
• Allowing or Disallowing the Populate Privilege

Setting Permissions for Marketing Server Groups

To fine tune the permissions that users and groups have in the Oracle BI repository (that is, the RPD file), use the Administration Tool to update the Permissions. Specify the Web Catalog folders for segments, segment trees, list formats, and filters to which each user or Web group can access.

To provide visibility of Marketing Segmentation functions

1. Specify the users and groups that are allowed to have access to the Segment Designer, Segment, Tree Designer, and List Format Designer.
2. After the users and groups are created, navigate to the Administration - Marketing screen, select Marketing Server Admin, and then select Manage Privileges.
3. In Manage Privileges, designate which users and groups have permission to access and perform each privilege listed.
4. Establish the Web users and groups that must have access to display each BI Catalog folder.
5. In the BI Repository, verify which groups have permission to each Target Level, Segmentation Catalog, and Presentation Column.

To set permissions for Marketing Server Groups

1. Navigate to the Administration - Marketing screen, select Marketing Server Admin, and then select Manage Privileges.
2. In the Access row, allow access by the appropriate groups to the following parts of Marketing Segmentation:
   1. Access Segment Designer
   2. Access Segment Tree Designer
   3. Access List Format Designer
3. In the List Formats row, specify which user groups can perform each action.
4. In the Segmentation row, specify which user groups can perform each action.

Verifying Database Privileges for Marketing Segmentation

The Segmentation and List Generation functions of Marketing Segmentation use writeback capabilities for internal functions such as cache and saved result sets. For security reasons, the administrator can set up a second writable connection pool for the cache and saved result set database and grant login and password database privileges to users.

Contact your database administrator to verify that you have the necessary privileges to create tables and have writeback capabilities to the database.

To verify that write back has been set up properly

1. In Target Levels, in Saved Result Sets, verify that the connection pool used for the physical SQL permits writeback.
2. In Qualified List Items, in Cache Information, verify that the connection pool used for the physical SQL permits writeback.
3. In User/Group Permissions, for Query Limits for the segmentation database, set PopulatePrivilege to Allow.

NOTE:  You do not have to set Populate Privilege to Allow, if you select the Allow populate queries by default check box in the General tab.

Allowing or Disallowing the Populate Privilege

When a criteria block is cached, the Populate stored procedure writes the Cache/Saved Result Set value to the database. You can grant or deny this privilege to particular application roles specific only to Oracle Sales Cloud application users. For the selected application role, this privilege overrides the property Allow populate queries by default for the database object in the Physical layer.

Any Oracle Marketing Segmentation user who writes a cache entry or saves a result set must be a member of an application role that has been assigned the Populate privilege for the target database.

To allow or disallow the Populate privilege

1. Open BI Admin Tool and navigate to Identity Manager-> Application Roles.
2. Choose a specific role -> Properties -> Permissions ->Query Limits tab.
3. For each database object, in the Populate Privilege field, select one of the following options:
   1. Allow: Explicitly grants the Populate privilege for this database. For all Marketing data warehouses, select Allow.
   2. Disallow: Explicitly denies the Populate privilege for this database.
   3. Ignore: Limits are inherited from the parent application role. If there is no limit to inherit, then the Populate privilege is allowed or disallowed based on the property Allow populate queries by default for the database object. Ignore is the default value.
4. Click OK, then click OK again to return to the Identity Manager.