# How to configure destinations in Salto Homelok
> Set up and manage destinations in the Salto Homelok access control platform, including elevator floors and controlled access points.


## Overview {#overview}

Destinations represent secured points of entry or exit within an installation that can only be accessed by users with appropriate permissions.
The primary use case is elevator control (where presenting a key to a reader activates only the buttons for floors the user has access to), however destinations could also represent any access-controlled output that requires selective activation based on user credentials.

### How destinations work in Salto Homelok {#how-destinations-work-in-salto-homelok}

- **Functionality:** In an elevator scenario, users present a key at a {{< glossary_term "reader" >}}reader{{< /glossary_term >}}, which is attached to a {{< glossary_term "controller" >}}controller{{< /glossary_term >}}.
The system then, based on their permissions (which can be time-dependent, [based on schedules](/homelok/user-guide/property-manager/access/schedules)), enables access to specific destinations by enabling or illuminating corresponding buttons on the elevator panel.
- **Entities affected:**
  - **Destinations:** The actual locations (first floor, second floor, garage, attic).
  Destinations could also be 2 exit or entry points on the same floor (for example, second floor, exit A and second floor, exit B).
  - **Access:** Permissions granted to users.
  These include destinations in addition to "traditional" doors.
  - **Access destination:** The link between an access and a specific destination.

{{% info-panel %}}
Destinations work with the [BLUEnet Controller](/installation-guides/controllers/bluenet) range of devices.
{{% /info-panel %}}

### Technical implementation details {#technical-implementation-details}

- **Controllers:** These devices are central to how destinations work.
A controller with relays is used.
Each relay can correspond to an elevator button, which in turn is a destination.
- **Hardware configuration:**
  - A controller has a **master board** (for example, the BLUEnet Controller standard unit has 2 relays and 2 programmable inputs on its master board).
  - {{< glossary_term "output_expansion_unit" >}}Output expansion units{{< /glossary_term >}} (standard expansion boards) can be added (up to 16), each providing additional relays (typically 4 per expansion unit).
  This allows for a large number of destinations (typically up to 66 or 68, depending on the master board).
  - {{< glossary_term "exit_reader_unit" >}}Exit reader units{{< /glossary_term >}} can be added as needed for additional reader points, enabling separate entry and exit control with a second wall reader.
  Although an exit reader unit has its own relays, it doesn't provide an additional door or destination access point.
  - **Installation distance:** the controller's master board and each output expansion unit or exit reader unit must be installed within 1 meter of each other, since they communicate over a serial bus.
  - **DIP switches:** Installers need to physically configure DIP switches on the expansion boards sequentially (0000, 0001, 0010, 0011, and so on) as they are added, with switches numbered 1 to 4 for easy identification.

Output expansion units and exit reader units are accessories added to an existing controller, not device types you create separately in the **Devices** section.

- **Relay assignment logic:**
  - A controller's relay (or the entire controller setup via its master board) can be configured to manage **either** traditional **doors** **or** **destinations**, but **not both simultaneously**.
  - If you choose a door for a relay/controller, no destinations can be added, and further expansion boards for destinations might be disabled.
  - If you choose a destination, multiple destinations can be linked to the available relays.

{{% info-panel %}}
If you change the purpose of a controller from enabling destinations to doors or vice versa, you must [reset](/nebula/user-guide/installer/maintain-devices/reset) and [reconfigure](/nebula/user-guide/installer/configure-devices/controllers) the controller.
<!-- TODO: This may change in the future. -->
{{% /info-panel %}}

- **Managing doors and destinations:**
  - Doors can either be created implicitly (that's to say, at the same time as [when you create the associated electronic lock](/homelok/user-guide/property-manager/devices/electronic-locks)) or in a separate section if they are to be associated with controllers.
  - In the **Settings** section of Homelok you can manually create and manage both doors and destinations as separate entities, before [associating them with access](/homelok/user-guide/property-manager/access).
  This differs from creating doors implicitly when creating electronic locks.

{{% info-panel %}}
The [passcodes feature of Homelok](/homelok/user-guide/property-manager/users/assign-keys#passcodes) is not currently supported with destinations.
Users cannot use readers fitted with keypads to access destinations at the moment.
<!-- TODO: This will be supported in the future. -->
{{% /info-panel %}}

### BLUEnet Controller settings {#bluenet-controller-settings}

![BLUEnet Controller settings](images/bluenet-controller-settings.png "To use the destinations feature, you need to configure a BLUEnet Controller device")
{.border}

#### Legend {#legend}

1. Input/Output: power input/output and proprietary serial bus for communication with
expansion boards. There are two groups of connections that are identical.
2. Relay outputs: (1A/30VDC).
3. Connection with the reader: consult the [reader installation guides](/installation-guides/readers) for more detailed information about the type of recommended wiring, connections and
maximum distances.
4. Inputs: inputs for external configuration (default, IN2, tamper).
5. **Clear** button: short press (< 3 seconds) to pair with the connected wall reader and discover and pair devices on the proprietary serial bus.

## Creating destinations {#creating-destinations}

To create a destination go to **Settings** > **Destinations** and select **New destination**.

You only need to enter a name for the destination.
For example, **First floor**, **Second floor**, **Garage**, etc.

![Destinations example](images/destinations.png "An example of destinations created in the 'Settings' section")
{.border}

## Associating destinations to controllers {#associating-destinations-to-controllers}

Once you have created a destination, you can associate it with a controller's relays during the controller setup process.
To do this, you need to create a controller first.

![Associating destinations with a controller](images/controller-add-destinations.png "Associating destinations with a controller")
{.border}

For more information on how to create controllers and associate the controller's relays to destinations, see the [section on configuring controllers](/homelok/user-guide/property-manager/devices/controllers).

## Creating doors {#creating-doors}

If you also **only** want to associate a door - rather than destinations - to the controller, first you need to create the door in the **Settings** > **Doors** section.
After that, you can associate the door with the controller's relay in a similar way as you would with destinations.

The BLUEnet Controller device currently allows you to associate one door per controller.

See the section on [creating doors](/homelok/user-guide/property-manager/settings/doors) for more information.