> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zentitle2-docs/integrations/salesforce.md).

# Salesforce

<figure><img src="/files/kByK6LVkrCSQ70vEJfHH" alt=""><figcaption></figcaption></figure>

Key to our strategy is integrating Zentitle with Salesforce and other leading CRMs. Zentitle is undergoing several such integration initiatives, and we **are investing heavily in our Salesforce Integrations.**

Our current API allows for effective and easy integration with Salesforce. Our dedicated team is developing multiple products for Salesforce, including an installable package, direct integrations baked into our products, and special solutions for specific use cases.

Here’s a clean version of the **Salesforce integration summary for Zentitle 2**, rewritten without any links:

***

### What the Salesforce Integration Provides

* Zentitle offers a Salesforce integration package that can be installed in your Salesforce environment.
* Salesforce Accounts map directly to Zentitle Customers, with synchronization keeping the records aligned.
* Common license and entitlement tasks can be carried out directly in Salesforce:
  * Create or update a Zentitle Customer from a Salesforce Account.
  * Create or modify entitlements (choosing offering SKUs, seat counts, etc.), which are then provisioned automatically in Zentitle.
  * Edit existing entitlements and sync those changes back to Zentitle.
  * View and manage software activations as part of entitlement records inside Salesforce.
* Synchronization is bidirectional, so updates flow between Salesforce and Zentitle both ways.
* The connection uses Salesforce features such as Named Credentials, External Credentials, and custom headers to securely communicate with the Zentitle API.
* Permissions are managed with a dedicated entitlement admin permission set, so only authorized Salesforce users can perform these operations.
* A sandbox override option prevents unintended API calls in test environments.

***

### Benefits & Value

1. **CRM-centric workflow**\
   Sales, support, and customer success teams can manage licensing and entitlements without leaving Salesforce.
2. **Data consistency**\
   Customer and entitlement data stays synchronized between Salesforce and Zentitle, reducing discrepancies.
3. **Operational efficiency**\
   Entitlement creation and updates can be done as part of normal CRM processes, cutting down on manual steps and errors.
4. **Visibility & auditability**\
   Teams gain insight into licensing and entitlement status within Salesforce, with logs available for troubleshooting.
5. **Security & access control**\
   Secure authentication methods and permission sets ensure only the right users can manage entitlements.
6. **Reduced development overhead**\
   The integration package provides much of the heavy lifting (auth, API calls, mappings) so you don’t need to build a custom solution.

→ [Learn more](/zentitle2-docs/ui-administration/integrations/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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nalpeiron.com/zentitle2-docs/integrations/salesforce.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.