Basic automated procedure

Data domain segmentation in Service Management is intended to work after setup with minimal manual maintenance. The examples in these steps come from Data domain segmentation – use case.

1. Edit the out-of-the-box Data domains list in the Lists Management module with the data domains required for your organization. For more information, see Lists.

   By default, all Service Management tenants come with a single data domain called Public. For this use case, a data domain called Database is created.

2. Configure all relevant group and person forms to include the Primary domain field. For more information, see How to edit a form.

   For this use case, a Primary domain field is added to the DBA team group.

3. Assign a primary domain to groups and users, as required. For more information, see How to assign a Primary data domain to a group or user.

   For this use case, the DBA team group is assigned the Database domain.

4. Assign permissions for a primary domain to roles. For more information, see How to assign permission for a data domain to a role.

   Since the people with the VP Engineering role also need to view database requests, the VP Engineering role is assigned the permission for the Database domain.

5. If necessary, manually assign permission to people outside a particular group to access a data domain.

6. (Optional) Create business rules to add or remove data domains. For more information, see How to assign a record to a data domain.

Related topics

• Data domain segmentation
• Data domain segmentation – use case