---
schema_version: "1"
id: 4e3e0c23048ca85d3f1fbcc7edf1529c042fbcf98df9ce08c4ff17f6cf0e563b
title: Data Prep Access Based on Your User Type
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/analytics/264-0-0/bi_integrate_data_prep_data_security.md
canonical_url: https://help.salesforce.com/s/articleView?id=analytics.bi_integrate_data_prep_data_security.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 9c6fd5b5e2b0031707a75ad7a0df2c4b432923f3b2d82d61eb7a12d027bfa002
description: "Not all Data Prep users in CRM Analytics need access to all data prep features. For example, a business analyst doesn’t need to change dataset security to grant themselves and others access to more data. To support advanced and limited Data Prep user types, CRM Analytics comes with two user permissions: Edit Analytics Dataflows and Edit Dataset Recipes."
products:
  - CRM Analytics
  - Cross Cloud
release: "264"
---
# Data Prep Access Based on Your User Type

Not all Data Prep users in CRM Analytics need access to all data prep features. For example, a business analyst doesn’t need to change dataset security to grant themselves and others access to more data. To support advanced and limited Data Prep user types, CRM Analytics comes with two user permissions: Edit Analytics Dataflows and Edit Dataset Recipes.

To have full access to data prep features, you must be assigned the Edit Analytics Dataflows user permission. Among other things, it enables you to change dataset security on datasets, allowing you to grant yourself and other users access to more Salesforce data in datasets.

If you’re assigned the Edit Dataset Recipes user permission, you have limited access, including:

- When you create a recipe, you can’t use datasets with security predicates as a source for the recipe.
- To prevent you from granting yourself access to rows that you currently don't have permission to see, you can’t add or change security predicates on target datasets.
- You can’t create, edit, run, or schedule recipes that have target datasets defined with security predicates.
- To prevent you from seeing data that you don’t have access to view, you can’t view connected objects on the Data tab or preview them as sources in a recipe.

To understand all differences between the user permissions, check out this table.

  
| Action | Edit Dataset Recipes | Edit Analytics Dataflows |
| --- | --- | --- |
| View, create, edit, and delete local connections. Creating a local connection includes adding connected objects. Editing a local connection includes changing the connected objects, moving objects between local connections, and filtering rows from connected objects. |   | X |
| View, create, edit, and delete output connections. To create an output connection, the org admin must enable the output connection in setup, and you need the Edit Analytics Dataflows and Add Remote Connections user permissions. |   | X |
| Run, schedule, unschedule, and set notifications for data syncs. You can also change the schedule and disconnect an object from a data sync. |   |   |
| Add a local or remote connected object as a source to a recipe. |   | X |
| Write recipe results to a CSV. | X | X |
| Write recipe results to multiple output nodes |   | X |
| Write recipe results to an output connection. You must create the output connection before you can select it in an output node of a recipe. |   | X |
| Sync out—exports local Salesforce data from a connected object to a remote connection. To sync out data, the org admin must enable the output connection in setup, and you need the Edit Analytics Dataflows and Add Remote Connections user permissions. |   | X |
| Preview recipe data from a remote input or output connection in Data Prep. |   | X |
| Add, change, and remove security predicates for datasets that contain Salesforce data. |   | X |
| View, create, edit, delete, run, schedule, unschedule, and set notifications for a dataflow. |   | X |
| View, create, and delete a recipe. | X | X |
| Edit, run, schedule, unschedule, and set notifications for a recipe that writes to a dataset without a security predicate. | X | X |
| Edit, run, schedule, unschedule, and set notifications for a recipe that writes to a dataset with a security predicate. |   | X |
| Monitor a dataflow or recipe job. Download the dataflow error log for the job. If you don’t own the dataflow, you also need the View All Data profile permission to download the error log. |   | X |

#### See Also

- [Set Up Dataset Security to Control Access to Rows](https://help.salesforce.com/s/articleView?id=analytics.bi_security_datasets_row_level.htm&release=264.0.0&type=5 "If a CRM Analytics user has access to a dataset, the user has access to all records in the dataset by default. To restrict access to records, you can implement row-level security on a dataset when you use sharing inheritance and security predicates. Sharing inheritance automatically applies a Salesforce object’s sharing logic to the dataset’s rows. A security predicate is a manually assigned filter condition that defines dataset row access.")