---
schema_version: "1"
id: e9390f8f024d624225b2307d567c5190955b897e746f14712161a47d31a06a74
title: Account Configuration for User Data Access
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_co_account_configuration_for_user_data_access.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_co_account_configuration_for_user_data_access.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: b41c6a5c7cb779460bf14fe7a8d9afa9b0cfdcc0146095fd400ae0c01227be23
description: Marketing Cloud Engagement administrator and Sales or Service Cloud administrator review these options for configuring Marketing Cloud Connect data. Choose to set the account as scope by user or non-scope by user.
products:
  - Marketing
  - Cross Cloud
release: "264"
---
# Account Configuration for User Data Access

Marketing Cloud Engagement administrator and Sales or Service Cloud administrator review these options for configuring Marketing Cloud Connect data. Choose to set the account as scope by user or non-scope by user.

These options for Marketing Cloud Connect set the level of data access for your users.

- Non-scope by user
- Scope by user

Understanding the important differences between the two account configuration options is critical to determining how you want Marketing Cloud Connect to be used after installation. This option is selected during the Marketing Cloud Connect configuration process and can be altered in the Engagement Email Studio Setup, under Platform Tools > Apps > Salesforce Integration at any time.

## Option 1: Non-Scope by User

This option configures data access on the Salesforce system user, typically an administrator. Choose this option to allow Marketing Cloud Connect users to send to all subscribers in a report or campaign that the Salesforce system user can access. Subscribers aren’t filtered based on the user running the report.

Examples:

- You create a report based on My Contacts, but the Salesforce system user can’t access the contacts in that report. The report is empty and so you can’t send to My Contacts. You don’t receive an error message, but the subsequent email-send report shows “0” contacts sent.
- You can access an existing report containing records shared with other users. You see only your own records on that report. If you send to that report intending only to send to the records you see, you can inadvertently send to other shared records.

Considerations:

- Within Engagement, report or campaign lists aren’t limited to what is visible to the user initiating the send.
- Within Engagement, returned subscribers aren’t limited to what is visible to the user initiating the send.
- Password policies aren’t in effect, making this configuration easy to maintain because passwords don’t expire.
- An administrator can set up a user without entering a password.
- You can mistakenly send to report or campaign members who aren’t visible to that user without notice.
- This send behavior is the default for v2 accounts, so this option is favorable for existing v2 customers migrating to Marketing Cloud Connect.

## Option 2: Scope by User

This option configures data access on the Marketing Cloud Connect user initiating the send. Reports and campaigns that are visible to the user are available for selection as a target audience for sending. The list of subscribers returned is limited to what the user initiating the send has access to view.

## Implications on Salesforce Data Extension Import Activities

Import Salesforce data extensions into Engagement through Interactions. Create import activities only with Sales or Service Cloud reports you can access. For example, reports in the Engagement Admin folder in Sales or Service Cloud aren’t available for use if you can’t access it in Engagement.

Manual and automated imports behave differently in Scope by User accounts:

- Scope by User doesn't affect the configured backend processes for data and objects returned by Salesforce Data Event, Sales and Service Cloud Activities in Journey Builder, and Synchronized Data Sources.
- Manual import activities respect scoping, so the number of records that appear in the report are specific to the user who is running the import.
- All automated import activities are executed as the Engagement API user. Therefore, the number of records reflects the Salesforce system user’s level of access to data.

With non-scope by user accounts, imports return results based on the Salesforce system user’s data access.

![Review Prerequisites and Install Package - Step 3](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_cross-cloud_products-264-0-0-production-enus/bd617332-480f-48e8-b283-3477883c1320/mc_cross-cloud_products/images/connect---1-3-prereqs.png)