> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/integrations-overview/setup-salto.md).

# How to Connect Salto Space and Peoplevine

The Salto Space integration uses Peoplevine-generated credentials that you paste into a Salto **alarm event** with a **web request action**. Salto then pushes keycard taps back to Peoplevine as automatic check-ins.

This article covers the **Peoplevine Control Panel side** of the integration. Salto-side configuration (alarm event, web request action, **SHOW\_EXT\_ID** parameter) lives in Peoplevine Connect — links are provided in each step.

> Setting up VIZpin instead? See: [How to Connect VIZpin and Peoplevine](/products/integrations-overview/setup-vizpin.md). Building a custom or non-standard access-control integration? Use the [Access Control Integration with Peoplevine](https://docs.peoplevine.com/peoplevine-docs/peoplevine-connect) partner guide in Connect.

### Before you begin (Prerequisites)

* **Permissions**: You must be an **Administrator** or **Supervisor**. See: [How to Manage Users and Permissions](/products/control-panel-overview/admin-overview/manage-roles-permissions.md).
* **Peoplevine Control Panel** access.
* A Peoplevine **business location** to associate with the connection.
* **Salto Space version 6.10.4.3 or higher**.
* Access to Salto Space with permission to create alarm events and modify system options.
* For full Salto-side prerequisites and walkthrough, see the [Connect Salto Space and Peoplevine](https://docs.peoplevine.com/peoplevine-docs/peoplevine-connect) guide.

***

### Setup

#### 1. Generate the Peoplevine credentials

1. Navigate to [**AUTOMATE > Integrated Platforms**](https://control.peoplevine.com/admin_authenticate.aspx).

   > **Note (Pro Dash):** Same path — **AUTOMATE > Integrated Platforms**.
2. Under **Access Control**, select **Salto**.
3. Select the location you want to associate with this Salto connection, or create a new one.
4. Click **GENERATE CREDENTIALS**.
5. Review the generated **Post to URL** and **Body** values — you will paste these into Salto Space.
6. Click **OK**, then click **SAVE** to activate the connection.

#### 2. Paste credentials into Salto Space

In Salto Space, create the alarm event with a web request action and paste the **Post to URL** into the Salto **URL** field and the **Body** value into the Salto **Body** field.

For the full Salto-side walkthrough — alarm event creation, **Trigger Type = Audit trail event**, **WHO / WHERE / WHAT** configuration, and the **SHOW\_EXT\_ID** parameter — follow the [Connect Salto Space and Peoplevine](https://docs.peoplevine.com/peoplevine-docs/peoplevine-connect) guide.

#### 3. Map Salto users to Peoplevine members

Choose one of these two options to link Salto keycards to Peoplevine members:

* **Option A — You already use EXT ID for another purpose:** Copy the existing **EXT ID** value from the Salto user profile. In Peoplevine, go to **MEMBERS > All Members**, select the member, and paste the value into the **Alternate ID Number** field.
* **Option B — EXT ID is available:** In Peoplevine, go to **MEMBERS > All Members**, select the member, and copy the **Membership Number**. In Salto, paste it into the **EXT ID** field on the user profile.

> **Note**: The EXT ID field must be visible in Salto. If it is not, set the **SHOW\_EXT\_ID** parameter to **1** in **System > General Options > Advanced**. See the Connect guide for the exact steps.

***

### What Gets Synced

| Data                    | Direction          | Notes                                             |
| ----------------------- | ------------------ | ------------------------------------------------- |
| Keycard tap (door open) | Salto → Peoplevine | Real-time, via web request from Salto alarm event |
| Member check-in         | Salto → Peoplevine | Triggered automatically on keycard tap            |

> **Note**: The Salto integration is one-directional. Salto sends check-in events to Peoplevine. Peoplevine does not push data back to Salto.

***

### Troubleshooting

**Check-in not appearing in Peoplevine after keycard tap** Verify the **Post to URL** and **Body** values in Salto match what Peoplevine generated. Confirm the alarm event in Salto is configured with **Trigger Type = Audit trail event**, **WHO = Any Cardholder**, and all **Door Open** commands selected under **WHAT** (full settings live in the Connect guide).

**EXT ID field not visible in Salto** The **SHOW\_EXT\_ID** parameter is not set. Add it under **System > General Options > Advanced** and set the value to **1**. See the Connect guide for the exact steps.

**Member not recognized on tap** The EXT ID in Salto does not match the corresponding value in Peoplevine. If using Option A, check the **Alternate ID Number** field on the member's profile. If using Option B, check the **Membership Number**.

For hardware- or portal-side troubleshooting (Salto reader behavior, system options), refer to the [Connect Salto Space and Peoplevine](https://docs.peoplevine.com/peoplevine-docs/peoplevine-connect) guide or your Salto support contact.

***

### Best Practice

* **Test with a single member first.** Map one member end-to-end and verify a keycard tap creates a check-in before rolling out to your full base.
* **Use consistent ID mapping.** Pick Option A or Option B and apply it to all members. Mixing methods makes troubleshooting harder.

***

### What Happens Next

When a member taps their Salto keycard at any configured access point, Peoplevine records an automatic check-in on the member's CRM profile. No manual check-in is needed from front-of-house staff.

* Peoplevine Connect: Access Control hub README (origin/connect-integrations, commit fcc9870, 2026-04-29)
* Peoplevine Connect: Connect Salto Space and Peoplevine (origin/connect-integrations, commit 188f96e)

*Last updated: 2026-05-24*


---

# 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://help.peoplevine.com/products/integrations-overview/setup-salto.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.