# Accessia Docs

One pane of glass for video monitoring, access control, visitor management, and location services

Accessia is the end-to-end solution that makes every interaction with the physical workplace seamless, more secure, and fully auditable

## Discover

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Quick start guide</td><td><a href="/pages/Hqbf9mbqHBnUoJgl8W2x">/pages/Hqbf9mbqHBnUoJgl8W2x</a></td></tr><tr><td>User and Groups</td><td><a href="/pages/GlxMsbIwZna4sw3H6fUJ">/pages/GlxMsbIwZna4sw3H6fUJ</a></td></tr><tr><td>Sites and floorplans</td><td><a href="/pages/NftKAFJt4WjCBSdFLrDa">/pages/NftKAFJt4WjCBSdFLrDa</a></td></tr><tr><td>Settings access</td><td><a href="/pages/Dv4tdFO7WwpsHpCdf4yW">/pages/Dv4tdFO7WwpsHpCdf4yW</a></td></tr><tr><td>Visitor management</td><td><a href="/pages/85nwyRpQt8R2GLC6UeZb">/pages/85nwyRpQt8R2GLC6UeZb</a></td></tr><tr><td>Accessia app</td><td><a href="/spaces/3aHNco86HS4wMiiOghxU/pages/EuVqlTmkR6TtAy5TzSPB">/spaces/3aHNco86HS4wMiiOghxU/pages/EuVqlTmkR6TtAy5TzSPB</a></td></tr><tr><td>Hardware</td><td><a href="/spaces/gMpDCc9niMPkEbpxDaD9/pages/TkN67HN9lROcAlMTftsO">/spaces/gMpDCc9niMPkEbpxDaD9/pages/TkN67HN9lROcAlMTftsO</a></td></tr><tr><td>Datasheets</td><td><a href="/spaces/gMpDCc9niMPkEbpxDaD9/pages/QtsTo4pLdCCgangeQxDD">/spaces/gMpDCc9niMPkEbpxDaD9/pages/QtsTo4pLdCCgangeQxDD</a></td></tr></tbody></table>


# Quick start guide

## 1. Sign in

1. Check your inbox for an Accessia welcome email containing a temporary password
2. Go to [cloud.accessia.com](https://cloud.accessia.com/) and sign in
3. You’ll be asked to set a new password and set up Multi-factor authentication (MFA) if it’s enabled for your organization

## 2. Connect to a people directory

Skip this step if you're manually adding users and groups to Accessia

1. Go to **Integrations** and follow the steps to add Microsoft Entra ID or Okta

## 3. [Add and configure users and groups](/users-and-groups/adding-users-and-groups)

## 4. Set up a site

1. [Set up a site and floor plan](/site-setup/sites-basics)
2. [Place and preconfigure Hubs](/site-setup/adding-hubs)
3. [Place and configure doors](/site-setup/adding-doors)
4. Place and configure cameras
5. Place and preconfigure **beacons**
6. [Create and manage access schedules](/setting-access/access-schedule-basics)
7. [Set up booking-based access](/setting-access/booking-based-access)
8. [Set up visitor management](/visitor-management/visit-templates)

## 5. Deploy hardware

1. [AI Security Hub installation guide](/hardware/ai-security-hub-hub-v1/ai-security-hub-hub-v1-installation)
   1. Learn about [Hub visual states](/hardware/ai-security-hub-hub-v1/hub-visual-states)
2. [Reader installation guide](/hardware/accessia-reader/reader-installation)
   1. Learn about [Reader visual states](/hardware/accessia-reader/reader-visual-states)
3. Go to a real deployment from preconfigured hardware

## 6. Maximize Accessia

1. How to add third party video cameras
2. How to use **Events**
3. How to set up **Alerts**
4. How to use **Lockdown**
5. How to use **Reports**

## 7. Deploy to your organization

1. Roll out mobile credentials
2. Write cards


# Adding users and groups

Add a new user or group from the **Users & groups** tab

1. Add your users first
2. After adding a user, you can select their Global and Site roles from the **Account** tab, and add physical passes for them from the **Passes** tab

{% hint style="info" %}
You can add passes before creating any access schedules
{% endhint %}

3. Add a group
4. Add users to your group

{% hint style="info" %}
You can add users to multiple groups
{% endhint %}

{% hint style="info" %}
You can set access schedules for particular groups, so consider also creating groups based on shared access schedules. For example, ‘Medium Security’
{% endhint %}

See [Setting access](/setting-access/access-schedule-basics) to define access for a user or group


# User passes

Add passes to users so they can identify themselves at Readers and get through doors you’ve allowed them access to. There are four types of passes:

* Mobile passes
* NFC cards
* CSN cards (any card with a serial number)
* PINs

{% hint style="info" %}
You can add passes before creating any access schedules
{% endhint %}

### Mobile passes

Users can create a mobile pass by downloading Accessia app on their device and logging in. When a user is created, they receive a welcome email asking them to do so

{% hint style="info" %}
Users must give Accessia app permission to access the device’s Bluetooth, location, and background location to use Accessia app as a pass
{% endhint %}

### NFC cards

{% hint style="info" %}
Adding a NFC pass requires a NFC card writer
{% endhint %}

Add an NFC pass to a user from the **user’s profile**

1. Go to the **Passes** tab
2. Click ‘Add NFC card’ in the upper right corner
3. Select the port with your NFC card writer
4. Place the NFC card on the card writer and wait till the card has been added to the user
5. Click close

### CSN cards

{% hint style="info" %}
A CSN card can be any card with a serial number - for example a Wiegand 26-bit Prox H10301 card
{% endhint %}

Add an CSN pass to a user from the **user’s profile**

1. Go to the **Passes** tab
2. Click ‘Add CSN card’ in the upper right corner
3. Select which the card type under **Configuration**
4. Fill the field(s) for that card type
5. Click save

### PINs

PINs can be used at keypads for access

{% hint style="info" %}
By default, PINs can only be used for two-factor authentication. To enable PIN as single factor authentication, see [door settings](/site-setup/adding-doors/door-settings)
{% endhint %}

Add PINs to a user from the **user’s profile**

1. Go to the **Passes** tab
2. Click ‘Add PIN’ in the upper right corner
3. Select a PIN or generate a random PIN
4. Click Save

{% hint style="info" %}
Users can only have one PIN each and PINs must be unique
{% endhint %}


# Resetting a multi-factor credential

As an admin, you might need to reset a user’s MFA credential. For example, if they have changed devices and no longer have access to their MFA authenticator

To do this:

1. Go to **Users & groups** and find the user
2. Go to the **Account** tab
3. Select ‘Reset credentials’

<img src="/files/igInCtZIdecYnI3jVCkW" alt="" width="375">

4. The user will be sent a new temporary password to log in with, after which they can set a new password and set up a new MFA app


# Sites basics

## **Sites basics**

Accessia uses real world concepts to represent your building and how hardware is placed

In Accessia;

* A **site** represents a single physical location or address - a headquarters or regional office, for example.
* A site is made up of one or more **floors**
* **Floors** are constructed by uploading a floor plan image and then placing **rooms** on it. For example, meeting rooms, server rooms, and kitchens
* To connect rooms together on the floor plan, place **doors** between them, just as they are in reality
* Add hardware such as cameras, beacons, and kiosks inside rooms or by doors on the floor plan
* Rooms can be grouped together into optional **zones** when they share the same access rules, for example, rooms that only engineering teams have access to can be grouped into an engineering zone

In the example below,

* Doors are connecting rooms
* Hubs are in Server Room A
* Both Server Rooms are in a secure zone, highlighted in pink, and sharing the same access rules
* The Kitchen and Reception are in a common areas zone, highlighted in green, and also sharing the same access rules

<img src="/files/ZeAAiznf5FTVsYixuNN2" alt="" width="563">


# Setting up a site

1. Go to **Site setup** and select **New site**
   1. Enter a name for your site, for example ‘New York - Avenue of the Americas’
   2. Select the local timezone of the site from the dropdown menu
   3. Enter the longitude and latitude of the site. You can find these using external tools such as <https://www.latlong.net/>

{% hint style="info" %}
Accessia requires longitude and latitude information for location services features to work when users are onsite
{% endhint %}

1. Save your site information then click **New floor**, enter a floor name, and upload a floor plan image
2. When you’ve added the new floor, click on **Edit map** and then **Add room**
   1. Click to draw a point on each corner of the room you’re adding and click **Save**
   2. Give your room a name
   3. Set which zone the room is in
   4. Set the room type and capacity

{% hint style="info" %}
Zones group rooms together to share the same access schedule
{% endhint %}

{% hint style="info" %}
Setting a room type and capacity allows for accurate reporting on space utilization
{% endhint %}

## Related pages

* [Add Hubs](/site-setup/adding-hubs)
* [Add doors](/site-setup/adding-doors)
* [Setting access](/setting-access/access-schedule-basics)


# Adding Hubs

Add Hubs to your site map

1. Go to **Site setup** and select the relevant site
2. Click on **Edit map**
3. Drag a **Hub** to where it will be installed on the floor plan
4. Name your Hub and select its serial number if you know it. When a serial number has been assigned, the correct Hub type will be automatically selected. If the serial number is unassigned, you must select whether it is an AI Security Hub or Cloud Converter

{% hint style="info" %}
If hardware is yet to arrive or be allocated, you can set the serial number as unassigned and update it later&#x20;
{% endhint %}


# Adding doors

Add access controlled doors to your site map

{% hint style="info" %}
Make sure to add Hubs to your site before adding doors
{% endhint %}

1. Drag a door to the wall it is positioned on. This will connect rooms together, and external walls to **Outside.** When you first add a door, it will appear as being disconnected
2. Click on a disconnected door and select **Link to Hub** to start setup
3. Select the Hub this door will be connected to

#### Linking a door to an AI Security Hub / Hub v1

4. Select the channel this door will be connected to
5. Complete door setup by selecting
   1. The reader type - Accessia Readers and third party OSDP readers are supported
   2. Which side of the door the reader is on
   3. Whether a REX is fitted
   4. If there is a door status input
   5. Whether there are DEOL resistors installed
   6. Any auxiliary inputs that are linked to the door

#### Linking a door to a Cloud Converter for S2 NetBox

4. Select the blade and reader input this door will be connected to
5. Complete door setup by:
   1. Selecting which side of the door the reader is on
   2. Adding locks and selecting whether the lock is energized on open or lock
   3. Adding any input that are linked to the door, selecting input type, polarity and supervision type

{% hint style="info" %}
You can rename a door after you've added it to the site by clicking on the menu button <i class="fa-ellipsis-vertical">:ellipsis-vertical:</i> in the upper right corner and selecting **Customize name**
{% endhint %}


# Door settings

Once you’ve added a door to the site, you can change how the door behaves by clicking the door on the floor plan, and going to the **Behavior** tab

### **Unlock methods**

* Enable or disable hands-free unlock (UWB) and set the range if enabled. Read more about [setting up hands-free unlock](/site-setup/adding-doors/set-up-hands-free-uwb-unlock)
* Enable or disable PIN as single factor authentication

{% hint style="info" %}
By default, PINs can only be used for two-factor authentication
{% endhint %}

* Enable or disable remote app unlock. If enabled, allow only admins or admins and users with access to unlock the door remotely via Accessia app

{% hint style="info" %}
Read more about unlocking doors remotely via [Accessia for iOS](/accessia-app/accessia-for-ios/remote-unlocking-doors-on-ios) and [Accessia for Android](/accessia-app/accessia-for-android/remote-unlocking-doors-on-android)
{% endhint %}

### Unlock durations

* Define how long the door will be unlocked for when users request access from either direction
* Define whether the door should relock immediately when it is opened. If this setting is disabled, the door will relock after the unlock duration has been exceeded

{% hint style="info" %}
If the door does not have a door status input, it will relock after the unlock duration has been exceeded
{% endhint %}

* Define whether an event should be raised in the event log if the door is held open or fails to relock for a set duration

{% hint style="info" %}
If you only want to raise an event if the door is held open while it is supposed to be locked, select ‘raise held open event only when door is locked’
{% endhint %}

### Reader behavior

* Adjust Reader bluetooth sensitivity
* Adjust Reader brightness
* Enable or disable Reader sounds
* Enable or disable Reader flashing while the door is being held open or has been forced open

{% hint style="info" %}
Read more about [Reader behavior](/site-setup/reader-behavior)
{% endhint %}


# Set up hands-free (UWB) unlock

{% embed url="<https://www.youtube.com/watch?ab_channel=Accessia&v=hN_UjXpTGgY>" %}

Enabling hands-free unlock on doors with Accessia Readers means that users don’t have to have their phone in their hand to unlock the door

{% hint style="info" %}
You’ll need to allow hands-free unlock for each door
{% endhint %}

In the Accessia portal:

1. Go to **Site** **setup** to choose the site and floor where your door is located
2. On your site floor plan, click on the door you want to enable hands-free access for
3. Go to **Behavior** and click the edit button in the upper right corner
4. Under **Unlock methods**, enable Hands-free unlock (UWB) and move the slider to the desired range. The larger the range, the further away from the Reader users can be to unlock the door with UWB
5. Click save and hands-free unlock is enabled for the door

<figure><img src="/files/0S2pB9TB1g8eZt2hMWsc" alt="" width="563"><figcaption></figcaption></figure>

Users can then set up UWB unlock from their phones, a guide for this is here:

{% content-ref url="/spaces/3aHNco86HS4wMiiOghxU/pages/9Lor0tt9FmtaxzJtH6tC" %}
[Hands-free (UWB) unlock](/accessia-app/accessia-for-ios/hands-free-uwb-unlock)
{% endcontent-ref %}


# Adding elevators

Add elevators to your site map

## Setting up elevator relays

1. Go to **Site setup** and select the relevant site
2. Click on **Edit map**
3. Drag an **Elevator door** to where the elevator opens up onto the floor
4. Select an existing elevator to add the door to or create and name a new one. If there are no elevators on your site, a new one will be automatically created
5. Go to each floor that the elevator goes to and repeat steps 3-4
6. To configure your elevator, click on any of the elevator doors then go to the **Hardware** tab and select **Link to Hub**
7. Select the Hub and channel the elevator Reader will be connected to
8. Select which output each floor button is wired to on the Hub

{% hint style="info" %}
If a floor button is not wired to the Hub, that floor will not be access controlled and anyone using the elevator will be able to access the floor
{% endhint %}

9. Go to the **Behavior** tab, click **Edit** and configure:
   1. How long the floor buttons should be active when a valid pass has been presented
   2. Reader bluetooth sensitivity
   3. Reader light brightness
   4. Whether the Reader sounds should be turned on or off&#x20;

{% hint style="info" %}
If a user has access to a room in which the elevator opens, they will also have access to that floor via the elevator

[Learn more about setting access](/setting-access/access-schedule-basics)
{% endhint %}

## Destination dispatch&#x20;

Accessia access control can integrate with destination dispatch systems. Get in touch at <sales@accessia.com>


# Triggering actions

Set up your Hubs or doors so that every time a certain event occurs, one or more actions are triggered

> **Example**
>
> A panic button locks down the site when pressed

**The following events can trigger actions:**

* Hub events:
  * Time of day
  * Hub tamper detected
  * Hub battery failure
  * Mains power failure
* Door events:
  * Door unlocked
  * Door locked
  * Access requested - Allowed
  * Reader tamper detected
  * Lock fails to energize
  * Door input opened
  * Door input closed
  * Door input state changed
* Input events:
  * Input opened
  * Input closed
  * Input state changed

**Events can trigger one or more of the following actions:**

* Site actions
  * Lock down site
* Door actions
  * Quick unlock doors
  * Unlock doors - toggle
    * Each time the event occurs, the selected doors will switch from being on schedule to unlocked and off schedule. [Read more about taking doors off schedule](/setting-access/taking-doors-off-schedule)
  * Lock doors - toggle
    * Each time the event occurs, the selected doors will switch from being on schedule to locked and off schedule. [Read more about taking doors off schedule](/setting-access/taking-doors-off-schedule)
* Hub actions
  * Send webhooks
  * Activate AUX outputs
  * Deactivate AUX outputs
  * Pulse AUX outputs

{% hint style="info" %}
Actions can only affect doors that are linked to the Hub associated with the trigger event
{% endhint %}

> **Example**
>
> A button behind the reception allows the receptionist to unlock the front door when they are at the reception and lock it when they are not

## Setting up a trigger

1. Go to **Site** **setup** and choose the site and floor where your Hub or door is located
2. Click on the Hub or door you want to trigger actions from
3. Go to the **Triggers** tab and click the **Add trigger** button in the upper right corner
4. Select a Hub, door, or input event as the trigger event. See above for the list of possible trigger events
5. Click **Add action** and select the action you want to trigger each time the trigger event occurs. See above for the list of possible actions
6. If relevant, configure which doors should be affected by the action. You can only select doors linked to to the Hub associated with the trigger event
7. Add more actions if required
8. Click **Save**
9. You have now set up your trigger, which will be listed under the **Triggers** tab

<div><figure><img src="/files/Jr8a6wp3rMTcw8bPqzxo" alt="" width="282"><figcaption></figcaption></figure> <figure><img src="/files/6epzC4V5ULvYpaOoobIU" alt="" width="282"><figcaption></figcaption></figure></div>

## Auditing triggered actions

Actions triggered by events are audited just like other user actions, so you're always aware of what's happening on your sites


# Reader behavior

In everyday operation, the Reader:

1. Is lit solid red or green to indicate whether the door is locked or unlocked
2. Flashes green 3 times to indicate that a credential has successfully unlocked the door
3. Starts a countdown indicating how long the door will be unlocked for to allow it to be opened
   1. Set timings for a door in the [door settings](/site-setup/adding-doors/door-settings)
   2. If UWB is enabled, the countdown is replaced by an infinite chase for as long as the user is standing within proximity to the door

When the door is opened, the lock either:

1. Engages almost immediately so that the door is locked when it's closed. The Reader returns to being lit red
2. Stays unlocked for the full unlock duration before it locks

Configure the Reader behavior in the [door settings](/site-setup/adding-doors/door-settings)

1. When a REX is used to unlock the door, the Reader stays lit red
2. The Reader can also be set to flash red if a door is held open or if there is a door forced event. Set this in the [door settings](/site-setup/adding-doors/door-settings)

{% hint style="info" %}
You can adjust Reader brightness and turn sounds on or off in the [door settings](/site-setup/adding-doors/door-settings)
{% endhint %}

## Reader visual states

Accessia Reader has several different colors and lighting patterns to communicate different statuses

{% columns %}
{% column %}

<div align="center"><figure><img src="/spaces/gMpDCc9niMPkEbpxDaD9/files/enVs4l6ZuKxo4FLAKoSc" alt="" width="121"><figcaption></figcaption></figure></div>

<p align="center">Solid red - door locked under access control schedule</p>

<p align="center"></p>
{% endcolumn %}

{% column %}

<figure><img src="/spaces/gMpDCc9niMPkEbpxDaD9/files/t1ZAM0JCISn18APeFLV1" alt="" width="121"><figcaption></figcaption></figure>

<p align="center">Flashing red - door warning (held open, forced, tamper)</p>
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

<figure><img src="/spaces/gMpDCc9niMPkEbpxDaD9/files/M7guh9dSJmqnQgRWdRtK" alt="" width="121"><figcaption></figcaption></figure>

<p align="center">Solid green - door unlocked under access control schedule</p>

<p align="center"></p>
{% endcolumn %}

{% column %}

<figure><img src="/spaces/gMpDCc9niMPkEbpxDaD9/files/MlugjrauZSUjBZyhaCYu" alt="" width="121"><figcaption></figcaption></figure>

<p align="center">Flashing green - access granted</p>

<p align="center"></p>
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

<figure><img src="/spaces/gMpDCc9niMPkEbpxDaD9/files/8uXPKVgd0x2yTkH7KQJE" alt="" width="121"><figcaption></figcaption></figure>

<p align="center">Green segment countdown - door unlocked and counting down to locked</p>
{% endcolumn %}

{% column %}

<figure><img src="/spaces/gMpDCc9niMPkEbpxDaD9/files/DUg9YN7GqyW9KAAo1E1K" alt="" width="121"><figcaption></figcaption></figure>

<p align="center">Green segment chase - door unlocked while the UWB user is in proximity</p>
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

<figure><img src="/spaces/gMpDCc9niMPkEbpxDaD9/files/GW78i9NBEQjnHkqwy3jw" alt="" width="121"><figcaption></figcaption></figure>

<p align="center">Yellow segment chase - reading NFC credential</p>
{% endcolumn %}

{% column %}

<figure><img src="/spaces/gMpDCc9niMPkEbpxDaD9/files/U0C4rGldMd1Lb9SlpJzS" alt="" width="121"><figcaption></figcaption></figure>

<p align="center">Solid dark blue - door locked, meeting room available to access</p>
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

<figure><img src="/spaces/gMpDCc9niMPkEbpxDaD9/files/Vqp2UPmljjTqwpHGyhYw" alt="" width="121"><figcaption></figcaption></figure>

<p align="center">Solid purple - reader in commissioning mode</p>
{% endcolumn %}

{% column %}

<figure><img src="/spaces/gMpDCc9niMPkEbpxDaD9/files/kIvwFEVRwkFuwIvRklfA" alt="" width="121"><figcaption></figcaption></figure>

<p align="center">Solid blue with purple segment chase - ‘Beep reader’ triggered from Portal</p>
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

<figure><img src="/spaces/gMpDCc9niMPkEbpxDaD9/files/3X6e8zhmliE0ZriGsTAi" alt="" width="121"><figcaption></figcaption></figure>

<p align="center">Partial flashing green segment with solid white - Reader booting, updating, or loss of communication with the Hub (before boot)</p>
{% endcolumn %}

{% column %}

<figure><img src="/spaces/gMpDCc9niMPkEbpxDaD9/files/IXWUGxhQl65pb8PXWDCL" alt="" width="121"><figcaption></figcaption></figure>

<p align="center">Flashing yellow - Fault - loss of communication with the Hub (after Reader boot)</p>
{% endcolumn %}
{% endcolumns %}


# Access schedule basics

## Day templates and calendars

Accessia uses calendar-based access schedules, with the ability to create day templates

* Day templates are configurable templates for defining the site’s access schedule on any given day
* The calendar allows you to apply those day templates to specific days

> **Example**
>
> You might create a day template for how a building will be accessed on typical working days:
>
> Day template name: *Work day*
>
> Applies to: *Every Monday to Friday*

Accessia provides a ‘No access’ day template by default, which locks all access controlled doors. You can’t modify this day template

## Rooms and doors

Access schedules define who can enter a room. Doors inherit their access rules automatically from the room

> **Example**
>
> Your break room has 2 entrances from the hallway
>
> Everyone in the Finance team is added to to the access schedule for the doors into the break room
>
> Both doors from the hallway into the break room automatically inherit access rules from the room to allow all Finance team members access

## Zones

When there are two or more rooms that can be accessed by the same users and groups, adding those rooms to a zone reduces duplicate work when setting up the access schedule

> **Example**
>
> You have 5 meeting rooms that all employees can access
>
> These meeting rooms could be added to an ‘All employees meeting rooms' zone

## **Create an access schedule**

### 1. Create a day template

1. Go to **Site setup** > **Day templates** tab
2. Create a new day template with a suitable name and icon
3. When you’ve created the new day template, all the rooms and zones on the site will be listed

{% hint style="info" %}
You can copy access from an existing day template. This is helpful when your new day template will have a similar access schedule to an existing one. Copying the access schedule won’t link the two day templates in any way
{% endhint %}

### 2. Manage access

To see the access schedule for a room or zone, click on the room or zone

<figure><img src="/files/Ae87sTrZWPTYrC7hlhlj" alt=""><figcaption></figcaption></figure>

The access schedule is divided into 3 sections. To edit any section, hover your cursor over it until the pencil icon ✏️ appears, then click to edit

* **Door state** - whether the door is locked (so only specific users and groups can enter) or unlocked (so anyone can enter)
* **Access when locked -** the specific users and groups who can access the room when the door state is locked. Access can be added in time blocks (e.g. 6 AM to 6 PM)

> **Example**
>
> Only users in the Marketing group can access the Marketing meeting room ***when it is locked*** from 9 AM to 5 PM
>
> Outside of these times, the door is unlocked so anyone can enter

* **Access when locked or booked** - the specific users and groups who can access the room at any time, even if the door is locked, or if the room is booked. Learn more about [booking-based access](/setting-access/booking-based-access)

> **Example**
>
> An IT technician can access the Marketing meeting room ***at any time*** including when it is locked from 9 AM to 5 PM

**Door state**

1. Hover over the door state section and click the edit pencil to configure door states
2. To add a period where the door is unlocked you can either:
   1. click '+' to the right of the access schedule and input an unlocked time range

      or
   2. click and drag on the access schedule to create an unlocked period

**Access when locked**

1. Click the edit pencil to configure access for when the door is locked
2. Search for the users and groups to allow access to when the door is locked
3. Set the start and end time for access to be allowed

{% hint style="info" %}
Search will show you both users and groups created on Accessia and also those synced from integrations such as Microsoft Entra ID and Okta
{% endhint %}

**Access when locked or booked**

1. Click the edit pencil to configure access regardless of door state or time of day
2. Search for the users and groups to allow access to when locked or booked

### 3. Apply the access schedule

1. Once a schedule has been created for all rooms and zones within the site, click **Apply to dates** in the sidebar on the left
2. Select which dates this access schedule applies to

{% hint style="info" %}
You can quickly select all instances of a given day (e.g. Wednesdays) by clicking the **WED** header on the calendar, or select all weekdays using the dedicated **Weekdays** dropdown above
{% endhint %}

{% hint style="info" %}
You can view which day template is being used on any given date from the **Calendar** tab
{% endhint %}

## **Make changes to access schedules**

The **Schedule** tab shows the day template in use on any given date

1. Go to the date where a change needs to be made and expand the relevant room / zone
2. Manage access, as per section 2 above
3. To save changes, click the **Update** button containing the specific date you are changing

{% hint style="info" %}
To change all instances of a day template, click the **Update** button containing the day template name
{% endhint %}


# Creating an access schedule

## 1. Create a day template

1. Go to **Site setup** > **Day templates** tab
2. Create a new day template with a suitable name and icon
3. When you’ve created the new day template, all the rooms and zones on the site will be listed

{% hint style="info" %}
You can copy access from an existing day template. This is helpful when your new day template will have a similar access schedule to an existing one. Copying the access schedule won’t link the two day templates in any way
{% endhint %}

## 2. Manage access

To see the access schedule for a room or zone, click on the room or zone

<figure><img src="/files/Ae87sTrZWPTYrC7hlhlj" alt=""><figcaption></figcaption></figure>

The access schedule is divided into 3 sections. To edit any section, hover your cursor over it until the pencil icon ✏️ appears, then click to edit

* **Door state** - whether the door is locked (so only specific users and groups can enter) or unlocked (so anyone can enter)
* **Access when locked -** the specific users and groups who can access the room when the door state is locked. Access can be added in time blocks (e.g. 6 AM to 6 PM)

> **Example**
>
> Only users in the Marketing group can access the Marketing meeting room ***when it is locked*** from 9 AM to 5 PM
>
> Outside of these times, the door is unlocked so anyone can enter

* **Access when locked or booked** - the specific users and groups who can access the room at any time, even if the door is locked, or if the room is booked. Learn more about [booking-based access](/setting-access/booking-based-access)

> **Example**
>
> An IT technician can access the Marketing meeting room ***at any time*** including when it is locked from 9 AM to 5 PM

**Door state**

1. Hover over the door state section and click the edit pencil to configure door states
2. To add a period where the door is unlocked you can either:
   1. click '+' to the right of the access schedule and input an unlocked time range

      or
   2. click and drag on the access schedule to create an unlocked period

**Access when locked**

1. Click the edit pencil to configure access for when the door is locked
2. Search for the users and groups to allow access to when the door is locked
3. Set the start and end time for access to be allowed

{% hint style="info" %}
Search will show you both users and groups created on Accessia and also those synced from integrations such as Microsoft Entra ID and Okta
{% endhint %}

**Access when locked or booked**

1. Click the edit pencil to configure access regardless of door state or time of day
2. Search for the users and groups to allow access to when locked or booked

## 3. Apply the access schedule

1. Once a schedule has been created for all rooms and zones within the site, click **Apply to dates** in the sidebar on the left
2. Select which dates this access schedule applies to

{% hint style="info" %}
You can quickly select all instances of a given day (e.g. Wednesdays) by clicking the **WED** header on the calendar, or select all weekdays using the dedicated **Weekdays** dropdown above
{% endhint %}

{% hint style="info" %}
You can view which day template is being used on any given date from the **Calendar** tab
{% endhint %}

## **Make changes to access schedules**

The **Schedule** tab shows the day template in use on any given date

1. Go to the date where a change needs to be made and expand the relevant room / zone
2. Manage access, as per section 2 above
3. To save changes, click the **Update** button containing the specific date you are changing

{% hint style="info" %}
To change all instances of a day template, click the **Update** button containing the day template name
{% endhint %}


# Taking doors off schedule

When a door is off-schedule it

* Ignores the door lock schedule
* Is either locked or unlocked until it is returned to schedule
* Allows access to users according to their access permissions
* Can be manually returned to schedule by an admin at any time
* Can be returned to schedule by an event trigger
* Can be automatically returned to schedule at a specified time

A door can be taken off schedule by

* Primary and secondary admins
* Event triggers

{% hint style="info" %}
During a lockdown all doors will be locked down regardless of whether they are on or off schedule
{% endhint %}

> **Example**
>
> A receptionist needs to step away from the reception for a moment, but the front door is unlocked. They can quickly take the door off schedule and lock it, so that the building is secure. Users with access permissions can still use a valid credential for access while the door is locked off schedule

## Taking a door off schedule manually

Only primary and secondary admins can take doors off schedule

1. Go to **Site setup** and select the relevant site and floor
2. Click on the door you want to take off schedule
3. On the **Schedule** tab, click on the **Take door off schedule** button
4. Select the door’s lock state while off schedule
5. Select when the door should be automatically returned to schedule

<figure><img src="/files/YX3WJdPJNmZNHwBw5NwA" alt="" width="375"><figcaption></figcaption></figure>

6. Click **Confirm**
7. The door is now off-schedule and the door’s regular schedule will be ignored for the duration of the off-schedule session

Admins can also take doors off schedule via Accessia app for [iOS](/accessia-app/accessia-for-ios/taking-doors-off-schedule-on-ios) and [Android](/accessia-app/accessia-for-android/taking-doors-off-schedule-on-android)

## Returning a door to schedule manually

Only primary and secondary admins can return doors to schedule

1. Go to **Site setup** and select the relevant site and floor
2. Click on the door you want to return to schedule
3. On the **Schedule** tab, click on the **Return to schedule** button
4. Click **Confirm**
5. The door is now returned to schedule

Admins can also return doors to schedule via Accessia app for [iOS](/accessia-app/accessia-for-ios/taking-doors-off-schedule-on-ios) and [Android](/accessia-app/accessia-for-android/taking-doors-off-schedule-on-android)

## Setting up an event trigger to switch a door on and off schedule

Event triggers can be set up to switch a door between being on-schedule and off-schedule when a certain event occurs. [Read more about triggering actions](/site-setup/triggering-actions)


# Booking-based access

## **Booking-based access basics**

You can allow access to a meeting room based on bookings in that room’s calendar. This feature currently supports Microsoft 365 room resource calendars.

With booking-based access, a room still has an access schedule (see [Setting access](/setting-access/access-schedule-basics)) but the schedule is overridden when there is a booking, allowing access only to users on the booking invite.

Users and groups in **Access when locked or booked** section of the access schedule retain access during a booking.

## **Set up booking-based access**

Accessia can read bookings from a Microsoft 365 room calendar.

1. Make sure the Microsoft Entra ID integration is set up
   1. Booking-based access specifically requires the Microsoft Graph Application Permissions for *Calendars.Read* and *Place.Read.All*
2. In Accessia, under **Site setup**, click the meeting room that you want to apply booking-based to
3. Go to the **Integrations** tab
4. Click the edit pencil to select the name of the corresponding meeting room from Microsoft

<figure><img src="/files/nxVfrsOdxtoIxXCTa0a3" alt="" width="375"><figcaption></figcaption></figure>


# Visit templates

Learn what visit templates are and how to set them up

A visit template defines how a visitor can access the site, including

* Which rooms they can access during their visit
* What information is included in the invitation email
* Any documents requiring signature before visitors can sign in, and an email address signed documents will be sent to for audit

{% hint style="warning" %}
At least one visit template needs to be created before users can invite visitors
{% endhint %}

## Create a visit template

1. Go to **Visitors** and select the site you want to set up visit templates for
2. Go to the **Visit templates** tab
3. Click **New visit template**
4. Name your visit template, select which rooms or zones visitors can access, and add any information that should be included in the invitation email

{% hint style="info" %}
If visitors will need to sign documents you can add up to 3 files and an audit email address. See [Visitor documents](/visitor-management/visitor-documents)
{% endhint %}

<div data-full-width="false"><figure><img src="/files/bKz0KddFrw3izM5Ded1y" alt="" width="393"><figcaption></figcaption></figure></div>


# Visitor documents

Learn how to set up documents requiring signature

If visitors need to sign any documents before they sign in at your site, you can add these to the relevant visit template. You can upload up to 3 PDF documents no larger than 2MB each

To autofill visitors’ names, signature date, and the name of the host site onto your visit documents, makes sure the PDF includes form fields. You can add form fields using a PDF editing service such as Adobe Acrobat

{% hint style="info" %}
Make sure to name your PDF form fields so that you can easily match them with the correct information when uploading to Accessia
{% endhint %}

Accessia will automatically detect form fields when you upload documents. You can then select which information to autofill in each field when the visitor signs the document

<figure><img src="/files/3sgNb0QhIco3H5JhEs2I" alt="" width="443"><figcaption></figcaption></figure>

If the PDF does not include form fields, the document will not be modified during sign in

After a visitor has signed the documents, they will receive copies of them by email. If an audit email has been set up on the visit template, copies will also be sent to this address for easy auditing


# Visitor Kiosk

Learn how to set up a Visitor Kiosk

Before you get started with a Visitor Kiosk, you'll need to&#x20;

1. [Set up a site](/site-setup/setting-up-a-site)
2. [Create at least one visit template](/visitor-management/visit-templates)

## Set up a Visitor Kiosk

1. Unbox the Visitor Kiosk and connect it to power
2. Connect the Kiosk to the internet using either Wi-Fi or a wired USB-C to Ethernet adapter
3. On the Portal, from the sidebar go to **Site setup** → the site you want to add a Visitor Kiosk to
4. Click **Edit map** and drag the Visitor Kiosk to the room where it is placed
5. Set a name and which visit template to use when a visitor uses self check-in on the Kiosk
6. If you’d like to print visitor badges, set a badge printer URL. Speak to Accessia about setting up a badge printer URL
7. Click **Save**
8. Click on the newly added Kiosk on the map and select **Set up** from the card
9. Show the QR code to the Kiosk


# Integrations

## Pre-built integrations

Accessia has a range of pre-built integrations that allow you to connect your system to third-party directories, cameras, locks, and environmental data

### Directory integrations

Import users, groups, and access control settings, and enable SSO with a directory integration. Accessia supports:

* Microsoft Entra ID
* Okta

### Camera integrations

View video alongside door access control events. Accessia supports:

* Avigilon Alta
* Eagle Eye
* Rhombus

### Lock integration

Accessia supports ASSA ABLOY Aperio locks for access control

### Environmental sensor integration

Accessia supports Neat devices to get environmental data from rooms

## Custom API integration

Custom API integrations allow third-party integrations to read data such as the configured users and groups on Accessia secured using Machine-to-Machine authentication

API integrations have the same permissions as a global **Event Viewer** Accessia user. If your integration requires higher level permissions, talk to your Accessia representative

### **How to set up API integrations**

To set up a custom API integration:

1. Go to the **Integrations** tab
2. Under **Available integrations**, find the **API Integration** and click ‘Add’
3. Name the integration
4. Copy the following fields:
   * Integration ID
   * Authentication URL
   * Secret

{% hint style="info" %}
Note that the Secret will only be shown once. You can generate a new Secret at any time, but doing so will invalidate the previous Secret
{% endhint %}

1. On the Accessia portal, click ‘Save’
2. [Authenticate the custom API integration](#authenticate-the-custom-api-integration)
3. [Exchange your Identity token for your Access and Refresh tokens](#exchange-your-identity-token-for-your-access-and-refresh-tokens)
4. [Use your Access token and Bearer token authentication against Accessia’s API](#use-your-access-token-and-bearer-token-authentication-against-accessias-api)

#### Authenticate the custom API integration

Use the copied Integration ID, Authentication URL, and Secret to get Access and Refresh tokens that you can pass to Accessia

Here is the simplified flow:

<img src="/files/QBN4Rgq6lu30Z3o1K3N4" alt="" width="563">

You’ll need to sign an identity JWT on your side using the Secret provided during setup. The signing algorithm is **HMAC with SHA-256** and should include the following fields:

* iat - Issued At Time - UTC timestamp of when this token was issued
* exp - Expiry - UTC timestamp for when this token is valid until. We recommend that this is a few minutes after the value of iat
* jti (optional) - JWT ID - Unique identifier for this Identity token

{% hint style="info" %}
Note that the Secret is [base64 url encoded](https://developer.mozilla.org/en-US/docs/Glossary/Base64#url_and_filename_safe_base64) and you’ll need to decode it before use
{% endhint %}

Example of how you would generate this Identity token in Python:

```
import jwt
import base64
import time
import uuid

# Here you populate the values given to you during setup
INTEGRATION_DATA = {
    "integrationId": "<integrationId>",
    "secret": "<urlSafeBase64Secret>",
    "authenticationUrl": "<authenticationUrlValue>"
}
# you will need to sign a simple JWT with the shared secret. This JWT will be used as an Identity token to confirm who is requesting the Access and Refresh tokens
IDENTITY_TOKEN = jwt.encode(
  {
    "iat" : int(time.time()),
    "exp" : int(time.time()) + 300, # 5 minutes after creation
    "jti" : str(uuid.uuid4())
  },
  base64.urlsafe_b64decode(INTEGRATION_DATA["secret"]),
  "HS256"
)
```

#### Exchange your Identity token for your Access and Refresh tokens

To exchange your Identity token for your Access and Refresh tokens, execute a POST request against the following URL:

```jsx
**<authenticationUrlValue>/exchange/integration**
```

The body of this request should be JSON containing:

* “token” - Your Identity token
* “integrationId” - The custom Integration ID shared with you at setup

As a response you’ll get a JSON body containing:

* “accessToken” - JWT you can use to access Accessia APIs
* “refreshToken” - JWT you can use to obtain new Access tokens
* “expiresIn” - How long your Access token will be valid for in seconds (default 21600)
* “domain” - The domain of your Accessia deployment
* “accessiaApisUrl” - URL against which you can execute your requests

Example Python implementation:

```
import requests
# here we make the request to exchange an identity token for Access and refresh tokens
integrationExchangeResponse = requests.post(
  f"{INTEGRATION_DATA['authenticationUrl']}/exchange/integration",
  json={
      "token" : IDENTITY_TOKEN,
      "integrationId" : INTEGRATION_DATA["integrationId"]
  }
).json()
REFRESH_TOKEN = integrationExchangeResponse['refreshToken']
ACCESS_TOKEN_HEADER = f"Bearer {integrationExchangeResponse['accessToken']}"
ACCESSIA_APIS_URL = integrationExchangeResponse['accessiaApisUrl']
```

#### Use your Access token and Bearer token authentication against Accessia’s API

Now that you have your Access token you can use it in combination with [Bearer token authentication](https://datatracker.ietf.org/doc/html/rfc6750) against Accessia’s API

Example of how to get groups containing the word “Office” with your new token:

```
ACCESS_TOKEN_HEADER = f"Bearer {integrationExchangeResponse['accessToken']}"
groupResponse = requests.get(
  ACCESSIA_APIS_URL + "/groups",
  headers = { "Authorization" : ACCESS_TOKEN_HEADER},
  params = { "source" : "all", "filter" : "Office", "limit" : 25, "sortBy" : "name" }
)
```

{% hint style="info" %}
To find the APIs currently available for your deployment, go to **\<your\_domain>/api\_schema.json** where you’ll find an API spec. You can then load it in a tool such as Swagger for easy browsing

**Example of deployment URL**

<https://example.cloud.accessia.com/api_schema.json>
{% endhint %}

If you need to refresh your Access token or if you need multiple parallel Access tokens, you can execute a POST request against

```jsx
**<authenticationUrlValue>/refresh**
```

with a JSON body of:

* “refreshToken” - Your Refresh token

This will return the following response:

* “accessToken” - JWT you can use to access Accessia APIs
* “expiresIn” - Seconds your Access token will be valid for. Tokens are valid for 21600 seconds (six hours) by default. Contact Accessia if you need a different duration
* “domain” - The domain of your Accessia deployment
* “accessiaApisUrl” - URL against which you can execute your requests

Example:

```

refreshResponse = requests.post(
  f"{INTEGRATION_DATA['authenticationUrl']}/refresh",
  json={
      "refreshToken" : REFRESH_TOKEN,
  }
).json()
NEW_ACCESS_TOKEN_HEADER = f"Bearer {refreshResponse['accessToken']}"
```


# How to set up alerts

How to set up alerts in Accessia

1. Go to Accessia Portal > **Monitor** > **Configured alerts**
2. From the top left dropdown, select the site(s) to create a webhook alert for and click **+ New alert**
3. Name your alert and select whether it is a High, Medium, or Low level alert
4. Select a time range to which the webhook alert will apply&#x20;
5. Select the location(s) for which the webhook alert will apply
6. Select the event(s) that will trigger webhook alerts
7. Select the user(s) that will trigger webhook alerts for the selected events
8. Click **+ Add action** to set up how your alert will be sent

{% hint style="info" %}
If you create a Global alert for all sites, only event and user triggers will be configurable
{% endhint %}

### Sending alerts via Accessia app

1. From the **Add action** dialog, select **Notify users via Accessia app** and click **Next**
2. Type the name(s) of the users you want to receive notifications and click **Save**

### Sending alerts via Microsoft Teams

1. From the **Add action** dialog, select **Send Microsoft Teams webhook** and click **Next**
2. Follow the onscreen instructions to generate a Microsoft Teams URL
3. Paste the Microsoft Teams URL into the field provided and click **Save**

### Sending alerts via custom webhooks

1. From the **Add action** dialog, select **Send custom webhook** and click **Next**
2. Name your custom webhook and add its URL to the Webhook URL field
3. Complete the remaining fields and click **Save**

{% hint style="info" %}
You can turn a saved alert on or off using the toggle that appears alongside it on the **Configured alerts** page
{% endhint %}


# Contact support

For general support inquiries, email <support@accessia.com>. We'll respond within one working day

For urgent 24/7 support, call us. You can find our phone number by logging into [cloud.accessia.com](http://cloud.accessia.com) and clicking the question mark button <i class="fa-question">:question:</i> next to your profile picture in the upper right corner


# Enabling support access

Sometimes Accessis Support may need access to your account to troubleshoot any issues.\
\
To enable temporary access for Accessia Support:

1. Click the question mark button <i class="fa-question">:question:</i> next to your profile picture in the upper right corner
2. Click on **Allow temporary access** and then **Allow**

You can remove Accessia Support access to your account at any time by clicking **Revoke access now**


# Accessia Apps

Transform your access experience with Accessia for iOS or Android. Test and commission hardware with Accessia Installer

## Discover

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td>Accessia for iOS</td><td><a href="/pages/EuVqlTmkR6TtAy5TzSPB">/pages/EuVqlTmkR6TtAy5TzSPB</a></td><td><a href="/files/g4ZyZgjmfXmoEWbK7S5R">/files/g4ZyZgjmfXmoEWbK7S5R</a></td></tr><tr><td>Accessia for Android</td><td><a href="/pages/pC0CGz7p1YxElXWmS6WF">/pages/pC0CGz7p1YxElXWmS6WF</a></td><td><a href="/files/M2N7Bg0nI4MBuPynKgkH">/files/M2N7Bg0nI4MBuPynKgkH</a></td></tr><tr><td>Accessia Installer</td><td><a href="/pages/59itYhlxZRxodmidzueC">/pages/59itYhlxZRxodmidzueC</a></td><td><a href="/files/2nRtiN3sg4Wgcx2S9HTv">/files/2nRtiN3sg4Wgcx2S9HTv</a></td></tr></tbody></table>


# Accessia for iOS

Accessia is your key to a smarter workday

Navigate your workplace securely and easily with Accessia in your pocket and never worry about lost keys or codes again

Extend the Accessia experience to your guests with visitor invitations straight from your phone

Download Accessia on the [App Store](https://apps.apple.com/gb/app/accessia/id6459868536)

[![](/files/Wd6MykpB0s5H2GfuAvLh)](https://apps.apple.com/gb/app/accessia/id6459868536)


# Hands-free (UWB) unlock

{% embed url="<https://www.youtube.com/watch?ab_channel=Accessia&v=5QkNHQ_Exeo>" %}

When your organization has Ultra-wideband (UWB) enabled, you can set up UWB hands-free door unlock with a few simple steps.

{% hint style="info" %}
UWB access means you don’t have to have your phone in your hand when you want to unlock a door, you can keep your phone in your pocket.
{% endhint %}

1. Make sure that you have set up Accessia app with the correct permissions. To do this, in Accessia app go to Profile > Permissions and make sure each item is ticked
2. Tap the Accessia Reader with your phone. This will bring up a pairing dialog on your phone screen

<img src="/files/MgcV08C9knaTM67DEcZf" alt="" width="188">

3. From the pairing dialog, tap ‘Pair’
4. Your phone will show you a Bluetooth Pairing Request dialog, tap ‘Pair’ again
5. You’ll now see a screen that tells you UWB has been successfully enabled, tap 'Done'
6. You can now use UWB for hands-free unlock. Repeat the steps on each door with an Accessia Reader you want to be able to unlock hands-free


# Remote unlocking doors on iOS

You can unlock doors remotely via Accesia app if:

* You’re an admin at the door’s site and remote unlock has been enabled in the door’s behavior settings
* You’re a user with access to the door, and remote unlock has been enabled for all users with access in the door’s behavior settings

[Read more about enabling remote unlock on a door](/site-setup/adding-doors/door-settings)

## How to remote unlock a door via Accessia app

1. Go to the **Access** tab where all doors you’re able to unlock remotely are listed. Expand the list to full height if needed
2. If you’re allowed to remote unlock doors on more than one site, select the relevant site in the upper right corner of the list
3. Find the relevant door in the list and tap the lock icon button 🔒
4. Tap **Unlock** in the confirmation
5. When the door has successfully unlocked, the lock icon button 🔒 will turn green and show an unlock icon 🔓
6. If you don’t have access to the door at this time, an alert will notify you that the unlock failed

{% hint style="info" %}
The door will unlock for the duration specified in the door’s behavior settings. [Read more about door behavior](/site-setup/adding-doors/door-settings)
{% endhint %}

<div><figure><img src="/files/W9gbZxxGKI4Vw8wMIjMH" alt="" width="237"><figcaption></figcaption></figure> <figure><img src="/files/VpufzUCmuZhvHKSjvxyX" alt="" width="237"><figcaption></figcaption></figure> <figure><img src="/files/IJZbbADh86rVraHs53t8" alt="" width="237"><figcaption></figcaption></figure></div>


# Taking doors off schedule on iOS

Primary and secondary admins can take doors off schedule and return doors to schedule

When a door is taken off schedule on iOS it:

* Ignores the door lock schedule
* Is either locked or unlocked for the duration of the off-schedule session
* Is locked down as usual in the event of a lockdown
* Allows access to users according to their access permissions
* Automatically returns to schedule at a specified time
* Can be manually returned to schedule by an admin at any time
* Can be returned to schedule by an event trigger

{% hint style="info" %}
During a lockdown all doors will be locked down regardless of whether they are on or off schedule
{% endhint %}

> **Example**
>
> A receptionist needs to step away from the reception for a moment, but the front door is unlocked. They can quickly take the door off schedule and lock it, so that the building is secure. Users with access permissions can still use a valid credential for access while the door is locked off schedule

## How to take a door off schedule

1. Go to the **Access** tab where all doors that you have admin controls for are listed. Expand the list if needed
2. If you are an admin for more than one site, select the relevant site in the upper right corner of the list
3. Find the relevant door and tap its name
4. Tap **Door State**, which will be set to **On Schedule**
5. Specify whether the door should be locked or unlocked while it’s off schedule and when it should return to schedule
6. Tap **Save**
7. In the confirmation dialog, tap **Take off Schedule**
8. The door has been taken off schedule. Check that the Door State is **Off Schedule - Locked** or **Off schedule - Unlocked**

<div><figure><img src="/files/JCGmYXJMBQsRRriINeoh" alt="" width="237"><figcaption></figcaption></figure> <figure><img src="/files/yh0rxTCGZLGDkcZecY5i" alt="" width="237"><figcaption></figcaption></figure> <figure><img src="/files/rBcdueFkZaNUkQewCLEu" alt="" width="237"><figcaption></figcaption></figure></div>

## How to return a door to schedule

An off-schedule door can be manually returned to schedule at any time

1. Go to the **Access** tab where all doors that you have admin controls for are listed. Expand the list if needed
2. If you are an admin for more than one site, select the relevant site in the upper right corner of the list
3. Find the relevant door and tap its name
4. Tap **Door State**, which will be set to **Off Schedule - Locked** or **Off Schedule - Unlocked**
5. In the confirmation dialog, tap **Return to Schedule**
6. The door has been returned to schedule. Check that the **Door State** is **On Schedule**

<div><figure><img src="/files/OuGDpZTKetSFGtRlE0TM" alt="" width="237"><figcaption></figcaption></figure> <figure><img src="/files/O9JsRUqlF95Ypimg55xr" alt="" width="237"><figcaption></figcaption></figure></div>


# Troubleshooting mobile unlock

### **Scenario: Mobile access is not working**

1. Make sure the user has been allowed access to the intended room ([Go to guide](/setting-access/access-schedule-basics))
2. In Accessia app, go to **Profile** > **Permissions** and check there are no tasks to complete

### **Scenario: Bluetooth-based access (tapping the Reader) is working, but the phone doesn’t offer to pair for hands-free access**

1. Make sure **hands-free unlock (UWB)** is enabled for the door ([Go to guide](/site-setup/adding-doors/set-up-hands-free-uwb-unlock))
2. Make sure you’re using a compatible iPhone (iPhone 11 or newer, excluding iPhone SE and iPhone 16e)

### **Scenario: Accessia app pairs with the door for hands-free unlock, but fails to unlock the door**

1. Follow the guide to [reset the UWB pairing](/accessia-app/accessia-for-ios/troubleshooting-mobile-unlock/reset-uwb-pairing)


# Reset UWB pairing

If Accessia app has paired with a Reader but the pairing fails, you’ll need to reset the UWB pairing

1. Open **Settings** on your phone
2. Go to **Bluetooth**
3. Under **My devices,** find the failing device pairing. It will be called ACCESSIA and there will be an ℹ️ icon next to the device name
4. Tap the ℹ️ icon
5. Tap **Forget This Device**
6. From your phone’s Settings, toggle Bluetooth off and then on again (note that this needs to be done from the Settings app, not Control Center)
7. Return to Accessia app and try to pair again with the Reader


# Accessia SDK

Accessia’s SDK provides services for:

* Authentication with Accessia’s cloud backend
* Communication with nearby Accessia doors for access
* Monitoring user location while on site

## Requirements

The SDK requires the following `Background Modes` capabilities:

* `Location updates`
* `Uses Bluetooth LE accessories`
* `Uses Nearby Interaction`

And requires the respective Privacy strings to be defined i.e. `NSBluetoothAlwaysUsageDescription`, `NSLocationAlwaysAndWhenInUseUsageDescription`, `NSLocationWhenInUseUsageDescription`, and `NSNearbyInteractionUsageDescription`.

## Configuration

1. At the entry point of your application call `AccessiaSDK.configure(delegate:logger:)`
2. To authenticate you must provide a pair of bearer tokens, namely authentication and refresh, to `AccessiaSDK.signIn(customerHost:accessToken:refreshToken:expiresIn:)`
3. Call `AccessiaSDK.startServices()` to start the location service and door service

## Get started

Speak with your Accessia account manager or partner for access to the full SDK


# Accessia for Android

Accessia is your key to a smarter workday

Navigate your workplace easily and securely with Accessia on your mobile and never worry about lost keys or codes again

Extend the Accessia experience to your guests with visitor invitations straight from your phone

Get Accessia on the [Play Store](https://play.google.com/store/apps/details?id=com.accessia.accessia\&hl=en_GB)

[![](/files/CdfEEl2vQYuo0NzfsHex)](https://play.google.com/store/apps/details?id=com.accessia.accessia\&hl=en_GB)


# Remote unlocking doors on Android

You can unlock doors remotely via Accesia app if:

* You’re an admin at the door’s site and remote unlock has been enabled in the door’s behavior settings
* You’re a user with access to the door, and remote unlock has been enabled for all users with access in the door’s behavior settings

[Read more about enabling remote unlock on a door](/site-setup/adding-doors/door-settings)

## How to remote unlock a door via Accessia app

1. Go to the **Access** tab where all doors you’re able to unlock remotely are listed. Expand the list to full height if needed
2. If you’re allowed to remote unlock doors on more than one site, select the relevant site in the upper left corner of the list
3. Find the relevant door in the list and tap the lock icon button 🔒
4. Tap **Unlock** in the confirmation
5. When the door has successfully unlocked, the lock icon button 🔒 will turn green and show an unlock icon 🔓
6. If you don’t have access to the door at this time, an alert will notify you that the unlock failed

{% hint style="info" %}
The door will unlock for the duration specified in the door’s behavior settings. [Read more about door behavior](/site-setup/adding-doors/door-settings)
{% endhint %}

<div><figure><img src="/files/tNz06EQwhxRxHEfjSApO" alt="" width="375"><figcaption></figcaption></figure> <figure><img src="/files/xscwdxretrkzftA9eDHB" alt="" width="375"><figcaption></figcaption></figure> <figure><img src="/files/6SsZ2TbqOMEe2OdCL1vD" alt="" width="375"><figcaption></figcaption></figure></div>


# Taking doors off schedule on Android

Primary and secondary admins can take doors off schedule and return doors to schedule

When a door is taken off schedule on Android it:

* Ignores the door lock schedule
* Is either locked or unlocked for the duration of the off-schedule session
* Is locked down as usual in the event of a lockdown
* Allows access to users according to their access permissions
* Automatically returns to schedule at a specified time
* Can be manually returned to schedule by an admin at any time
* Can be returned to schedule by an event trigger

{% hint style="info" %}
During a lockdown all doors will be locked down regardless of whether they are on or off schedule
{% endhint %}

> **Example**
>
> A receptionist needs to step away from the reception for a moment, but the front door is unlocked. They can quickly take the door off schedule and lock it, so that the building is secure. Users with access permissions can still use a valid credential for access while the door is locked off schedule

## How to take a door off schedule

1. Go to the **Access** tab where all doors that you have admin controls for are listed. Expand the list if needed
2. If you are an admin for more than one site, select the relevant site in the upper left corner of the list
3. Find the relevant door and tap its name
4. The **Door State** will be set to **On Schedule**
5. Tap **Take door off schedule**
6. Specify whether the door should be locked or unlocked while it’s off schedule and when it should return to schedule
7. Tap **Save**
8. The door has been taken off schedule. Check that the Door State is **Off Schedule - Locked** or **Off schedule - Unlocked**

<div><figure><img src="/files/yO9WaDETx6pUrPgNg6Pq" alt="" width="188"><figcaption></figcaption></figure> <figure><img src="/files/vfqi5S2vqltbU19ae1U7" alt="" width="188"><figcaption></figcaption></figure></div>

## How to return a door to schedule

An off-schedule door can be manually returned to schedule at any time

1. Go to the **Access** tab where all doors that you have admin controls for are listed. Expand the list if needed
2. If you are an admin for more than one site, select the relevant site in the upper right corner of the list
3. Find the relevant door and tap its name
4. The **Door State** will be set to **Off Schedule - Locked** or **Off Schedule - Unlocked**
5. Tap **Return to Schedule**
6. The door has been returned to schedule. Check that the Door State is **On Schedule**

<figure><img src="/files/ge4M51acYXA0Zp0wawJ9" alt="" width="188"><figcaption></figcaption></figure>


# Accessia SDK

Accessia’s SDK provides services for:

* Authentication with Accessia’s cloud backend
* Communication with nearby Accessia doors for access
* Monitoring user location while on site

## Requirements

The SDK will add some required permissions to your third party app:

* **`INTERNET`** Required to talk to Accessia Cloud
* **`POST_NOTIFICATIONS`** Required for location services & mobile access. The foreground service must surface a notification when it is started. This can be muted by the user
* **`BLUETOOTH`** Required for location services & mobile access
* **`BLUETOOTH_ADMIN`** Used by the PermissionRequester utility to turn Bluetooth on for location services, if required and allowed by the user
* **`BLUETOOTH_SCAN`** Required for location services & mobile access
* **`BLUETOOTH_CONNECT`** Required for mobile access
* **`ACCESS_COARSE_LOCATION`** Required for location services & mobile access
* **`ACCESS_FINE_LOCATION`** Required for location services & mobile access
* **`ACCESS_BACKGROUND_LOCATION`** Required for location services & mobile access. This is needed for geofencing and starting foreground services in the background
* **`FOREGROUND_SERVICE`** Required for location services & mobile access
* **`FOREGROUND_SERVICE_LOCATION`** Required for location services & mobile access
* **`RECEIVE_BOOT_COMPLETED`** Required for location services & mobile access. On boot completed, we reset the geofences and check if we need to restart the services, based on geofence location
* **`NFC`** Required for mobile access
* **`VIBRATE`** Required for mobile access

It will also declare usage of the following features:

* **`android.hardware.bluetooth_le`:** Required for location services & mobile access
* **`android.hardware.nfc.hce`:** Required for mobile access

You may need to update your Google Play store listing for some of these, such as foreground service location and background location

## Configuration

1. At the entry point of your application call `AccessiaSDK.configure(config: AccessiaConfig, callbacks: AccessiaCallbacks, logger: Timber.Tree? = null)`
2. To authenticate you must provide a pair of bearer tokens, namely authentication and refresh, to `AccessiaSDK.signIn(context: Context, customerHost: String, accessToken: String, refreshToken: String, expiresIn: Int)`
3. Call `AccessiaSDK.startServices(context: Context)` to start the location service and door service

## Get started

Speak with your Accessia account manager or partner for access to the full SDK


# Accessia Installer

Test your hardware with ease with Accessia Installer

Accessia Installer makes hardware testing, commissioning, and reporting easy. The app guides you through all hardware tests, let you commission with one click, and then automatically generates a commission report

### Downloading Accessia Installer <a href="#downloading-the-installer-app" id="downloading-the-installer-app"></a>

1. On an Android device (tablets are strongly recommended), download Accessia Installer from the [Play Store](https://play.google.com/store/apps/details?id=com.accessia.installer)
2. Enable Bluetooth and location services on your device
3. Allow Accessia Installer to use Bluetooth and location services on your device. We use these to connect with the hardware during testing and commissioning
4. Log in to your Accessia account. If your account is associated with multiple organizations, select the organization you want to test and commission hardware for

​

### Testing a device with Accessia Installer <a href="#testing-a-device-with-the-installer-app" id="testing-a-device-with-the-installer-app"></a>

1. Go to the site where you want to test hardware and locate the device you want to test. Devices that are not fully tested are orange on the floor plan

{% hint style="info" %}
Always test Hubs before testing connected doors
{% endhint %}

1. When you're onsite and close to the device you want to test, open Accessia Installer
2. Click on the relevant floor in Accessia Installer and locate the device on the floor plan
3. Click on the device
4. In the bottom right corner, click **View tests**

{% hint style="info" %}
If Accessia Installer doesn't connect with the device, move closer to the device and try again
{% endhint %}

1. Accessia Installer will guide you through all tests. Stay close to the device while running the tests
2. When a device has passed all tests, it will show as purple on the floor plan

​

### Commissioning a Hub with Accessia Installer <a href="#commissioning-a-hub-with-the-installer-app" id="commissioning-a-hub-with-the-installer-app"></a>

1. Go to the site where you want to test hardware and locate the Hub you want to commission. Fully tested but uncommissioned hardware is purple on the floor plan

{% hint style="info" %}
Commissioning a Hub will automatically commission all doors linked to it. You can't commission doors individually
{% endhint %}

1. When you're onsite and close to the Hub you want to commission, open Accessia installer
2. Click on the relevant floor in Accessia Installer and locate the Hub on the floor plan
3. Click on the Hub
4. In the bottom right corner, click **Commission**

{% hint style="info" %}
If Accessia Installer doesn't connect with the device, move closer to the device and try again
{% endhint %}

1. Confirm **Commission**
2. Your Hub and all connected doors are now commissioned and will show as green on the floor plan

<figure><img src="/files/q3ncyB1JOZDuVCvlnhsO" alt="" width="563"><figcaption></figcaption></figure>


# Hub tests

Use Accessia Installer to quickly carry out the following Hub tests and to generate a commissioning report with all results

<table><thead><tr><th width="199.8984375">Test</th><th>Description</th><th>Results</th></tr></thead><tbody><tr><td>Fail secure locks</td><td>Automatically checks if any door locks are set to fail secure (power to open). If they are, you'll be asked to confirm that this is correct</td><td><ul><li>No fail secure locks found - Pass</li><li>Fail secure locks found, setup confirmed (Yes) - Pass</li><li>Fail secure locks found, setup not confirmed (No) - Fail</li></ul></td></tr><tr><td>Cables identified</td><td>Confirm that all cables are individually labeled at the terminal end</td><td><ul><li>Yes - Pass</li><li>No - Fail</li></ul></td></tr><tr><td>Ferrule terminations</td><td>Confirm that ferrule terminations have been used</td><td><ul><li>Yes - Pass</li><li>No - Fail</li><li>N/A - Pass</li></ul></td></tr><tr><td>Mains power</td><td>Confirm that the mains power cables have been connected correctly</td><td><ul><li>Yes - Pass</li><li>No - Fail</li></ul></td></tr><tr><td>Mains fuse</td><td>Confirm that the correct 3A mains fuse has been installed</td><td><ul><li>Yes - Pass</li><li>No - Fail</li></ul></td></tr><tr><td>Fire alarm interface</td><td>Confirm that the fire alarm interface has been installed correctly</td><td><ul><li>Yes - Pass</li><li>No - Fail</li><li>N/A - Pass</li></ul></td></tr><tr><td>Fire input</td><td>Automatically checks whether the fire input is currently asserted</td><td><ul><li>Fire input not currently asserted - Pass</li><li>Fire input currently asserted - Fail</li></ul></td></tr><tr><td>DEOL resistors</td><td><p>Automatically measures the resistance value on each channel input</p><p></p><p>The installer should sense check these measurements</p></td><td><ul><li>Automatically passes, measurements are included in the generated commissioning report</li></ul></td></tr><tr><td>Termination resistors</td><td>Confirm that the RS485 termination resistors have been fitted</td><td><ul><li>Yes - Pass</li><li>No - Fail</li></ul></td></tr><tr><td>Tamper detection</td><td>Close and then open the Hub door to check that the Hub door position indicator and tamper detection work as intended</td><td><ul><li>Hub door position indicator identifies door position correctly - Pass</li><li>Hub door position indicator identifies door position incorrectly - Fail</li></ul></td></tr><tr><td>Controller network</td><td>Automatically checks if the Hub is connected to the network. If it isn't, you'll be asked to confirm that this setup is correct</td><td><ul><li>Hub connected to network - Pass</li><li>Hub not connected to network, setup confirmed (Yes) - Pass</li><li>Hub not connected to network, setup not confirmed (No) - Fail</li></ul></td></tr><tr><td>Connected readers</td><td>Automatically checks the Hubs is connected to all configured Accessia Readers and no additional Accessia Readers Note that this test does not include third-party readers</td><td><ul><li>Hub is connected to readers - Pass</li><li>Hub is not connected to readers - Fail</li></ul></td></tr><tr><td>Input faults</td><td>Automatically checks for input faults</td><td><ul><li>No input faults detected - Pass</li><li>Input faults detected - Fail</li></ul></td></tr></tbody></table>


# Door tests

Run the following tests on your doors with Accessia Installer and share a commissioning report with your client

<table data-full-width="false"><thead><tr><th width="200.4765625">Test</th><th>Description</th><th>Results</th></tr></thead><tbody><tr><td>Reader connection</td><td>Confirm that the Reader beeps and flashes green when running the test</td><td><ul><li>Yes - Pass</li><li>No - Fail</li></ul></td></tr><tr><td>Lock state</td><td>Confirm that the door locks and then unlocks correctly</td><td><ul><li>Yes - Pass</li><li>No - Fail</li></ul></td></tr><tr><td>Emergency exit</td><td>Confirm that the door locks and then unlocks correctly when emergency exit is pressed</td><td><ul><li>Yes - Pass</li><li>No - Fail</li></ul></td></tr><tr><td>REX device</td><td>Asks the installer to activate the installed REX device and automatically checks it works as intended</td><td><ul><li>REX activation works as intended - Pass</li><li>REX activation does not work as intended - Fail</li></ul></td></tr><tr><td>Door timings</td><td><p>Automatically measures the door timings </p><p></p><p>The installer should sense check these measurements</p></td><td><ul><li>Automatically passes, measurements are included in the generated commissioning report</li></ul></td></tr><tr><td>Tamper detection</td><td>Automatically checks whether the Reader is reporting a tamper event</td><td><ul><li>No tamper event detected - Pass</li><li>Tamper event detected - Fail</li></ul></td></tr><tr><td>Exit device height</td><td>Confirm that emergency release and exit buttons are fitted at the correct DDA height</td><td><ul><li>Yes - Pass</li><li>No - Fail</li></ul></td></tr><tr><td>Voltage at lock</td><td>Measure and report the voltage at the lock</td><td><ul><li>Voltage within expected range - Pass</li><li>Voltage not within expected range - Fail</li></ul></td></tr></tbody></table>


# Commissioning reports

When you commission Hubs and doors with the Accessia Installer, a commissioning report is automatically generated and made available on the Portal

## What is included in the commissioning report

The commissioning report includes information on:

* Which Hubs and doors have been commissioned
* Who has commissioned the devices
* When and where the devices were commissioned
* All test results

<figure><img src="/files/LyIUp5iFfr6LJB6PliXQ" alt="" width="375"><figcaption></figcaption></figure>

## Reviewing commissioning reports on the Portal

Commissioning reports are automatically made available on the Portal

1. Go to **Reports > Site**&#x20;
2. Go to **Shareable reports**
3. Click on the commissioning report you want to review


# Accessia hardware

Everything you need for cloud access control and more

## Discover

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>AI Security Hub</td><td><a href="/pages/TkN67HN9lROcAlMTftsO">/pages/TkN67HN9lROcAlMTftsO</a></td><td><a href="/files/jntxcnAa2dVZhnGca5oh">/files/jntxcnAa2dVZhnGca5oh</a></td></tr><tr><td>Accessia Reader</td><td><a href="/pages/EDmQEP2EEC6iDM6fZTaP">/pages/EDmQEP2EEC6iDM6fZTaP</a></td><td><a href="/files/QBchEXBCc0PBOWXV09Wb">/files/QBchEXBCc0PBOWXV09Wb</a></td></tr><tr><td>Cloud Converter for S2 Netbox*</td><td><a href="/pages/TM3rgg7gFjpb1CHqILr9">/pages/TM3rgg7gFjpb1CHqILr9</a></td><td><a href="/files/g7l4Iu2MpqpDNMhb1Dep">/files/g7l4Iu2MpqpDNMhb1Dep</a></td></tr></tbody></table>

<sub>\*</sub><sub>*Accessia is not an authorized partner of LenelS2. Accessia Cloud Converter for S2 NetBox is not approved or supported by LenelS2*</sub>


# Datasheets

All Accessia datasheets in one place

## AI Security Hub datasheet

{% file src="/files/pjvjqG6S3MHqeWETEd4i" %}

## Hub v1 datasheet

{% file src="/files/q5PaAIUuolded2O3f9Ot" %}

## Accessia Reader datasheet

{% file src="/files/g0e6xF3v5aFZYXr85zo4" %}

## Cloud Converter for S2 datasheet

{% file src="/files/1rB64jhDmlCZUhu60BaY" %}


# AI Security Hub / Hub v1

Accessia AI Security Hub and Security Hub v1 are enterprise-grade 4 door controllers that are easy to commission, even offline

<figure><img src="/files/hW4pTdQx9h6FTNnS77Nk" alt="" width="188"><figcaption></figcaption></figure>

## Get started

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Datasheet</td><td><a href="/pages/QpOmXv79ABnYXAjCBuUk">/pages/QpOmXv79ABnYXAjCBuUk</a></td></tr><tr><td>Installation</td><td><a href="/pages/UdgWdY9T28YSZf9YvgzH">/pages/UdgWdY9T28YSZf9YvgzH</a></td></tr><tr><td>Mounting</td><td><a href="/pages/v9w7iJbHN4VIVIp0ddHU">/pages/v9w7iJbHN4VIVIp0ddHU</a></td></tr></tbody></table>


# AI Security Hub / Hub v1 datasheet

See the datasheet for AI Security Hub and Security Hub v1 specifications and certifications

## AI Security Hub

{% file src="/files/pjvjqG6S3MHqeWETEd4i" %}

## Security Hub v1

{% file src="/files/q5PaAIUuolded2O3f9Ot" %}


# AI Security Hub / Hub v1 installation

## **Getting started with AI Security Hub or Security Hub v1**

Document Number 490-0001-01

Revision 07 – 27 October 2025

{% file src="/files/Q0YB7HVQpJ6bNz0C51UZ" %}

Document Number 490-0003-01

Revision 04 – 27 October 2025

{% file src="/files/shU0QUs173xwT6WU3t1d" %}

### **What’s in the box?**

* Accessia Hub
* Hub key

### **What you’ll need**

**Equipment**

* 4 x 5mm diameter (no. 10) panhead screws and wall anchors suitable for the wall surface the Hub will be mounted on
* Tools for mounting, wiring, and knocking out and deburring cable apertures
* Appropriately sized conduit and bushes for all wiring external to the Hub
* 3mm flat-head screwdriver for wiring terminals

**Network and AC mains connection**

The Hub requires a connection to the local area network using 100BaseT Ethernet. This local area network must permit HTTPS connections to the internet. The Hub will automatically use this connection to establish a secure connection to Accessia’s cloud

### **Wiring guide**

* For the AC mains connection, see [Connecting mains and battery power](/hardware/ai-security-hub-hub-v1/mains-and-battery-power). Make sure that the AC mains is isolated before starting any wiring activities inside the Hub enclosure
* All other wiring in the system is safety extra low voltage (SELV) and should not be connected to any voltage greater than 30 VDC. The wiring to the DC power input and battery connection terminals is already provided using 16AWG wire. For the remaining connections, use a wire gauge in the range 14 to 24 AWG, making sure that the wire gauge is suitable for the maximum current being conducted
* The network connection must be made using Cat5 (or better) cable

### **1.** [**Mounting guide**](/hardware/ai-security-hub-hub-v1/mounting-the-hub)

### **2.** [**Connecting mains and battery power**](/hardware/ai-security-hub-hub-v1/mains-and-battery-power)

### **3. Connecting a channel**

The Hub supports up to four channels. For each channel, there are connections for:

* Up to two OSDP Readers (including RS485 signal pair and 12VDC power supply)\*
* One lock
* Two inputs with dual end-of-line (DEOL) monitoring support

Two groups of terminals are provided for the lock: wet and dry

\**2 readers per channel coming soon*

Also see: [Channel output power guide](/hardware/ai-security-hub-hub-v1/inputs-and-outputs/channel-output-power)

#### **3.1** [**Connecting Readers**](/hardware/ai-security-hub-hub-v1/connecting-readers)

#### **3.2** [**Connecting a lock**](/hardware/ai-security-hub-hub-v1/connecting-locks)

#### **3.3** [**Connecting an input**](/hardware/ai-security-hub-hub-v1/inputs-and-outputs/channel-inputs)

### **4.** [**Connecting the fire alarm interface (FAI)**](/hardware/ai-security-hub-hub-v1/inputs-and-outputs/fire-alarm-interface)

### **5.** [**Connecting auxiliary IO**](/hardware/ai-security-hub-hub-v1/inputs-and-outputs/auxiliary-io)

### **6.** [**Connecting the intruder alarm interface**](/hardware/ai-security-hub-hub-v1/inputs-and-outputs/intruder-alarm-interface)

### **7.** [**Learn about visual statuses**](/hardware/ai-security-hub-hub-v1/hub-visual-states)

## **Additional information**

### **Compatibility**

* Cloud: the Hub is only compatible with Accessia’s cloud
* Readers: the Hub is compatible with OSDP Readers

### **Programming**

Programming and configuration of the system can be done using either Accessia Installer app or the Portal

### **Software**

System software is automatically updated when necessary by Accessia’s cloud. To check the current software version, check Accessia Installer app or [Accessia Portal](http://cloud.accessia.com/)

### **Operating conditions**

AC mains input: 100 – 240VAC 50/60Hz, 3A

Operating temperature range: 32°F \~ 120°F / 0 \~ 49oC

Humidity: 20 - 90% RH non-condensing

### **Compliance**

Compliance Model CTL01A

#### **FCC**

This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation\
\
Contains FCC ID: S9NBNRGM0AL

#### **UL294/UL293 Access control performance levels**

Destructive attack: Level I (Local Level III for reader RDR01A)

Line security: Level II

Endurance: Level IV

Standby Power, 60W output: Level II

Standby Power, 24W output: Level III


# Mounting the Hub

## Before you start

* Make sure the wall you want to mount the Hub on is indoors and vertical
* Choose a good position for the Hub in an area free from excessive temperature or moisture and where the ventilation holes will not be blocked

## How to mount the Hub

1. Use the key to unlock and then open the enclosure door. Optionally, you can slide the door upwards to remove it
2. Knock out the cable apertures where necessary for the external wiring and remove any burrs
3. Fit appropriately sized bushes to the cable apertures used for the external wiring and conduit
4. Secure the Hub to the wall using four 5mm diameter (no. 10) screws and wall anchors appropriate for the wall material, bearing in mind the weight of the Hub. There are four mounting holes for securing the Hub to the wall on the inside rear wall of the Hub enclosure

<figure><img src="/files/7sMowxMK0FbnduIP6EO5" alt="" width="362"><figcaption></figcaption></figure>


# Mains and battery power

## **AC mains connection**

* The Hub must be connected to an isolation device and current interruption device rated at no greater than 6A
  * This connection must only be made by a competent person and must comply with the relevant national and local electrical codes
  * This connection must be made to the AC mains connection terminals (Figure 1 and Figure 2). Do not connect AC mains to any other terminals
* All other terminals and wiring inside the enclosure are safety extra low voltage (SELV) and the AC wiring must be kept physically separated from them. The AC wiring must not share an enclosure aperture with any other wiring. If not using a conduit, fit a cable gland to the selected aperture to secure the AC wiring in place and protect it from damage
* The Hub enclosure must be connected to mains earth using the terminal block provided
* For compliance with electrical codes, the cable must use conductors of minimum 2.5mm2 or, if using a a non-flexible metal conduit, the conductors must be a minimum of 1.5mm2

{% columns %}
{% column width="50%" %}
![Figure 1: AC mains wiring](/files/ASAwt0V3kQnYEeOH5t64)

{% endcolumn %}

{% column %} <img src="/files/YKU9Nrpy7LWBzEtmlYCa" alt="Figure 2: Inside the enclosure" width="375">
{% endcolumn %}
{% endcolumns %}

## **Battery connection**

Optional backup power can be provided using a 12V sealed lead acid battery. Only use a 12V battery approved to IEC 60896 and rated for a charging current up to 1.7A and a load current up to 8A

{% hint style="info" %}
Accessia recommends using Yuasa model NP12-12G which has a rated capacity of 12Ah
{% endhint %}

Connect the battery to the Hub using the labeled terminals and the wires supplied

* The red wire is positive and the black wire is negative
* The supplied wires include a thermistor for monitoring the battery temperature
* Make sure to place the battery securely in the base of the enclosure with the terminals facing upwards


# Network requirements

|                         | Security Hub v1   | AI Security Hub    |
| ----------------------- | ----------------- | ------------------ |
| **Network requirement** | 100BaseT Ethernet | 1000BaseT Ethernet |

* This local area network must permit HTTPS connections to the internet
* The Hub will automatically use this connection to establish a secure connection to Accessia’s cloud

{% hint style="info" %}
Note that the network connection is in a different position inside the enclosure dependent upon whether the Hub is a Security Hub v1 or an AI Security Hub
{% endhint %}

<figure><img src="/files/wiCHtsEadXTdukAo9uYt" alt="" width="375"><figcaption><p>Figure 1: Inside a Hub v1 enclosure</p></figcaption></figure>


# Connecting Readers

The AI Security Hub and Security Hub v1 support Accessia Readers and third party OSDP readers

The RS-485 connections to the Readers must use a shielded twisted pair with characteristic impedance in the range of 100 to 120 Ohms

* For example, Belden 8723 cable is suitable, provided that the two RS-485 connections share a single twisted pair
* The RS485 twisted pair must be terminated at both ends with a 120 Ohm +/- 1% resistor
* The Hub has this resistor built in and it is optionally connected using the slide switch. If the Hub is at one end of the Reader wiring (this is the usual case, see Figure 1 and Figure 2) slide the switch to turn the line termination on. If the Hub is in the middle of the Reader wiring (this is possible if two readers are connected to the same channel, coming soon, see Figure 3) then slide the switch to turn the line termination off
* Connect the shield of the cable to earth using the labelled earth post inside the enclosure

![Figure 1: Channel with single Reader](/files/YwCU6XcaHYhTxiM1EwmF)

![Figure 2: Channel with two Readers, shared cable (coming soon)](/files/Y7tCgOy3eI6QQJGreGAz)

![Figure 3: Channel with two Readers, separate cables (coming soon)](/files/QLCBAHDYGW7AO9vfhR6Y)


# Connecting locks

For locks with their own power supply, use the dry terminals. These are implemented using a single-pole-double-throw relay and are electrically isolated from the rest of the system (including the other locks). The dry contacts are rated to a maximum of 5A and 30 VDC (Figure 1)

![Figure 1: Lock with its own power supply](/files/XZDQ17wZBh0j5ZEUh33R)

For locks without their own power supply, use the wet outputs. These switch power directly to the lock, using either 12 VDC or 24 VDC. Select the voltage using the slide switch on the Hub. Note that Channels 1 and 2 must use the same lock voltage and, similarly, Channels 3 and 4 must use the same lock voltage. Do not supply 24V to a lock that is intended for 12V as this may damage the lock. A red warning indictor adjacent to the wet terminals lights up whenever 24V is selected for the lock (Figure 2)

![Figure 2: Lock powered directly from the Hub](/files/SZj69VgInL7G2DbZU7YG)

Set the slide switch on the Hub to match the mode of lock that has been connected: either power-to-lock (fail safe) or power-to-open (fail secure)


# Inputs and outputs

The AI Security Hub and Security Hub v1 support a number of different inputs and outputs

With the Hub's inputs and outputs you can install request-to-exit (REX) buttons, door position indicators, fire alarm interfaces and much more

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Channel inputs</td><td><a href="/pages/vhuo5qP1vPeNMeNj6JP6">/pages/vhuo5qP1vPeNMeNj6JP6</a></td></tr><tr><td>Channel output power</td><td><a href="/pages/mGqT9t9CzC6ioIi3yQnP">/pages/mGqT9t9CzC6ioIi3yQnP</a></td></tr><tr><td>Auxiliary IO</td><td><a href="/pages/6BWNGwYavrRm4n7Mbis2">/pages/6BWNGwYavrRm4n7Mbis2</a></td></tr><tr><td>Fire alarm interface</td><td><a href="/pages/1YKnBDfaXVla5RgTcPry">/pages/1YKnBDfaXVla5RgTcPry</a></td></tr><tr><td>Intruder alarm interface</td><td><a href="/pages/mGradGxDluJKXY3x9su9">/pages/mGradGxDluJKXY3x9su9</a></td></tr></tbody></table>


# Configuring inputs and outputs

The Accessia platform allows you to configure polarity of both inputs and outputs in either software on the Cloud Converter, or in hardware on the AI Security Hub. When connecting to relay outputs, you can choose between using the NC or NO output.

Input devices such as door position sensors and exit buttons are available in either NC or NO versions, or feature both NC and NO outputs.

Locks are available in different types such as maglocks, which require power to lock the door, or electric strikes, which can require power to lock the door (fail safe), or power to open the door (fail secure).

Reading and understanding this document will help you wire and configure your access control system for proper functionality.

{% hint style="info" %}
Choosing the right wiring options and software configuration is essential to ensure compatibility with the chosen hardware and for correct functioning in cases of broken cables or power loss etc.&#x20;
{% endhint %}

## Inputs <a href="#inputs" id="inputs"></a>

#### Door position sensors

Usually, the 'normal' state of a door is considered to be in the secure state, i.e. with the door closed. \
\
This might not match the wording shown on the output of the sensor, for example:<br>

* For a reed switch type contact, the normal state would be with the door open
* For a maglock field strength sensor, normal is typically when the maglock is not energized, for example  when the door is open and unlocked

#### Other inputs

For a button, the normal state is when the button is not pressed. Understanding this helps with the below:

* For a REX button, typically the button offers NC and NO outputs. Usual configuration is to connect the NO output into the input on the controller, and choose the option **Door release request closes circuit (NO)**
* For a presence detector, the sensible option is **Presence detection closes circuit (NO)**. This ensures that, if a presence detector fails (for example, in the case that even when people are present, the input stays open), all door openings will result in an alert. This might be the opposite of typical usage of a PIR sensor in an alarm sensor, where it is desirable for a cable break to trigger the alarm, so **Presence detection opens circuit (NC)** would be used
* For an emergency door release, usual setup is that a failure in the emergency door release mechanism, or a break in the cabling connecting the emergency door release to the controller, will result in the door being released. To enable this, use the NC output of the emergency door release, and choose the **Emergency door release opens circuit (NC)** option. This way a break in the cable will cause an open circuit to appear to the input, and so trigger the door to open
* For a door position indicator, the active state should be when the door is open. Therefore, if the sensor is installed such that closing the door closes the circuit, choose the **Circuit is closed when door is closed (NC)** option.

## Outputs <a href="#outputs" id="outputs"></a>

To correctly choose how to connect the output, consider the type of lock and the desired behavior in case of a controller failure, as might be caused by hardware failure or complete loss of power including  exhaustion of the backup battery.

{% hint style="danger" %}
WARNING: In case of the controller losing power, correct lock functionality requires a separate lock power supply with its own backup supply
{% endhint %}

To control the behavior of the relay in case of controller failure, use the software control of the output polarity. If, in the case of a failure, the lock should open (fail safe), the **Energize relay on lock option** should be used. On the other hand, if in the case of a failure the lock should lock (fail secure), the **Energize relay on open** option should be used.

{% hint style="info" %}
Note that fail secure locks can trap people during a power outage or failure. Install a mechanical exit mechanism to ensure people can safely exit at all times&#x20;
{% endhint %}

### AI Security Hub outputs <a href="#ai-security-hub" id="ai-security-hub"></a>

When configuring the AI Security Hub, the polarity of the output must be set using the **POWER TO LOCK/OPEN** switch on the board. This switch configures both the behavior of the wet output and the dry output on a channel.

If the switch is set to **POWER TO LOCK**, when the access control system requests the door to lock, the wet output will provide power, and the relay will be energized.

If the switch is set to **POWER TO OPEN**, when the access control system requests the door to unlock, the wet output will provide power, and the relay will be energized.

#### **Relay outputs**

When using the relay outputs, three terminals are available, NC, NO, and COM. For all installations, COM and one of either NC or NO should be used. To choose whether to use NO or NC, consider the position of the **POWER TO LOCK/OPEN** switch, and the type of lock.

<table data-header-hidden><thead><tr><th width="159.3671875">Behavior</th><th width="289.0546875">Requires power to lock (e.g. maglock)</th><th>Requires power to unlock (e.g. electric strike)</th></tr></thead><tbody><tr><td></td><td><strong>Lock requires power to lock (e.g. maglock)</strong></td><td><strong>Lock requires power to unlock (e.g. electric strike)</strong></td></tr><tr><td><strong>Switch set to POWER TO LOCK</strong></td><td>COM &#x26; NO</td><td>COM &#x26; NC</td></tr><tr><td><strong>Switch set to POWER TO OPEN</strong></td><td>COM &#x26; NC</td><td>COM &#x26; NO</td></tr></tbody></table>

#### **Wet outputs**

When using the wet outputs, only two terminals are available, both of which should be used. The **Power to Open/Lock** switch on the Hub should then be used to set the correct behavior.

Because the AI Security Hub is providing all the power, you should not choose between fail secure and fail safe, as if there is a failure, there will be no power supplied to the lock. Therefore, the choice of the switch depends only on the choice of lock.

<table data-header-hidden><thead><tr><th width="160.38671875"></th><th>Lock requires power to lock (e.g. maglock)</th><th>Lock requires power to unlock (e.g. electric strike)</th></tr></thead><tbody><tr><td> </td><td><strong>Lock requires power to lock (e.g. maglock)</strong></td><td><strong>Lock requires power to unlock (e.g. electric strike)</strong></td></tr><tr><td><strong>Power to:</strong></td><td>LOCK</td><td>OPEN</td></tr></tbody></table>

#### **Fire override**

The Accessia AI Security Hub allows integration with a fire alarm system. Correct connection and configuration of the hardware switches on the Hub are required to ensure correct behavior in alarm situations.

If the **FIRE OVERRIDE** switch is set for an output, in the case of a fire alarm (i.e. a positive input on the **FIRE ALARM INTERFACE**), the door will be set into the open state.


# Channel inputs

The channel inputs can be used for request-to-exit (REX) buttons, door position sensors, or lock status sensors

* Configure input functions using Accessia Installer app
* The inputs should only be connected to isolated switch contacts – do not connect to a power supply
* Use a shielded cable and connect the shield to earth using the labeled earth post inside the enclosure
* For end-of-line monitoring, use 2.2 kOhm +/- 1% resistors at the switch (Figure 1)

![Figure 1: DEOL monitored input](/files/GtG32P6M09a4T2AI9lbL)

For optimum DEOL monitoring performance, keep the inputs isolated from each other. If it cannot be avoided, the two inputs on the same channel can share a common terminal. In this case, wire the two inputs as shown in Figure 2

![Figure 2: DEOL monitored inputs with common terminal](/files/2ZJX3zBxDhAGdHdxHVwB)

Adjacent to the input terminals is a switchable 12VDC power output for peripheral devices. This can be used for a touch-free REX button or a door-left-open alarm. Configure its function in Accessia installer app

The labeling on the Hub shows the correct pin out for all these connections


# Channel output power

|                           | Security Hub v1 | AI Security Hub |
| ------------------------- | --------------- | --------------- |
| **Total power available** | 60W             | 44W             |

For each channel, power can be supplied to:

* a Reader (12 VDC)
* a peripheral such as a touch-free request-to-exit button (12 VDC)
* a lock (selectable between 12 VDC or 24 VDC)

> **Example**
>
> On Security Hub v1, if all locks use 12V, then a total output current (across all locks, readers, and peripherals) of 5.0A is available. If 24V locks are used, then the total current available reduces accordingly, such that the total power remains within the 60W limit.

* Any one lock output can supply a maximum current of 1.4A. Any one Reader or peripheral output can supply a maximum current of 700mA
* It is not possible to supply the maximum current on all outputs at the same time, due to the total output power limit of 60W
* Each power output has an active current limiter which prevents a fault on one external device from affecting any other part of the system. Use the Accessia Installer app to optionally configure a lower current limit for each output to minimize the risk of system disruption or damage to external devices in the event of a fault
* All power outputs are Power-Limited Class 2 circuits

## Output power on battery

* In the event of AC mains failure, the Hub can maintain normal operation for a minimum of 30 minutes and typically 1 hour (standby power performance level II) with a total output power of 60 Watts when using the recommended backup battery (see [Battery connection](/hardware/ai-security-hub-hub-v1/mains-and-battery-power))
* If the total output power is reduced to a maximum of 24 Watts, the Hub can maintain normal operation for a minimum of two hours and typically 3 hours (standby power performance level III)


# Auxiliary IO

* The Hub includes four auxiliary inputs, **AUX 1 IN,** **AUX 2 IN, AUX 3 IN, AUX 4 IN**, and three auxiliary outputs **AUX 1 OUT,** **AUX 2 OUT,** and **AUX 3 OUT**. Use Accessia Installer app to configure their function

{% hint style="info" %}
If you want to connect an intruder alarm interface, use **AUX 3 IN, AUX 4 IN,** and **AUX 3 OUT**. See how to connect an [intruder alarm interface](/hardware/ai-security-hub-hub-v1/inputs-and-outputs/intruder-alarm-interface)
{% endhint %}

* The inputs can only be connected to isolated switch (or relay) contacts. Do not connect them to a power supply. A loop resistance greater than 500 kOhms will be interpreted as Open and a loop resistance less than 500 Ohms will be interpreted as Closed
* Use a shielded cable and connect the shield to earth using the labeled earth post inside the enclosure
* The outputs are implemented using a single-pole-double-throw relay and are electrically isolated from the rest of the system (and each other). The dry output is rated to switch a maximum of 5A and 30 VDC


# Fire alarm interface

* The Hub includes a **FIRE IN** input that can be connected to an isolated relay driven by a fire alarm system. Do not connect this input to a power supply
* Configure the sense of the relay (normally open or normally closed) using the slide switch on the Hub (a red indicator lights up when the fire condition is indicated). A loop resistance greater than 500 kOhms will be interpreted as Open and a loop resistance less than 500 Ohms will be interpreted as Closed
* Use a shielded cable and connect the shield to earth using the labeled earth post inside the enclosure
* When the FAI is used, you can configure each lock to unlock in response to the fire condition
  * For each lock, set the corresponding fire override slide switch to on. Note that you must set the power-to-lock/power-to-open switch correctly to ensure that the lock will unlock during a fire condition
* When using the FAI feature, the installation must be tested and approved by the relevant fire authority to ensure that the behavior results in a system that is safe
* For any power-to-open locks, do not rely on this feature for safety, as failures elsewhere in the system can result in power loss to the lock
* This feature is not a substitute for mechanical overrides or break-glass disconnects at the exit door to allow for safe exit from the building in the event of an emergency


# Intruder alarm interface

* The intruder alarm interface has two inputs and one dry output
* The inputs can only be connected to isolated switch (or relay) contacts. Do not connect them to a power supply. A loop resistance greater than 500 kOhms will be interpreted as Open and a loop resistance less than 500 Ohms will be interpreted as Closed
* Use a shielded cable and connect the shield to earth using the labeled earth post inside the enclosure
* The dry output is implemented using a single-pole-double-throw relay and is electrically isolated from the rest of the system. The dry output is rated to switch a maximum of 5A and 30 VDC
* You can configure the interface in Accessia Installer app
* For buildings that include an intruder alarm supporting this feature, the Hub output **AUX 3 OUT** can be used to toggle the state of the intruder alarm (set or unset)
* The **AUX 3 IN** input should be driven by the intruder alarm to indicate its current state (set or unset)
* The **AUX 4 IN** input should be connected to a set-request push button on the inside of the exit door
* When the alarm is set and an authorized user presents their credentials at the entrance door, the alarm is automatically unset
* When an authorized user exits the building and presses the set-request button, the alarm is automatically set as soon as the exit door closes behind them


# Hub visual states

<figure><img src="/files/oedJqCsUkACYfE32Ru3E" alt="" width="375"><figcaption></figcaption></figure>

## Power status indicator

A white indicator on the front panel of the Hub shows the Hub’s power status

| **Indicator behavior** | **Meaning**             |
| ---------------------- | ----------------------- |
| Off                    | No power or booting     |
| Solid on               | AC power and battery OK |
| Flashing slow          | AC power loss           |
| Flashing fast          | Battery fault           |

## System STATUS indicator

A red indicator labeled **STATUS** on the module inside the Hub shows the Hub’s system status

| **Indicator behavior** | **Meaning**         |
| ---------------------- | ------------------- |
| Off                    | No power or booting |
| Solid on               | System status OK    |
| Flashing slow          | System fault        |

System faults indicated by flashing slow include:

* Failure to communicate with a Reader – check the Reader and its wiring
* Reader tampering detected – check the Reader
* Bad battery temperature – check the battery and its thermistor connection
* Battery close to being exhausted – connect AC power as soon as possible

To view details of the fault, check the system health report in Accessia Installer app or Accessia Portal

## CLOUD status indicator

A blue indicator labeled **CLOUD** on the module inside the Hub shows the Hub’s cloud connection status

| **Indicator behavior**                 | **Meaning**                                 |
| -------------------------------------- | ------------------------------------------- |
| Off                                    | No power or booting                         |
| Solid on                               | Cloud connection OK                         |
| Flashing slow                          | Cloud connection down                       |
| Flashing one second on, one second off | Cloud connection down, Hub not commissioned |
| Flashing twice every two seconds       | Cloud connection OK, Hub not commissioned   |

If the indicator is flashing slow, check the network connection from the Hub to the local area network and from the local area network to the internet


# Accessia Reader

Accessia Reader is an award-winning, mobile-first, next generation reader for cutting-edge credentials - UWB, NFC, and BLE

<figure><img src="/files/M7guh9dSJmqnQgRWdRtK" alt="" width="61"><figcaption></figcaption></figure>

## Get started

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Datasheet</td><td><a href="/pages/k5SPkXGNFS24BbWtxzmF">/pages/k5SPkXGNFS24BbWtxzmF</a></td></tr><tr><td>Installation</td><td><a href="/pages/MHIS9BX2slLef58tvoDB">/pages/MHIS9BX2slLef58tvoDB</a></td></tr><tr><td>Visual states</td><td><a href="/pages/TC2cEXH2Q3sZ34OVXUUV">/pages/TC2cEXH2Q3sZ34OVXUUV</a></td></tr></tbody></table>


# Reader datasheet

See the datasheet for Reader specifications and certifications

{% file src="/files/g0e6xF3v5aFZYXr85zo4" %}


# Reader installation

## **Install guide**

Document Number 490-0002-01

Revision 05 – 27th October 2025

{% file src="/files/HyP8SeJbgCbtuPqwSJwA" %}

## **What’s in the box?**

* Accessia Reader
* Bezel removal tool

## **What you’ll need**

* 2 x 3.5mm diameter (no. 6) panhead screws and wall anchors suitable for the wall surface the Reader will be mounted on
* 5-way terminal block with suitable tool for 24AWG wire connection
* Bezel removal tool (supplied)
* 120 Ohm +/- 1% termination resistor (depending on topology)

## **Mounting guide**

### Before you start

* Make sure the wall you want to mount the Reader on is flat and vertical
* Choose a good position that is easy for all users to access, including those with limited mobility
* Make sure there is a hole in the wall behind the Reader which you can pass the integrated cable through
* Avoid mounting the Reader directly onto a metallic surface

### How to mount the Reader

1. Remove the bezel. Insert the removal tool into the two holes at the bottom of the Reader. Push the tool in until the clips at the lower end of the bezel release and lift. Unhook the upper end of the bezel and remove it from the Reader (Figure 1)
2. Remove the mounting bracket from the back of the Reader by sliding it downwards (Figure 2)

![Figure 1: Removing the bezel](/files/R3NW49XvNFIlk72W104b)

![Figure 2: Removing the mounting bracket](/files/Jv50LHwX59WXRHWETyOK)

3. Secure the mounting bracket to the wall using fixings appropriate for the wall surface. Make sure that the that the hole in the wall for the integrated cable and the exit point for the cable from the Reader are lined up when positioning the mounting bracket (Figure 3)

<img src="/files/MwiBMGTTqHMPBCLwTswo" alt="Figure 3: Securing the mounting bracket" width="429">

4. Pass the integrated cable though the mounting bracket and the wall and then hook the Reader onto the mounting bracket. Make sure the Reader is fully attached to the mounting bracket
5. Hook the top edge of the bezel over the top of the Reader and press the lower end of the bezel until it clicks securely into place

## **Wiring guide**

* The Reader must be connected to an Accessia Hub. For connections and topologies, check the [AI Security Hub installation guide](/hardware/ai-security-hub-hub-v1/ai-security-hub-hub-v1-installation) and Figure 4 below
* The Reader must be connected using shielded twisted pair cable, for example Belden 8723. Connect the shield to the drain wire in the Reader’s integrated cable
* The RS-485 twisted pair must be terminated at both ends with a 120 Ohm +/- 1% resistor. For details, check the [AI Security Hub installation guide](/hardware/ai-security-hub-hub-v1/ai-security-hub-hub-v1-installation)
* Make sure that the terminal block and all wiring is inaccessible to unauthorized personnel

<img src="/files/hE4aY8mZ3gEklGLJdXFu" alt="Figure 4: Reader integrated cable connections" width="563">

Maximum cable lengths:

* 22 AWG: 250 feet / 76 meters
* 20 AWG: 330 feet / 100 meters
* 18 AWG: 500 feet / 152 meters

## **Information**

### **Reader supported credentials**

* NFC - MIFARE DESFire EV2 and EV3
* BLE - Accessia for mobile and SDKs
* UWB - Accessia for mobile and SDKs

### How to clean

When necessary, clean the Reader with a soft damp cloth. Do not use any solvents or abrasive materials

### **Compatibility**

Readers are only compatible with Accessia Hubs

### **Software version**

Reader software is automatically updated when necessary by the Hub. To check the current software version, check Accessia Installer app or [Accessia Portal](http://cloud.accessia.com/)

### **Operating conditions**

Power input: 8 to 12VDC, 2 Watts maximum

Operating temperature range: -31 to 150ºF / -35 to +66ºC

Humidity: 20 - 90% RH non-condensing

Ingress protection rating: IP65

Impact protection rating: IK07

### **Compliance**

Compliance Model RDR01A

#### **FCC**

This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation

Contains FCC ID: VPYLB2BP

Contains FCC ID: YCP-32WB5MMGH02


# Reader visual states

See also [Reader behaviour](/site-setup/reader-behavior)

{% columns %}
{% column %}

<div align="center"><figure><img src="/files/enVs4l6ZuKxo4FLAKoSc" alt="" width="121"><figcaption></figcaption></figure></div>

<p align="center">Solid red - door locked under access control schedule</p>

<p align="center"></p>
{% endcolumn %}

{% column %}

<figure><img src="/files/t1ZAM0JCISn18APeFLV1" alt="" width="121"><figcaption></figcaption></figure>

<p align="center">Flashing red - door warning (held open, forced, tamper)</p>
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

<figure><img src="/files/M7guh9dSJmqnQgRWdRtK" alt="" width="121"><figcaption></figcaption></figure>

<p align="center">Solid green - door unlocked under access control schedule</p>

<p align="center"></p>
{% endcolumn %}

{% column %}

<figure><img src="/files/MlugjrauZSUjBZyhaCYu" alt="" width="121"><figcaption></figcaption></figure>

<p align="center">Flashing green - access granted</p>

<p align="center"></p>
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

<figure><img src="/files/8uXPKVgd0x2yTkH7KQJE" alt="" width="121"><figcaption></figcaption></figure>

<p align="center">Green segment countdown - door unlocked and counting down to locked</p>
{% endcolumn %}

{% column %}

<figure><img src="/files/DUg9YN7GqyW9KAAo1E1K" alt="" width="121"><figcaption></figcaption></figure>

<p align="center">Green segment chase - door unlocked while the UWB user is in proximity</p>
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

<figure><img src="/files/GW78i9NBEQjnHkqwy3jw" alt="" width="121"><figcaption></figcaption></figure>

<p align="center">Yellow segment chase - reading NFC credential</p>
{% endcolumn %}

{% column %}

<figure><img src="/files/U0C4rGldMd1Lb9SlpJzS" alt="" width="121"><figcaption></figcaption></figure>

<p align="center">Solid dark blue - door locked, meeting room available to access</p>
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

<figure><img src="/files/Vqp2UPmljjTqwpHGyhYw" alt="" width="121"><figcaption></figcaption></figure>

<p align="center">Solid purple - reader in commissioning mode</p>
{% endcolumn %}

{% column %}

<figure><img src="/files/kIvwFEVRwkFuwIvRklfA" alt="" width="121"><figcaption></figcaption></figure>

<p align="center">Solid blue with purple segment chase - ‘Beep reader’ triggered from Portal</p>
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}

<figure><img src="/files/3X6e8zhmliE0ZriGsTAi" alt="" width="121"><figcaption></figcaption></figure>

<p align="center">Partial flashing green segment with solid white - Reader booting, updating, or loss of communication with the Hub (before boot)</p>
{% endcolumn %}

{% column %}

<figure><img src="/files/IXWUGxhQl65pb8PXWDCL" alt="" width="121"><figcaption></figcaption></figure>

<p align="center">Flashing yellow - Fault - loss of communication with the Hub (after Reader boot)</p>
{% endcolumn %}
{% endcolumns %}


# Cloud Converter for S2 Netbox

Get your LenelS2 Netbox\* cloud-connected and breathe new life into your access control. All the features you need with none of the headache

<figure><img src="/files/Za1ugmJJZQgk3OS2t4im" alt="" width="188"><figcaption></figcaption></figure>

## Get started

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Datasheet</td><td><a href="/pages/MyKmmePhudciVxz14fWx">/pages/MyKmmePhudciVxz14fWx</a></td></tr><tr><td>Installation</td><td><a href="/pages/HLIo7DW5hseHklejGFg0">/pages/HLIo7DW5hseHklejGFg0</a></td></tr></tbody></table>

<sub>*\*Accessia is not an authorized partner of LenelS2. Accessia Cloud Converter for S2 NetBox is not approved or supported by LenelS2*</sub>


# Cloud Converter datasheet

See the datasheet for Cloud Converter specifications and certifications

{% file src="/files/1rB64jhDmlCZUhu60BaY" %}

<sub>*\*Accessia is not an authorized partner of LenelS2. Accessia Cloud Converter for S2 NetBox is not approved or supported by LenelS2*</sub>


# Cloud Converter installation

## **Install guide**

Document Number 490-0004-01

Revision 03 – 27th October 2025

{% file src="/files/PG9Xsq7YYco0Zm30l6bS" %}

## Video demonstration

{% embed url="<https://www.youtube.com/watch?ab_channel=Accessia&v=LpwZkr8A2m0>" %}

The Accessia Cloud Converter for S2 NetBox\* is the simple way to bring cloud functionality to your on-premise access control

{% hint style="info" %}
Replacing node blades and migrating to Accessia’s cloud can be completed in under a minute
{% endhint %}

1. Disconnect your S2 NetBox controller from power
2. Unplug any connectors including the ribbon cable from the node blade and unscrew it
3. Install the Accessia Cloud Converter, by screwing it in and plugging in the same connectors including the ribbon cable
4. Reconnect your S2 NetBox controller to power
5. Your access control is now connected to Accessia’s cloud platform

<sub>\*</sub><sub>*Accessia is not an authorized partner of LenelS2. Accessia Cloud Converter for S2 NetBox is not approved or supported by LenelS2*</sub>


# Cloud Converter visual states

There are four LEDs on the Cloud Converter board, labeled **PWR**, **INF**, **CLOUD** and **STATUS**

You can also connect the Cloud Converter  to an externally visible panel indicator (see the "Panel LED" section of the installation manual)

## External panel status indicator

This LED communicates status in two ways color and flashing pattern, which are used independently

<table><thead><tr><th valign="top">Indicator pattern</th><th valign="top">Meaning</th></tr></thead><tbody><tr><td valign="top">Solid off</td><td valign="top">No power or booting</td></tr><tr><td valign="top">Solid on</td><td valign="top">External power and battery OK</td></tr><tr><td valign="top">Flashing slow</td><td valign="top">External power loss</td></tr><tr><td valign="top">Flashing fast</td><td valign="top">Battery fault</td></tr></tbody></table>

<table><thead><tr><th valign="top">Indicator color</th><th valign="top">Meaning</th></tr></thead><tbody><tr><td valign="top">Blue</td><td valign="top">Cloud connection OK</td></tr><tr><td valign="top">Red</td><td valign="top">Cloud connection lost</td></tr></tbody></table>

## PWR indicator

<table><thead><tr><th valign="top">Indicator behavior</th><th valign="top">Meaning</th></tr></thead><tbody><tr><td valign="top">Solid off</td><td valign="top">No power</td></tr><tr><td valign="top">Solid red</td><td valign="top">Power on</td></tr></tbody></table>

## **INF indicator**

<table><thead><tr><th valign="top">Indicator behavior</th><th valign="top">Meaning</th></tr></thead><tbody><tr><td valign="top">Solid off</td><td valign="top">No power or booting</td></tr><tr><td valign="top">Heartbeat red (2 flashes every 2 seconds)</td><td valign="top">System is running smoothly</td></tr></tbody></table>

## **CLOUD indicator**

<table><thead><tr><th valign="top">Indicator behavior</th><th valign="top">Meaning</th></tr></thead><tbody><tr><td valign="top">Solid off</td><td valign="top">No power or booting</td></tr><tr><td valign="top">Solid blue</td><td valign="top">Cloud connection OK</td></tr><tr><td valign="top">Flashing slow blue</td><td valign="top">Cloud connection lost</td></tr></tbody></table>

If the CLOUD indicator is flashing slow, check the network connection from the Cloud Converter to the local area network and from the local area network to the internet

## **STATUS indicator**

<table><thead><tr><th valign="top">Indicator behavior</th><th valign="top">Meaning</th></tr></thead><tbody><tr><td valign="top">Solid off</td><td valign="top">No power or booting</td></tr><tr><td valign="top">Solid red</td><td valign="top">System status OK</td></tr><tr><td valign="top">Flashing slow red</td><td valign="top">System fault</td></tr></tbody></table>

System faults indicated by flashing slow include:

* Failure to communicate with a downstream device
* Fault reported by a downstream device
* Battery close to being exhausted – connect external power as soon as possible

You can find details of the fault by viewing the system health report in the Accessia Installer app or the Accessia Portal


# Configuring inputs and outputs

The Accessia platform allows you to configure polarity of both inputs and outputs in either software on the Cloud Converter, or in hardware on the AI Security Hub. When connecting to relay outputs, you can choose between using the NC or NO output.

Input devices such as door position sensors and exit buttons are available in either NC or NO versions, or feature both NC and NO outputs.

Locks are available in different types such as maglocks, which require power to lock the door, or electric strikes, which can require power to lock the door (fail safe), or power to open the door (fail secure).

Reading and understanding this document will help you wire and configure your access control system for proper functionality.

{% hint style="info" %}
Choosing the right wiring options and software configuration is essential to ensure compatibility with the chosen hardware and for correct functioning in cases of broken cables or power loss etc.&#x20;
{% endhint %}

## Inputs <a href="#inputs" id="inputs"></a>

#### Door position sensors

Usually, the 'normal' state of a door is considered to be in the secure state, i.e. with the door closed. \
\
This might not match the wording shown on the output of the sensor, for example:<br>

* For a reed switch type contact, the normal state would be with the door open
* For a maglock field strength sensor, normal is typically when the maglock is not energized, for example  when the door is open and unlocked

#### Other inputs

For a button, the normal state is when the button is not pressed. Understanding this helps with the below:

* For a REX button, typically the button offers NC and NO outputs. Usual configuration is to connect the NO output into the input on the controller, and choose the option **Door release request closes circuit (NO)**
* For a presence detector, the sensible option is **Presence detection closes circuit (NO)**. This ensures that, if a presence detector fails (for example, in the case that even when people are present, the input stays open), all door openings will result in an alert. This might be the opposite of typical usage of a PIR sensor in an alarm sensor, where it is desirable for a cable break to trigger the alarm, so **Presence detection opens circuit (NC)** would be used
* For an emergency door release, usual setup is that a failure in the emergency door release mechanism, or a break in the cabling connecting the emergency door release to the controller, will result in the door being released. To enable this, use the NC output of the emergency door release, and choose the **Emergency door release opens circuit (NC)** option. This way a break in the cable will cause an open circuit to appear to the input, and so trigger the door to open
* For a door position indicator, the active state should be when the door is open. Therefore, if the sensor is installed such that closing the door closes the circuit, choose the **Circuit is closed when door is closed (NC)** option.

## Outputs <a href="#outputs" id="outputs"></a>

To correctly choose how to connect the output, consider the type of lock and the desired behavior in case of a controller failure, as might be caused by hardware failure or complete loss of power including  exhaustion of the backup battery.

{% hint style="danger" %}
WARNING: In case of the controller losing power, correct lock functionality requires a separate lock power supply with its own backup supply
{% endhint %}

To control the behavior of the relay in case of controller failure, use the software control of the output polarity. If, in the case of a failure, the lock should open (fail safe), the **Energize relay on lock option** should be used. On the other hand, if in the case of a failure the lock should lock (fail secure), the **Energize relay on open** option should be used.

{% hint style="info" %}
Note that fail secure locks can trap people during a power outage or failure. Install a mechanical exit mechanism to ensure people can safely exit at all times&#x20;
{% endhint %}

### Cloud Converter for S2 Netbox outputs <a href="#hub-mini-and-s2-cloud-converter" id="hub-mini-and-s2-cloud-converter"></a>

When using the relay outputs, three terminals are available, NC, NO, and COM. For all installations, COM and one of either NC or NO should be used. To choose whether to use NO or NC, consider the software option, and the type of lock

<table data-header-hidden><thead><tr><th width="132.4375">Behavior</th><th width="270.546875">Requires power to lock (e.g. maglock)</th><th>Lock requires power to unlock (e.g. electric strike)</th></tr></thead><tbody><tr><td></td><td><strong>Lock requires power to lock (e.g. maglock)</strong></td><td><strong>Lock requires power to unlock (e.g. electric strike)</strong></td></tr><tr><td><strong>Energize relay on lock (fail safe)</strong></td><td>COM &#x26; NO</td><td>COM &#x26; NC</td></tr><tr><td><strong>Energize relay on open (fail secure)</strong></td><td>COM &#x26; NC</td><td>COM &#x26; NO</td></tr></tbody></table>