Skip to content

Commit e3fdac3

Browse files
Apply suggestions from code review
1 parent 3f10fb1 commit e3fdac3

File tree

1 file changed

+4
-3
lines changed
  • src/connections/destinations/catalog/actions-salesforce

1 file changed

+4
-3
lines changed

src/connections/destinations/catalog/actions-salesforce/index.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -36,9 +36,10 @@ Before you connect Segment to Salesforce, please ensure you have a Salesforce ac
3636
6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings). You must select which Event Types and/or Event Names will trigger each mapping.
3737
7. Enable the destination and configured mappings.
3838

39-
> info "Authenticate with Salesforce"
40-
> Salesforce (Actions) requires OAuth based authentication. Salesforce limits the number of apps (destinations) a single user can grant (authorize). A single user can connect five Salesforce destinations, but upon connecting a sixth destination, the oldest destination's authorization is revoked. If the same user reauthorizes that same destination, this same behavior will occur on the next oldest destination that was authorized, and so on. To prevent this behavior, ensure that a different user with the same Salesforce permissions connects any new Salesforce destinations.
41-
> _For additional information on this Salesforce limitation, please see this documentation [Manage OAuth-Enabled Connected Apps Access to Your Data](https://help.salesforce.com/s/articleView?id=sf.remoteaccess_request_manage.htm&type=5#:~:text=NOTE,impact%20your%20org.)._
39+
> info "Salesforce (Actions) authentication limitations"
40+
> You must authenticate with the Salesforce (Actions) destination using OAuth. A single user can connect up to 5 Salesforce destinations, but upon connecting a 6th instance of the Salesforce (Actions) destination, Salesforce revokes the oldest destination's authorization. If the same user reauthorizes that same destination, this same behavior occurs on the next oldest destination that was authorized, and so on. To prevent this behavior, ensure that a different user with the same Salesforce permissions connects any additional Salesforce destinations.
41+
>
42+
> _For additional information on these limitations, see the Salesforce [Manage OAuth-Enabled Connected Apps Access to Your Data](https://help.salesforce.com/s/articleView?id=sf.remoteaccess_request_manage.htm&type=5#:~:text=Each%20connected%20app%20allows%20five%20unique%20approvals%20per%20user.){:target="_blank”} documentation._
4243
4344

4445
{% include components/actions-fields.html %}

0 commit comments

Comments
 (0)