> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/connectors-and-triggers/connectors/enterprise-applications/salesforce/authtoken-reuse-salesforce.md).
# AuthToken Reuse for Salesforce connector
Learn how to configure the Salesforce connector to enable token reuse on the Digibee Platform.
This documentation teaches you how to perform the necessary configurations to enable token reuse when using the Salesforce connector in the Digibee Integration Platform.
## How to enable the AuthToken reuse
1. Login to the [Salesforce portal](https://login.salesforce.com/?locale=us).
2. Click on **Apps** at the menu on the left side of the screen.
3. Click on **App Manager**.
4. Search for the name of the latest token generated at the Digibee Integration Platform.
5. Click on the arrow down on the right side of the token infos and click at **Edit** option.
6. Mark the option **Introspect All Tokens**.
7. Click on the **Save** button at the end of the page.
To learn more about how the Salesforce connector works, read the [documentation](/documentation/connectors-and-triggers/connectors/enterprise-applications/salesforce.md).
---
# 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://docs.digibee.com/documentation/connectors-and-triggers/connectors/enterprise-applications/salesforce/authtoken-reuse-salesforce.md?ask=&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.
.gif)