Required Permissions for Your Clay User
To connect Clay to Salesforce, your Clay user needs the following permissions:
Access Identity Information: Permission to access identity URL services (e.g., id, profile, email, address, phone).
Manage User Data via APIs: Permission to manage data through APIs.
Perform Requests Anytime: Permission to perform requests at any time (e.g., refresh_token, offline_access).
To establish the initial connection between Clay and Salesforce, you'll need a user with OAuth permissions. Once the connection is made, any user within your Clay workspace can use the integration.
Security Measures
All credentials are encrypted before being stored, and our storage systems are also encrypted. Access to these storage systems is restricted and typically granted only for troubleshooting user issues.
We only collect the minimum necessary information from the integrations you intend to use. All stored information is visible to you within the cell, and we do not save anything else.
Connection Scope and Permissions
The connection to Salesforce is made through OAuth and is scoped to the user who created the connection. If there are sensitive fields or objects you don’t want Clay to access, you can create a permission set that limits the OAuth user's access to those fields.
Data Flows in Clay Pull/Import (Sources or Lookup): Clay can pull data from Salesforce into a Clay Table, either by importing records via the "Import" functionality or making API calls. The data pulled is scoped to the objects and fields accessible to the OAuth user. For example, you can look up a contact by email and use the Contact ID in further columns.
Push/Create or Update: Clay can also push data back to Salesforce, provided the OAuth user has write access. For example, Clay might update the Employee Count field in an Account record from a Clay Table.