---
schema_version: "1"
id: e7ccaa7f01b8480a562b3cfa84b84e585019c7cfabd0d53fdae03980da313347
title: Set Sharing Inheritance for a Data Prep Recipe
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/analytics/264-0-0/bi_security_datasets_sharing_apply_to_recipe.md
canonical_url: https://help.salesforce.com/s/articleView?id=analytics.bi_security_datasets_sharing_apply_to_recipe.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 70b2b3289f620f5d57627bd6a3c0490ec59996891d80471543d5d5e5067fce60
description: Specify the sharing inheritance settings when generating a dataset from a Data Prep recipe, then set a default security predicate.
products:
  - CRM Analytics
  - Cross Cloud
release: "264"
---
# Set Sharing Inheritance for a Data Prep Recipe

Specify the sharing inheritance settings when generating a dataset from a Data Prep recipe, then set a default security predicate.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-analytics-bi-264-0-0-production-enus/ec791473-f5b4-4f64-a656-9104f455d966/images/icon_note.png)

Note We recommend that you test in a sandbox environment before rolling out sharing inheritance to production. To make sure that sharing inheritance works for you, test your particular use cases against your Salesforce org’s security model and data to make sure that sharing inheritance works for you.

## Configure Data Prep Recipe

Before a dataset can inherit sharing, you must configure its recipe in Data Prep. Specify which source object to inherit sharing from and the backup security predicate.

1. Enable sharing inheritance for your org and synced objects if you haven’t already. For more information, see [Enable Sharing Inheritance](https://help.salesforce.com/s/articleView?id=analytics.bi_security_datasets_sharing_getting_started.htm&release=264.0.0&type=5 "Turn on sharing inheritance and select the objects to use as a sharing source. Sharing inheritance is on by default in new Salesforce orgs.").
2. Open the recipe in Data Prep. Sharing inheritance isn’t available for recipes built in Data Prep classic.
3. In the output node, configure the sharing inheritance settings. Set which object is the source of sharing rules (1).
    
    ![Output node of data prep recipe calling out sharing source and security predicate.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-analytics-bi-264-0-0-production-enus/ec791473-f5b4-4f64-a656-9104f455d966/bi/images/bi/rn_bi_recipe_output_node_security.png)
4. Optionally, add a security predicate in the Security Predicate field (2). Leaving this field empty is the same as “False,” so users not covered by sharing inheritance have no record visibility. For syntax and more information, see [Add Row-Level Security with a Security Predicate](https://help.salesforce.com/s/articleView?id=analytics.bi_security_datasets_predicate_considerations.htm&release=264.0.0&type=5 "Applying a predicate to a dataset is more than just defining the predicate expression. You must also consider how the predicate depends on the information in the dataset and where to define the predicate expression.").
5. Click **Apply**.

## Configure Datasets

Update the sharing inheritance settings for datasets on the edit dataset page.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-analytics-bi-264-0-0-production-enus/ec791473-f5b4-4f64-a656-9104f455d966/images/icon_note.png)

Note The settings in the dataset and recipe must match. If they don’t, you receive the warning, "The sharing source and security predicate in this dataset version must be the same as in the recipe."

To remove the warning, set the security predicate in the recipe output node and its resulting dataset to false, then rerun the recipe.

1. Edit the dataset. For more information, see [Edit a Dataset](https://help.salesforce.com/s/articleView?id=analytics.bi_dataset_edit.htm&release=264.0.0&type=5 "Edit a dataset to change its name, app, security, or extended metadata (XMD). You can also replace data in a dataset, restore it to a previous version, or delete it. The dataset edit page also provides key information about when the dataset was created and last updated, and where it is used.").
2. Click the pencil under Sharing Source.
    
    ![Enter object name in Sharing Source field on the dataset edit page](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-analytics-bi-264-0-0-production-enus/ec791473-f5b4-4f64-a656-9104f455d966/bi/images/bi/bi_security_edit_dataset_page_sharing.png)
3. Select the object to inherit sharing settings from. Only valid objects are displayed in the list. For example, the primary key of the object must be a field in the dataset.
4. Optionally, click the pencil under Security Predicate. The security predicate is the row visibility fallback when you exceed sharing inheritance limits, described [here](https://help.salesforce.com/s/articleView?id=analytics.bi_security_datasets_sharing_limits.htm&release=264.0.0&type=5 "Here are some things to consider when working with sharing inheritance.").
    1. Add your security predicate in the syntax described in [Add Row-Level Security with a Security Predicate](https://help.salesforce.com/s/articleView?id=analytics.bi_security_datasets_predicate_considerations.htm&release=264.0.0&type=5 "Applying a predicate to a dataset is more than just defining the predicate expression. You must also consider how the predicate depends on the information in the dataset and where to define the predicate expression."). The default on existing datasets is `false`, so users not covered by sharing inheritance have no record visibility.