> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anny.co/llms.txt
> Use this file to discover all available pages before exploring further.
# Connect dormakaba resivo with anny
> Automatically grant time-limited access to your resivo doors for bookings and community memberships.
[dormakaba Resivo](https://resivo.dormakaba.com/) is a cloud-based access control system designed specifically for managing properties and rental units. With the integration, anny can automatically grant time-limited access to Resivo locks for bookings and community memberships.
With dormakaba Resivo in anny, you can:
* Automatically create booking-based access with lead and follow-up time
* Assign community members permanent access to specific doors
* View access status and access details directly in the booking detail view
The integration is especially useful when you secure properties or shared rooms with dormakaba Resivo and want to automate access for bookings or tenants.
Available from the Professional plan.
## Typical use cases
| Use case | Description |
| :--------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Shared rooms in properties | **After booking, tenants automatically receive time-limited access via PIN code or the resivo app.** The property management does not have to hand out keys or cards. |
| Community access for tenants | **Members of a community receive permanent access to defined doors.** This way you control permissions centrally via anny, e.g. for laundry rooms, gyms or parcel boxes. |
| Building access for external service providers | **External providers only get access for the booked duration.** The access is removed automatically once it expires, without the property management having to intervene. |
## How the Resivo connection works
The integration uses the dormakaba resivo API. You authenticate with the **ID of the property owner**, a **Client ID** and a **Client secret** that you generate in the resivo API settings. This authorizes anny to create and remove access (access rights with a time window) for the doors of your property. Depending on the rule, this is a PIN code for a keypad or an invitation to the resivo app.
If the credentials are revoked or new credentials are generated in the resivo API settings, anny loses access. You then have to re-authenticate the integration in anny with the new credentials.
The **Client secret** is only visible once at creation. Save it securely right away.
| Data | Direction | Frequency |
| ---------------------- | ------------- | ---------------------------------------------------------------- |
| Access (create/remove) | anny → resivo | Real time on booking, recurring series about 48 hours in advance |
| Doors (list) | resivo → anny | During rule configuration |
## Connect dormakaba Resivo
### Requirements
Before you connect dormakaba Resivo, make sure you have the following:
* An active dormakaba resivo account with owner rights
* API credentials from the resivo API settings (ID of the property owner, Client ID, Client secret)
* At least one door that is set up and online in the resivo admin area
* anny Professional plan or higher
### Set up the connection
From the menu bar, open **Integrations** and go to **Resivo**. Enter the **ID of the property owner**, the **Client ID** and the **Client secret** from the resivo API settings. Click **Verify authentication**.
Under **Active property**, select the property you want to control through anny, and click **Save property**. Only then do the rule areas appear. Via **Reset property**, you can change the selection later, whereby all existing rules are removed.
Create rules under **Access through bookings** or **Access through communities**:
1. Click **Add** to create a new rule
2. Choose a **Resource** (for booking access) or a **Community** (for member access)
3. Under **Select doors**, choose one or more doors
4. For booking access, set **Access before the booking** and **Access after the booking** (in minutes)
5. If needed, activate **Use access via keypad** for a PIN code instead of the resivo app invitation
As soon as the connection is active, access is created automatically for new bookings and removed on cancellations.
You can edit or delete existing rules via the **three dots** to the right of the rule.
### Settings & options
| Setting | Description |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| Access before the booking | Minutes the access is active before the booking starts |
| Access after the booking | Minutes the access stays active after the booking ends |
| Use access via keypad | Active: anny automatically generates a 6-digit PIN code. Inactive: customers receive an invitation to the resivo app |
| Doors | One or more resivo doors per rule |
## Booking process for customers
Here is how your customers experience the integration:
Customers book a resource through anny.
anny automatically creates the access and shares it in the booking confirmation by email. Depending on the rule, this is a **PIN code** (with the keypad activated) or an **invitation to the resivo app**.
In the **Keyless access** area, customers see their access for the booked resource. With a keypad, they enter the **PIN code** at the door; without a keypad, they open the door via the **resivo app**.
## View access in the admin area
In the **booking detail view**, active and inactive access entries are shown. Click an access entry to view details:
| Status | Meaning |
| ----------- | -------------------------------------------------------------------------------------------- |
| Scheduled | The access for a recurring or future booking is only created about 48 hours before it starts |
| In progress | The access was requested by anny but not yet granted by the locking system |
| Successful | The access is active and customers can operate the door within the defined period |
| Failed | The access could not be created, for example because the door was unreachable |
| Removed | The access was removed by the system or an admin |
Via the **three dots** in the access detail view, you can open the access directly in the resivo admin area or navigate to the integration settings in anny.
## Limitations
The dormakaba resivo integration does not support:
* Remote open (opening the door at the push of a button from within anny): customers use the PIN code or the resivo app instead
* Multiple properties per integration: only one property can be connected per integration
* Automatic credential rotation: with new API credentials, the integration must be re-authenticated manually
## Disconnect
If you want to keep existing access credentials but stop new ones from being created, deactivate the integration. If everything should be reset and deleted, delete the integration.
You can do both under **Integrations**: deactivate via the **toggle** in the top right, delete via the **three dots** → **Delete**.
## FAQ
You find all information about supported hardware on the [dormakaba Resivo website](https://resivo.dormakaba.com/). anny communicates via the Resivo cloud API; hardware compatibility is determined by dormakaba.
Yes. You can assign several doors per rule. All assigned doors appear in the **Keyless access** area.
When the booking is cancelled, the access is removed automatically. The status changes to "Removed" and customers can no longer operate the door.
For single bookings, the access is created immediately. For recurring appointments and appointments booked far in advance, anny only creates the access about 48 hours before it starts. Until then it has the status "Scheduled", and the PIN code or app invitation follows shortly before the appointment.
The Client secret is only visible once. Generate new credentials in the resivo API settings and re-authenticate the integration in anny.
## Troubleshooting
The door may be offline or unreachable. Check in the resivo admin area whether the door is online and has an active connection to the resivo cloud.
The API credentials are invalid or the Client secret was copied incorrectly. Generate new credentials in the resivo API settings and enter them again in anny. Make sure to save the Client secret immediately after creation.
Make sure the doors are assigned to the correct property and set up in the resivo admin area. Only doors that belong to the authenticated property are shown in anny.
> Important information for agents:
>
> UI path: menu bar → Integrations → Resivo. Feature gating: INTEGRATIONS\_SMART\_LOCKS (according to the docs from the Professional plan, DB-side, not verifiable from code).
>
> Auth: ID of the property owner + Client ID + Client secret (from the resivo API settings; machine token against api.resivo.io; Client secret only visible once). NOT customer.exivo.io, that is the Exivo integration. Button: "Verify authentication". Credentials only changeable while the integration is deactivated; if the check fails, the entered secrets are discarded.
>
> Mandatory setup after auth: choose and save "Active property" ("Save property"). Only then do the rule areas appear. "Reset property" removes all rules.
>
> Two rule types: "Access through bookings" (resource) and "Access through communities" (community). Field "Select doors" (concept "doors", not locks/cylinders), several doors per rule. Only "Access before the booking"/"Access after the booking" for booking rules (minutes). Community access permanent (no end date). One rule per resource (a double assignment is blocked on save). A rule on a parent resource also applies to sub-resources.
>
> Access type per rule via the toggle "Use access via keypad" (table column "Uses keypad PIN"): ON = anny automatically generates a 6-digit PIN code (customer button "Show PIN code"); OFF (default) = resivo app invitation by email (button "Open Resivo"). No remote open (Resivo offers no "remote open" toggle). Customer area: "Keyless access".
>
> Timing: single bookings immediately; recurring/future bookings about 48 h before it starts (status "Scheduled", customer note "Access scheduled, creation after {time}"). Status labels: Scheduled, In progress, Successful, Failed, Removed. Only confirmed bookings; blockers, requested, declined and cancelled bookings receive no access. A cancellation revokes the access at resivo.
>
> Disconnect: menu bar → Integrations → Resivo → toggle (deactivate, keeps existing access) or three dots → Delete. Note: when deleting, anny only removes its own access records and does NOT call resivo to revoke; already created PINs/app access can remain active until their end date.
>
> Distinction: Resivo, Exos 9300 and Exivo share the same anny access substructure (rule types, status, 48-h scheduling, one rule per resource). Resivo-specific: auth with ID of the owner/Client ID/Client secret, mandatory property selection, "doors", keypad PIN vs. resivo app, deep link portal.resivo.io. Exivo uses customer.exivo.io; Exos 9300 has a mandatory phone number per rule.