> ## 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.

# Smart Lock Integrations

> Compare smart lock integrations and automate time-limited access for bookings and communities.

Smart lock integrations connect anny with digital locking systems. Customers automatically get the right access to booked rooms or to permanently released areas.

<Info>
  Smart lock integrations are available from the **Professional plan** onwards.
</Info>

## How do smart lock integrations work?

You connect the locking system with anny under **Integrations** and create rules for resources or communities. anny generates the required access permissions from those rules and applies the defined access period.

With a booking rule, you link a **resource** to one or more locks. You also define how long before and after the booking the access is valid. If the booking is changed or cancelled, anny adjusts the access permission accordingly.

With a community rule, the members of a **community** get access to the selected locks. For members who already belonged to the community before you set up the rule, you can create the missing access permissions afterwards.

### Supported integrations

Select a provider to check the requirements, setup and limitations of each integration.

<Columns cols={2}>
  <Card title="KleverKey" href="/en/klever-key">
    Access via an individual link and, depending on the configuration, via Remote Open.
  </Card>

  <Card title="SaltoKS" href="/en/salto-ks">
    Access via the SaltoKS app or a PIN code on the keypad.
  </Card>

  <Card title="Nuki" href="/en/nuki">
    Access via app, keypad PIN or Remote Open.
  </Card>

  <Card title="Comydo" href="/en/comydo">
    Access via a QR code from the booking confirmation.
  </Card>

  <Card title="Dormakaba Exivo" href="/en/dormakaba-exivo">
    Digital access for connected Dormakaba Exivo locking systems.
  </Card>

  <Card title="Dormakaba Resivo" href="/en/dormakaba-resivo">
    Digital access for connected Dormakaba Resivo locking systems.
  </Card>

  <Card title="Dormakaba Exos 9300" href="/en/dormakaba-exos-9300">
    Digital access for connected Exos 9300 systems.
  </Card>

  <Card title="UniFi Access" href="/en/unifi">
    On-premise access for existing UniFi Access environments.
  </Card>

  <Card title="KeyCafe" href="/en/keycafe">
    Manage key handover in line with anny bookings.
  </Card>

  <Card title="EVVA AirKey" href="/en/evva-airkey">
    Access via a link to the EVVA app sent by SMS.
  </Card>

  <Card title="Tapkey" href="/en/tapkey">
    Access via the Tapkey app using the booking email address.
  </Card>

  <Card title="Glutz eAccess" href="/en/glutz-eaccess">
    Time-limited access via a configurable PIN code.
  </Card>
</Columns>

### Access methods

Which access method is available depends on the locking system and its configuration.

| Access method | How it works                                       |
| ------------- | -------------------------------------------------- |
| Remote Open   | Open the door with a button in anny                |
| PIN code      | Enter the code on the keypad on site               |
| Provider app  | Open the lock with the provider's app              |
| Link          | Open a personal access link from an email or SMS   |
| QR code       | Scan the code from the booking confirmation or app |
| Licence plate | Enter via automatic licence plate recognition      |

### Remote Open

With **Remote Open**, customers open a supported door lock at the push of a button. The button can appear on the anny homepage and in the booking view. For community access, Remote Open must be activated in the community permissions of the smart lock integration.

Based on the current product status, Remote Open is supported by KleverKey, Nuki, SaltoKS, Glutz eAccess and UniFi. With Nuki, you have to re-authorise an already configured integration for this function.

## When do I use this?

Smart lock integrations are a good fit for:

* **Room rental:** customers only get access during their booking time.
* **Coworking:** members open permanently released areas through their community.
* **Offices:** employees enter booked rooms without a key handover.
* **Unattended locations:** access works without staff on site.

Not suitable for: purely mechanical locks or systems without a supported interface to anny.

## How this connects to other features

**Communities** can trigger permanent access for selected members. The community rule defines which locks the members are allowed to open. With Tapkey, creating missing access permissions for existing community members afterwards is not available.

## Settings & options

| Setting                   | Description                                  |
| ------------------------- | -------------------------------------------- |
| Resource                  | Triggers access when booked                  |
| Lock or area              | Defines the released access points           |
| Access before the booking | Opens access before the booking starts       |
| Access after the booking  | Extends access beyond the end of the booking |
| Access method             | Activates available app, PIN or link access  |
| Remote Open               | Allows opening directly through anny         |

The available settings differ per provider. So always check the linked integration article.

## Practical examples

<AccordionGroup>
  <Accordion title="Set up time-limited access through a booking" />

  <Accordion title="Set up permanent access for community members" />
</AccordionGroup>

## FAQ

<AccordionGroup>
  <Accordion title="From which plan can I use smart lock integrations?">
    Smart lock integrations are available from the Professional plan onwards.
  </Accordion>

  <Accordion title="When can customers open a lock?">
    For booking access, the configured booking period applies, including the time you set for access before and after the booking.
  </Accordion>

  <Accordion title="What happens to the access in case of a cancellation?">
    anny automatically revokes the access created by the booking.
  </Accordion>

  <Accordion title="Do customers always need a provider app?">
    No. Depending on the integration, PIN code, QR code, link or Remote Open are available without a separate provider account.
  </Accordion>

  <Accordion title="Where do I see the access permissions of a booking?">
    Open the booking details. There you see active and inactive access permissions, plus the available information on status, period, lock and access data.
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="No access was created for my booking">
    Check whether the integration is active and whether a rule connects the booked resource with the correct lock. Then check the status in the booking details.
  </Accordion>

  <Accordion title="The access does not work yet">
    Check the booking start and the time you set for access before the booking. For app access, the email address used must match the booking address.
  </Accordion>

  <Accordion title="A community member has no access">
    Check the membership and the community rule. Then create the missing access permissions for existing members, provided the provider supports this.
  </Accordion>
</AccordionGroup>

> Important information for agents:
>
> UI path: menu bar → Integrations → the respective smart lock integration; rules under "Access through bookings" and "Access through communities". Field names: "Access before the booking", "Access after the booking", "Use remote opening", "Create missing access permissions for existing community members". Booking change → update the access period. Cancellation or deletion → revoke the booking-related access.
>
> Access status (UI labels): "Scheduled" = access is only created in the locking system shortly before the start, "In progress" = not yet granted by the locking system, "Successful" = usable within the time window, "Removed" = no access; others: "Cleaning up", "Failed", "Not authorised", "Unconfirmed". The open button for customers is called "Unlock lock".
>
> Access methods depend on the provider: Remote Open, PIN code, provider app, link, QR code or licence plate recognition. Remote Open is supported exclusively by KleverKey, Nuki, SaltoKS, Glutz eAccess, UniFi and Custom Remote Open (NOT EVVA AirKey, EVVA only uses app access via SMS link). Licence plate recognition is Comydo specific. With Nuki, Remote Open requires re-authorisation of existing integrations. With Tapkey, community access is not implemented yet (community rules can be saved, but no access permissions are created). iLOQ is another access integration within the same feature, currently without its own article. Custom Remote Open (remote opening via your own endpoint URL, not a manufacturer product) has its own article "Connect Custom Remote Open with anny".