---
schema_version: "1"
id: 2e21e356b34c0cb69ad8a749fdc72f7740a578a547e102b280af552cc830664d
title: Assign Reps to Lightning Sync Configurations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/exchange_sync_admin_config_assign.md
canonical_url: https://help.salesforce.com/s/articleView?id=sales.exchange_sync_admin_config_assign.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 1b2d081ad450a714facc8b45972de0061d5261c8e0115a6b8339a8adfe18bc20
description: After configuring server settings, Salesforce admins can assign reps to a Lightning Sync configuration to get contacts or events to start syncing. Admins can assign individual reps or user profiles to add multiple users to configurations.
products:
  - Sales Cloud
  - Cross Cloud
  - Service Cloud Voice
release: "264"
---
# Assign Reps to Lightning Sync Configurations

After configuring server settings, Salesforce admins can assign reps to a Lightning Sync configuration to get contacts or events to start syncing. Admins can assign individual reps or user profiles to add multiple users to configurations.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available to sync records from: Salesforce Classic, Lightning Experience, and the Salesforce mobile app</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available to set up from: Salesforce Classic and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions with Sales Cloud, Service Cloud, and Lightning Platform</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d151415e81">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d151415e81 ">To view Lightning Sync configurations:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d151415e81 ">View Setup and Configuration</td>

          </tr>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d151415e81 ">To create, edit, or delete Lightning Sync configurations:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d151415e81 ">
              <p>Manage Users</p>
              <p style="margin-bottom:0;">AND</p>
              <p style="margin-bottom:0;">Manage Lightning Sync</p>
            </td>

          </tr>
        </tbody>
      </table>

Before admins assign reps to Lightning Sync configurations, consider how that rep’s records sync if they’re already mentioned in another configuration:

- If you assign an individual user to two Lightning Sync configurations, the user is removed from the first configuration automatically and assigned to the new one.
- If you assign a user to two Lightning Sync configurations as both an individual user and as part of a profile, the user isn’t removed from either configuration. However, the user’s records sync according to the configuration that lists the user individually.
- If you assign a user to one Lightning Sync configuration and one Salesforce for Outlook configuration, the user is not removed from either configuration, but the user’s records will sync according to the Lightning Sync configuration.

Users observe the assignments you’ve created, added, or removed the next time Lightning Sync runs a sync cycle.

To assign a user to a Lightning Sync configuration,

1. From Setup, enter Sync in the Quick Find box, then select **Outlook Integration and Sync** or **Google Integration and Sync**.
2. Click **Let users sync contacts, events, or both between Microsoft Exchange and Salesforce** or **Let users sync contacts, events, or both between Google and Salesforce**.
3. From the Set Sync Settings and Check Status section, click **Go to Config**.
4. If you’re modifying a Lightning Sync configuration, click **Edit** next to the one that you want to modify. Otherwise, click **New Lightning Sync Configuration**, and then complete the required fields.
5. In the Assign Users and Profiles section, select either Profiles or Users in the Search drop-down list.
6. If you don’t see the member you want to add, enter keywords in the search box and click **Find**.
7. Select members from the Available Members box, and click **Add** to add them to the group. If all available users are assigned to this configuration, the Users list is empty and you can only assign profiles.
8. To remove members, select those members and click **Remove**.
9. Click **Save**.

#### See Also

- [How Salesforce Manages Sync Conflicts Between Products](https://help.salesforce.com/s/articleView?id=sales.exchange_sync_sfo_sync_conflict.htm&release=264.0.0&type=5 "Learn how Salesforce manages conflicts when users are assigned to configurations for multiple products such as Einstein Activity Capture, Lightning Sync, and Salesforce for Outlook.")
- [Lightning Sync Considerations for Companies With Multiple Salesforce Organizations](https://help.salesforce.com/s/articleView?id=sales.exchange_sync_admin_config_avoid_sync.htm&release=264.0.0&type=5 "If your company uses multiple Salesforce organizations, review these considerations to avoid sync issues and unsupported configurations.")