---
schema_version: "1"
id: ff07da8db60cff983dc6980b5011c118162e7ef561c2b07a247f63cda5a0d43e
title: Automation Studio Support
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_co_automation_studio_support.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_co_automation_studio_support.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 7cbb1df1d32203d048a0c86e3e8a7311e590396393bba89cdfd60e49de757a49
description: Marketing Cloud Connect supports automated Salesforce sends through Automation Studio in Marketing Cloud Engagement by creating a Salesforce send definition. Next, define an automation with the Send Salesforce Email activity that includes the send definition. After sending, view tracking results in the Sales or Service Cloud.
products:
  - Marketing
  - Cross Cloud
release: "264"
---
# Automation Studio Support

Marketing Cloud Connect supports automated Salesforce sends through Automation Studio in Marketing Cloud Engagement by creating a Salesforce send definition. Next, define an automation with the Send Salesforce Email activity that includes the send definition. After sending, view tracking results in the Sales or Service Cloud.

Automation Studio is an Engagement application used to execute multi-step marketing and data management activities on an immediate, triggered, or scheduled basis. Use Automation Studio's workflow canvas to build simple or multi-step automations.

Using Automation Studio to manage sends to Salesforce reports and campaigns helps maintain a single view of the customer and manage relationships in Salesforce. For example, schedule standard welcome email messages to send to all new customers. Then send a personalized follow-up email to new contacts after a specific interaction. Last, send a notification email to current contacts after a specific event or interaction.

## Data Access Considerations

Manual import activities respect your account configuration for scope by user or non-scope by user. However, automated import activities in Automation Studio do not respect the scope-by-user configuration. The automation runs at the Salesforce tracking user’s level of access, which is typically greater than a regular user's access.

For example, if you manually start an import in Email Studio interactions in the Marketing Cloud, the import respects a scope-by-user configuration. However, if you schedule an automated import using Automation Studio in Marketing Cloud Engagement, the import completes as a non-scope-by-user account configuration.

Consider this data access configuration if you test your imports manually and then schedule the import in Automation Studio. To see actual results while testing, log in to Engagement as the API user to test the import manually. This method provides the same results as the scheduled automation.

You cannot create an import activity using a Salesforce report that you do not have permission to access. For example, reports in the Engagement admin folder in Salesforce are not available for use if you do not have access to that folder.

#### See Also

- [Automation Studio](https://help.salesforce.com/s/articleView?id=mktg.mc_as_automation_studio.htm&language=en_US)
- [Permission-Based Access](https://help.salesforce.com/s/articleView?id=mktg.mc_co_permission_based_accessibility.htm&release=264.0.0&type=5 "If you purchased Marketing Cloud Engagement Licensing after our September 2016 Release, you can access Marketing Cloud Connect functionality. You can access the features when your Marketing Cloud and CRM users are connected: enter a valid username in the Salesforce.com status field on the Marketing Cloud user record.")
- [Marketing Cloud Sends to Campaigns or Reports](https://help.salesforce.com/s/articleView?id=mktg.mc_co_marketing_cloud_sends_to_campaigns_or_reports.htm&release=264.0.0&type=5 "Use this Marketing Cloud Connect for Marketing Cloud Engagement feature to create a Salesforce Send Definition and send to Salesforce campaigns or reports in Engagement. Reports must contain Contact ID, ContactID, Lead ID, or LeadID fields. Store reports in a custom Salesforce folder for sending and ensure that the user who executes the send can access the folder. Marketing Cloud Connect doesn’t support sending to joined reports or reports stored in standard Salesforce folders.")