List Builder for Data Cloud Segment Add-Ons and Permissions
Users access List Builder for Data Cloud Segment in their Salesforce org, including Companion org, through supported editions, add-ons, and permissions.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Professional, Starter, and Unlimited Editions |
Required Add-Ons
The products and add-on licenses in your Salesforce org determine whether you have List Builder for Data Cloud Segment. These add-ons are required:
- CDP Data Spaces
- Industry Sales Excellence
- Segmentation and Activation
- Sonic Embedded Store Base
- Customer Data Platform
Required Permissions
List Builder for Data Cloud Segment works with Actionable Segmentation and Data Cloud, so you must assign these permission sets to your users:
- Data Space: Assign this permission set to users so that they can work within their assigned data spaces and use List Builder for Data Cloud Segment.
- Actionable Segmentation: Assign this permission set to the users who set up and use List Builder for Data Cloud Segment.
- Data Cloud: Assign the Data Cloud Architect (formerly known as Data Cloud Admin), Data Pipelines Base User, Data Cloud for Marketing Admin, Data Cloud Activation Manager (formerly known as Data Cloud Marketing Manager) or Data Cloud Activation Specialist (formerly known as Data Cloud Marketing Specialist) permission set based on the requirements of your users. See Data 360 Standard Permission Sets.
- Standard Object Permissions: Enable the Read, Create, Edit, and Delete permissions for the Actionable List, Actionable List Member, and Actionable List Column objects.
- View Setup and Configuration: Assign this permission set to sales and service executives to create and configure actionable lists.
To see what’s included in a permission set, click View Summary on the permission set’s detail page in Setup.
Customizing Permissions
If you customize List Builder for Data Cloud Segment—for example, by adding fields—create a custom permission set. To remove user permissions from the default permission set, create a muting permission set. Then, use permission set groups to assign users the default permission set in addition to your custom permission sets. This approach is an alternative to cloning permission sets and ensures that users always have the latest default permissions.

