---
schema_version: "1"
id: 3a11cfc6e1ea6195062768ba35b89bd9292bdf37ba7be22e784d8d961f240b35
title: Learn about Internal Analytics Users
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/analytics/264-0-0/bi_help_internal_users.md
canonical_url: https://help.salesforce.com/s/articleView?id=analytics.bi_help_internal_users.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 27f69081e2f7389ed2efc1ef5861cb3c085c240f4110e3e25e21714051fb9c9f
description: Analytics uses internal users, Integration User and Security User, to access Salesforce data, preview data in Data Prep recipes, and enforce row-level security on datasets.
products:
  - CRM Analytics
  - Cross Cloud
release: "264"
---
# Learn about Internal Analytics Users

Analytics uses internal users, Integration User and Security User, to access Salesforce data, preview data in Data Prep recipes, and enforce row-level security on datasets.

Analytics uses the permissions of the Integration User to extract data from Salesforce objects and fields when a dataflow or recipe job runs. Because the Integration User has View All Data access, consider restricting access to particular objects and fields that contain sensitive data. If the dataflow or recipe is configured to extract data from an object or field on which the Integration User does not have permission, the job fails. The Integration User permissions restrict the data extracted from Salesforce only—they don’t affect access to the data in datasets. To restrict user access to data in datasets, set up row-level security.

To enable the interactive preview in recipes, Data Prep uses the Security User. When a user previews the results of a recipe, Data Prep shows only the results that the logged-in user has permission to access. The permissions of the Security User don’t affect the data shown in the preview.

When you query a dataset that has row-level security based on the Salesforce User object, Analytics uses the permissions of the Security User to access the User object and its fields. The Security User must have at least read permission on each User object field included in a predicate. (A predicate is a filter condition that defines row-level security for a dataset.) By default, the Security User has read permission on all standard fields of the User object. If the predicate is based on a custom field, then grant the Security User read access on the field. If the Security User does not have read access on all User object fields included in a predicate expression, an error appears when you try to query the dataset using that predicate.

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

Important Because Analytics requires the Integration User and Security User to access Salesforce data and preview recipe changes to data, do not delete either of these users.

#### See Also

- [Control Access to Salesforce Objects and Fields](https://help.salesforce.com/s/articleView?id=analytics.bi_security_salesforce_object_field_levels_control_access.htm&release=264.0.0&type=5 "CRM Analytics requires access to Salesforce data when extracting the data and also when the data is used as part of row-level security. Configure the permissions of the Integration User on Salesforce objects and fields to control the dataflow’s access to Salesforce data. Configure the permissions of the Security User to enable row-level security based on custom fields of the User object.")
- [Set Up Dataset Security to Control Access to Rows](https://help.salesforce.com/s/articleView?id=analytics.bi_security_datasets_row_level.htm&type=5&language=en_US)