> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/fundamentals/announcements/upcoming-salesforce-authentication-changes-for-new-autorabit-guard-connections.md).

# Upcoming Salesforce Authentication Changes for New AutoRABIT Guard Connections

## Overview&#x20;

We're making updates to how AutoRABIT products connect to Salesforce.&#x20;

These changes are part of our ongoing efforts to improve reliability, simplify account management, and create a more consistent experience across AutoRABIT products as a Salesforce partner on AgentExchange.&#x20;

Existing Guard connections will continue to operate normally. This initial rollout only impacts new Salesforce org connections or refreshed sandboxes created after **October 16, 2026**.

## Why am I receiving this notice?&#x20;

AutoRABIT is updating Salesforce connectivity requirements as part of our Salesforce AgentExchange partnership and Salesforce's evolving authentication standards. We're providing advance notice of an upcoming authentication change for new Salesforce org connections or refreshed sandboxes created within AutoRABIT Guard.&#x20;

## What Is Changing?&#x20;

Beginning October 16, new Salesforce org connections and refreshed sandboxes created in AutoRABIT Guard will be established through AutoRABIT's centralized Salesforce authentication service. AutoRABIT's centralized Salesforce authentication service (referred to internally as Auth Hub) provides a consistent and secure way to manage Salesforce connections across AutoRABIT products. Existing connections are not changing as part of this phase. \
&#x20;\
For customers who need to take action, the process will be guided and supported by AutoRABIT. The goal is to make the transition as seamless as possible while preserving your existing configurations and settings.&#x20;

## Why Are We Making This Change?&#x20;

AutoRABIT is expanding its partnership with Salesforce through AgentExchange, Salesforce's ecosystem for trusted partner solutions that integrate with Salesforce environments and AI-powered experiences.&#x20;

As part of this initiative, Salesforce requires participating partners to adopt consistent security, authentication, and connectivity standards. To align with these requirements and provide a more consistent experience across AutoRABIT products, we're updating how Salesforce connections are authenticated and managed.&#x20;

As a Salesforce partner on AgentExchange, AutoRABIT is standardizing Salesforce authentication through a centralized Salesforce authentication service. This phase applies the updated authentication approach to new Salesforce org connections and refreshed sandboxes while preserving existing customer configurations and settings.&#x20;

## What Does This Mean for My Organization?&#x20;

For most customers:&#x20;

* Your existing Salesforce org connections will continue to work normally.&#x20;
* New Salesforce org connections and refreshed sandboxes created after October 16 will use AutoRABIT's centralized Salesforce authentication service&#x20;
* Your project history and settings will be retained.&#x20;
* AutoRABIT will provide guidance if any action is needed from your team.&#x20;

## What Happens When I Create a New Salesforce Org Connection?&#x20;

Beginning October 16, customers creating a new Salesforce org connection or refreshing a sandbox in AutoRABIT Guard will follow an updated authentication process.&#x20;

In most cases, administrators will be guided through the setup experience within the product. Depending on your Salesforce configuration, additional Salesforce authentication and authorization steps may be required during setup. &#x20;

AutoRABIT will provide step-by-step guidance and documentation to help you complete the connection process successfully.&#x20;

For detailed setup instructions, see [AutoRABIT App Installation and Configuration Guide](https://knowledgebase.autorabit.com/product-guides/guard/getting-started-with-guard/autorabit-app-installation-and-configuration-guide).

## &#x20;Do I Need to Do Anything?&#x20;

If you are not creating a new Salesforce org connection or refreshing existing sandboxes, no action is required.&#x20;

If you create a new Salesforce org connection or refresh sandboxes after **October 16, 2026**, you will follow the updated Salesforce authentication setup process. Detailed instructions are available here:  [AutoRABIT App Installation and Configuration Guide](https://knowledgebase.autorabit.com/product-guides/guard/getting-started-with-guard/autorabit-app-installation-and-configuration-guide).

Your Customer Success Manager will also be available to help answer questions and guide you through the process.&#x20;

## When Will This Happen?&#x20;

Customer communications begin immediately. Beginning **October 16, 2026**, all new Salesforce org connections and refreshed sandboxes in AutoRABIT Guard will use AutoRABIT's centralized Salesforce authentication service.&#x20;

## Authentication Across Multiple AutoRABIT Products&#x20;

AutoRABIT is introducing updated Salesforce authentication in phases across Guard, CodeScan, AutoRABIT Vault, and ARM.&#x20;

During this transition, products that have received the update will use AutoRABIT's centralized Salesforce authentication service for new connections and refreshed sandboxes. Products awaiting their rollout will continue using their existing connection methods.&#x20;

Existing connections will continue operating normally. Migration of existing connections will be addressed separately.

## Frequently Asked Questions&#x20;

### Do I need to take action?

No action is required unless you're creating a new Salesforce connection or refreshing a sandbox after the applicable product rollout date.

### What if I use multiple AutoRABIT products?&#x20;

Different products may temporarily use different authentication methods. Follow the connection instructions for each product.&#x20;

### Do I need to migrate existing connections?&#x20;

Not during this initial phase. Additional migration guidance will be provided separately.&#x20;

### Will my existing AutoRABIT setup change?&#x20;

No. Your existing configurations, settings, and historical information will remain intact.&#x20;

### Will users need to be retrained?&#x20;

We do not expect significant changes to normal product usage for most customers.&#x20;

### Will there be downtime?&#x20;

We do not anticipate disruption to normal operations as part of this new process.&#x20;

### Who should I contact if I have questions?&#x20;

Please contact your Customer Success Manager or AutoRABIT Support team.&#x20;

## Need Help?&#x20;

We're committed to making this transition as smooth as possible. If you have questions about how these changes may affect your organization, please contact your Customer Success Manager.&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/fundamentals/announcements/upcoming-salesforce-authentication-changes-for-new-autorabit-guard-connections.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
