From 3f10fb15382da4042f6ab9eab49e6436a44800f8 Mon Sep 17 00:00:00 2001 From: Liz Kane <68755692+lizkane222@users.noreply.github.com> Date: Mon, 1 Jul 2024 15:20:22 -0700 Subject: [PATCH 1/2] Update index.md Salesforce Auth limitation --- .../destinations/catalog/actions-salesforce/index.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/connections/destinations/catalog/actions-salesforce/index.md b/src/connections/destinations/catalog/actions-salesforce/index.md index 80d03237bb..0977bbd4dd 100644 --- a/src/connections/destinations/catalog/actions-salesforce/index.md +++ b/src/connections/destinations/catalog/actions-salesforce/index.md @@ -36,6 +36,11 @@ Before you connect Segment to Salesforce, please ensure you have a Salesforce ac 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. 7. Enable the destination and configured mappings. +> info "Authenticate with Salesforce" +> 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. +> _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.)._ + + {% include components/actions-fields.html %} ## Configuration options From e3fdac3af8f783c8ff5f0d1d348aa576cd36621d Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 13 Aug 2024 12:49:20 -0400 Subject: [PATCH 2/2] Apply suggestions from code review --- .../destinations/catalog/actions-salesforce/index.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/src/connections/destinations/catalog/actions-salesforce/index.md b/src/connections/destinations/catalog/actions-salesforce/index.md index 0977bbd4dd..1ae50a8827 100644 --- a/src/connections/destinations/catalog/actions-salesforce/index.md +++ b/src/connections/destinations/catalog/actions-salesforce/index.md @@ -36,9 +36,10 @@ Before you connect Segment to Salesforce, please ensure you have a Salesforce ac 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. 7. Enable the destination and configured mappings. -> info "Authenticate with Salesforce" -> 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. -> _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.)._ +> info "Salesforce (Actions) authentication limitations" +> 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. +> +> _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._ {% include components/actions-fields.html %}