> ## 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 KleverKey with anny
> Automate time-limited, keyless access for bookings and community members.
[KleverKey](https://www.kleverkey.com/) is a smart lock system for digital, time-controlled door access. With this integration, anny automatically creates matching access permissions for bookings and communities.
With KleverKey you can do the following in anny:
* create digital guest access for bookings
* connect resources and communities with one or more locks
* open doors via an access link or Remote Open without an extra KleverKey account
The integration is especially useful for teams that provide rooms without key handover and without extra effort on site.
Available from the Professional plan onwards.
## Typical use cases
| Use case | Description |
| :------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------ |
| Open rooms after a booking | **Customers automatically receive time-limited access.** The access applies to the linked lock and to the period defined in the rule. |
| Give community members access | **Members get access to shared areas.** You link a community with one or more locks. |
| Open doors directly through anny | **Remote Open opens an authorised lock at the push of a button.** The button appears on the anny homepage or in the booking view. |
## How the KleverKey connection works
anny authenticates the connection with a KleverKey API token and the organisation ID. The token allows anny to retrieve locks and to create time-limited guest access based on your rules.
For a booking, KleverKey creates an individual digital key. anny shows the access in the booking and can send it with the booking confirmation. If a booking is cancelled, the related access permission is revoked. anny only creates access for accepted bookings. A rule on a parent resource also applies to bookings of its sub-resources.
| Data | Direction | Frequency |
| ---------------------------------- | ---------------- | ----------------------------------------------- |
| Locks and organisation data | KleverKey → anny | When setting up and updating the connection |
| Booking-related access permissions | anny → KleverKey | When a booking is created, changed or cancelled |
| Access link and access details | KleverKey → anny | As a response when access is created or changed |
If the API token is revoked or replaced, anny cannot create new access until you update the connection with a valid token.
## Connect KleverKey
### Requirements
Before you connect KleverKey, make sure you have the following:
* a set up KleverKey account with at least one working lock
* guest access activated in the KleverKey organisation settings
* a KleverKey API token and your organisation ID
* the Professional plan in anny
### Set up the connection
Open **Integrations** from the menu bar and go to **KleverKey**. Enter your [API token](https://portal.kleverkey.com/account/api-keys) and the [organisation ID](https://portal.kleverkey.com/organization/settings). Also select the **time zone** in which the access times should apply. The default is your organisation's time zone.
Then define your access rules:
1. In the section for booking or community rules, click **Add**.
2. Select the resource or community.
3. Assign one or more KleverKey locks.
4. For booking rules, define how long the access should be valid before and after the booking.
5. If needed, activate **Send additional invitations from KleverKey** or **Remote opening**.
As soon as the connection is active, anny automatically creates matching KleverKey access based on your rules.
The [video on the KleverKey setup](https://www.loom.com/share/707db5b54f7d47b0a7bc5f78eaf1d5df) shows the full process in the KleverKey portal and in the anny admin area.
You can connect several locks with one resource, or assign the same lock to several resources.
### Settings & options
| Setting | Function |
| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------- |
| Resource | Defines which booking creates an access permission. |
| Community | Gives members of the selected community access to the assigned locks. |
| Locks | Defines which doors can be opened with the rule. |
| Access before the booking | Extends the access period before the booked time. |
| Access after the booking | Extends the access period after the booked time. |
| Send additional invitations from KleverKey | Lets KleverKey send its own invitation email with the access link as well. |
| Remote opening (Remote Open) | Allows authorised customers to open the lock directly through anny. The toggle is called **Use remote opening**. |
You can edit or delete existing rules via the **three dots**.
### Remote Open
With Remote Open, customers can open authorised door locks at the push of a button. For today's bookings and community permissions, the access appears on the anny homepage and in the booking details.
| Place | Where do you open the door? |
| -------- | ---------------------------------------------------------------------------------------------------------------------- |
| Email | The **Open** link in the booking confirmation takes you to the browser. There the **Unlock door** button appears. |
| anny app | The **Unlock door** button appears on the home page under **Today's access** and in the booking under **My bookings**. |
| Browser | The **Unlock door** button appears on the home page under **Today's access** and in the booking under **My bookings**. |
For Remote Open through a community, you activate the function in the community permissions of the smart lock integration.
### Check access permissions
Open a booking and select the related smart lock access. There you see the status, access period, door lock, creation date and access link.
| Status | Meaning |
| ----------- | ------------------------------------------------------------------------------------------------------------------ |
| In progress | anny has requested the access, but KleverKey has not created it yet. |
| Scheduled | For recurring bookings, anny schedules the access and creates it shortly before the respective appointment starts. |
| Successful | The access is active and can be used within the displayed period. |
| Removed | The system or an admin user has removed the access. The lock can no longer be opened with it. |
The [video on the booking process](https://www.loom.com/share/ed44e7768f13451392cf0da986e5f67a) shows how customers use the digital key after the booking.
## Limitations
The KleverKey integration does not support:
* access without guest access activated in the KleverKey account
* creating new access with a revoked or invalid API token
* access outside the period defined in the rule
* more than one booking rule for the same resource
* a status query at the lock: anny sends access permissions, but does not query the live state of the lock
According to KleverKey, the number of guest access permissions is not limited. Hardware prices and available lock models can change. Check the current information directly in the [KleverKey shop](https://www.kleverkey.com/shop).
## 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
No. An individual guest access link can open the lock without an extra KleverKey account.
Yes. One rule can contain several locks. You can also assign one lock to several resources.
anny revokes the access permission linked to the booking as soon as the cancellation has been processed.
Open the booking details and select the smart lock access. There you find the status, period, lock and access link.
anny can send the link in the booking confirmation. Optionally, KleverKey sends an additional email with the same link.
## Troubleshooting
Check the following one by one:
1. The KleverKey integration is active.
2. The API token and the organisation ID are valid.
3. Guest access is activated in the KleverKey account.
4. A rule with at least one lock exists for the booked resource.
KleverKey has not yet confirmed the access requested by anny. Open the access in the booking details and check the related connection in KleverKey via the **three dots**.
Check whether **Remote Open** is activated in the integration and whether a valid access permission currently exists. For community access, the function also has to be activated in the community permissions.
> Important information for agents:
>
> **Classification:** KleverKey is a smart lock integration (access), sharing a common base with the other smart lock integrations (Salto KS, Nuki, Comydo, UniFi Access, Key Cafe). Enabled via the feature INTEGRATIONS\_SMART\_LOCKS (the plan assignment "from Professional onwards" is stored in the database and cannot be finally verified from the code).
>
> **UI paths:** Setup: menu bar → **Integrations** → **KleverKey**. Auth fields: "KleverKey API Token", "KleverKey Organisation ID", plus time zone selection. Rules in the same area: "Access through bookings" and "Access through communities". Deactivate: toggle in the top right; delete: three dots → Delete.
>
> **Terminology (important):** On the admin side, remote opening is called "Use remote opening" (column "Remote opening"); on the customer side, anny shows the badge "Remote Open" and the button "Unlock door". The additional email toggle is called "Send additional invitations from KleverKey". The padding fields are called "Access before the booking" / "Access after the booking". The grant block in the booking is called "Smartlock access". Status values: In progress, Scheduled, Successful, Removed, Unconfirmed, Failed, Not authorised.
>
> **Quirks:** (1) Only accepted bookings receive access; requested, rejected or cancelled bookings and internal blockers do not. (2) Exactly one booking rule per resource (saving is rejected otherwise); several locks per rule and one lock for several resources are allowed. (3) A rule on a parent resource also applies to sub-resources; the more specific rule takes precedence. (4) Recurring bookings receive scheduled access (status "Scheduled"), created shortly before the start; single bookings receive it immediately. (5) Changing the locks or resource of a rule automatically updates or removes future access permissions. (6) Community rules offer the action "Create missing access permissions for existing community members". (7) No status query at the lock and no ongoing status sync. (8) The selected time zone determines the validity times including the lead and follow-up time.
>
> **Remote Open:** a separate access permission in addition to the link access. The button in the app or browser is only active if an access permission is valid today; the home page lists it under "Today's access". For community access, remote opening has to be activated in the community permissions. In the booking confirmation, the access permissions appear in the "Keyless access" section with the link "Open".
>
> **Disconnect:** deactivating keeps existing access permissions and creates no new ones; deleting removes the locally stored access permissions. Note for support: when the entire integration is deleted, the individual links are not actively removed from KleverKey, they expire through their time profile (in contrast to cancelling a single booking, which deletes the link via the API).