> ## 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 exivo with anny

> Automatically grant time-limited access to your exivo locks for bookings and community memberships.

[dormakaba exivo](https://www.dormakaba.com/de-de/exivo) is a cloud-based access control system for small and medium-sized properties. With the integration, anny can automatically grant time-limited access to exivo components for bookings and community memberships.

With dormakaba exivo in anny, you can:

* Automatically create booking-based access with lead and follow-up time
* Assign community members permanent access to specific locks
* View access status and PIN codes directly in the booking detail view

The integration is especially useful when you secure rooms or coworking spaces with dormakaba exivo and want to fully automate access.

<Info>
  Available from the Professional plan.
</Info>

## Typical use cases

| Use case                             | Description                                                                                                                                                                                     |
| :----------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Unlock coworking rooms automatically | **After booking, customers automatically receive a time-limited access link plus PIN.** You no longer have to hand over keys or create access manually.                                         |
| Community access for members         | **Members of a community receive permanent access to defined locks.** This way you control permissions centrally via anny, without maintaining every access individually in the locking system. |
| Building access with day passes      | **Day guests only get access for the booked duration.** The access is removed automatically once it expires, without you having to intervene.                                                   |

## How the Exivo connection works

The integration uses the dormakaba exivo REST API. You authenticate with the **ID of the site**, an **API key** and an **API secret** that you find in your exivo app. This authorizes anny to create and remove access (access rights with a time window and PIN) for the components of your site. anny generates the PIN automatically.

If the credentials are revoked or regenerated in the exivo app, anny loses access. You then have to re-authenticate the integration in anny with the new credentials.

| Data                   | Direction    | Frequency                         |
| ---------------------- | ------------ | --------------------------------- |
| Access (create/remove) | anny → exivo | Real time on booking/cancellation |
| Components (list)      | exivo → anny | During rule configuration         |

## Connect dormakaba Exivo

### Requirements

Before you connect dormakaba exivo, make sure you have the following:

* An active dormakaba exivo account with admin rights
* Your credentials from the exivo app: **ID of the site**, **API key** and **API secret**
* At least one component that is set up and online in the dormakaba admin area
* anny Professional plan or higher

### Set up the connection

<Steps>
  <Step title="Authorize">
    From the menu bar, open **Integrations** and go to **exivo**. Enter the **ID of the site**, the **API key** and the **API secret** from your exivo app. Click **Verify authentication**.
  </Step>

  <Step title="Configure">
    Create rules for booking-based access (**Access through bookings**) or community-based access (**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 components**, choose one or more components
    4. For booking access, set **Access before the booking** and **Access after the booking** (each in minutes)
    5. Optionally activate **Use access via keypad** if customers should enter the PIN directly on the lock's keypad
  </Step>
</Steps>

As soon as the connection is active, access is created automatically for new bookings and removed on cancellations.

<Tip>
  You can edit or delete existing rules via the **three dots** to the right of the rule.
</Tip>

### 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     | If the switch is off, customers get a link plus PIN by email. If it is on, they only get a PIN for the keypad on the lock |
| Components                | One or more exivo components per rule                                                                                     |

## Booking process for customers

Here is how your customers experience the integration:

<Steps>
  <Step title="Book a room">
    Customers book a resource through anny.
  </Step>

  <Step title="Receive an access link">
    anny automatically generates an individual access link plus PIN and sends both in the booking confirmation by email.
  </Step>

  <Step title="Open the lock">
    Customers open the **link from the email**, enter the **PIN** and click **Login**. There they see the access entries that belong to the booked resource. If **Use access via keypad** is active for the rule, customers enter the PIN directly on the lock's keypad instead.
  </Step>
</Steps>

## 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                                                                                                                     |
| ----------- | --------------------------------------------------------------------------------------------------------------------------- |
| 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 lock within the defined period                                           |
| Scheduled   | The access is reserved and will be created shortly before the appointment. This applies to recurring and repeating bookings |
| Failed      | The access could not be created. anny notifies the stored admins                                                            |
| Removed     | The access was removed by the system or an admin                                                                            |

<Tip>
  Via the **three dots** in the access detail view, you can open the access via **View access at provider** in the exivo visitor portal, open the **integration settings** or recreate a failed access via **Recreate access**.
</Tip>

## Limitations

The dormakaba exivo integration does not support:

* Remote open (opening the door at the push of a button from within anny): customers use the access link plus PIN or the keypad PIN on the lock instead
* Multiple sites per integration: only one exivo site can be connected per integration
* Automatic renewal of the credentials: with new credentials, the integration must be re-authenticated manually

## Disconnect

<Warning>
  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.
</Warning>

You can do both under **Integrations**: deactivate via the **toggle** in the top right, delete via the **three dots** → **Delete**.

## FAQ

<AccordionGroup>
  <Accordion title="Which hardware is compatible with exivo?">
    You find all information about supported hardware on the [dormakaba exivo website](https://www.dormakaba.com/de-de/exivo). anny communicates via the exivo cloud API; hardware compatibility is determined by dormakaba.
  </Accordion>

  <Accordion title="Can customers open several components with one booking?">
    Yes. You can assign several components per rule. All assigned components appear on the access page after login.
  </Accordion>

  <Accordion title="Do my customers get a link or a PIN for the keypad?">
    You control this per rule via **Use access via keypad**. If the switch is off, your customers get an access link plus PIN by email. If it is on, they only get a PIN that they enter directly on the lock's keypad. anny generates the PIN automatically in both cases.
  </Accordion>

  <Accordion title="What happens on a cancellation?">
    When the booking is cancelled, the access is removed automatically. The status changes to "Removed" and customers can no longer operate the lock.
  </Accordion>

  <Accordion title="Can I set different access times per resource?">
    The times **Access before the booking** and **Access after the booking** apply per rule. Only one rule is possible per resource. If you need different times for the same components, link them via separate resources with their own rules.
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Access stays in the 'In progress' status">
    The component may be offline or unreachable. Check in the dormakaba admin area whether the component is online and has an active connection to the exivo cloud.
  </Accordion>

  <Accordion title="Authentication fails">
    The credentials are invalid or expired. Check the **ID of the site**, **API key** and **API secret** in your exivo app and enter them again in anny.
  </Accordion>

  <Accordion title="Components do not appear in the selection">
    Make sure the components are assigned to the correct site and set up in the dormakaba admin area. Only components of the authenticated site are shown in anny. Wireless gateways deliberately do not appear in the selection.
  </Accordion>
</AccordionGroup>

> Important information for agents:
>
> UI path: menu bar → Integrations → exivo. Authentication fields (official labels): **ID of the site**, **API key**, **API secret**; button **Verify authentication**. The credentials come from the exivo app (dormakaba also names the portal customer.exivo.io in the docs). Plan gating: feature INTEGRATIONS\_SMART\_LOCKS, according to the docs from Professional (plan tier not verifiable from the code). Env flag: EXIVO\_ACTIVE.
>
> Rule types: **Access through bookings** (with resource, components, **Access before the booking**, **Access after the booking**, **Use access via keypad**) and **Access through communities** (with community, components, keypad switch; no lead/follow-up time). Rule table columns include: resource, components, access before/after the booking, **Uses keypad PIN**. The lock selection is called **Components** / **Select components** in exivo (not "locks", not "cylinders"). Gateways (wireless-gateway) are filtered out of the selection.
>
> Access format: keypad off → link + PIN by email (customer is created as a visitor with email); keypad on → PIN for the keypad only. The PIN is generated automatically by anny (4 to 6 digits), not configurable.
>
> Timing: single bookings receive the access immediately. Recurring/repeating bookings are reserved (status **Scheduled**) and created \~48 h before the appointment. Only confirmed bookings; requested/declined/cancelled bookings and internal blockers receive no access. One rule per resource (saving a second rule for the same resource is blocked). Rules also apply to sub-resources. Community access without an end date gets an internal \~3-year window.
>
> Status values for exivo: In progress, Successful, Scheduled, Failed, Not authorized, Removed. "Unconfirmed" and "Cleanup" are not used for exivo (exivo sets success synchronously, no two-stage verify step; exivo cleans up expired access itself). Access detail actions: **View access at provider** (opens customer.exivo.io/visitors), **Integration settings**, **Copy access URL**, **Recreate access**. No remote open (in the rule editor no remote open switch appears for exivo).
>
> Distinction: exivo is one of three dormakaba integrations with its own integration key (`exivo`). Do not confuse with exos-9300 (`kabaExos9300`, "Profiles", optional mobile number/SMS) and resivo (`resivo`, "Sites"/authorizations, keypad PIN). All three share the access control substructure in anny but differ in authentication and delivery.
>
> Disconnect: menu bar → Integrations → exivo → toggle (deactivate, existing access remains) or three dots → Delete (resets everything in anny).