Access Controller features

Doors and hardware

Standard parts, properly controlled.

Works with standard Wiegand fob and card readers (26/34-bit), electric strikes and maglocks, exit buttons and door sensors.
Small door controller: wireless (Wi-Fi) or wired (Ethernet), PoE as an order option on the wired one, single-door and dual-door models. One board drives two independent doors, each with its own reader, relay, exit button and door contact.
Per-door fail-safe or fail-secure behaviour, configurable relay pulse, exit button and door-position sensing.
Held-open and forced-door alerts.
Controllers keep working offline: the access list lives on the controller, so a broken internet link never locks anyone out.
Reader and relay mapping per door, including channel 1 and channel 2 on dual-door controllers.
Browser flash-and-adopt wizard with clickable steps: jump straight to Configure for a board that is already flashed.
Remote unlock button per controller. Over-the-air firmware updates and remote re-pointing from the panel.

Boards and wiring

Door detail page with fail mode and reader/relay mapping — Door detail: fail mode, relay pulse, reader and relay mapping.

Controllers list with status, firmware version and remote actions — Controllers: online status, firmware, remote unlock and re-point.

People and credentials

People first, fobs attached.

People with photo, contact details, notes, active/inactive status.
Multiple fobs per person; revoke, re-activate or delete a fob in one click.
Enrol a fob by scanning it at any door you choose: the next unknown fob presented at that reader is captured and attached to the person.
Enrolment mode, per door: tick the doors you are working at, pick the access level everyone should get and a window of 15 to 120 minutes. Unknown fobs are accepted and captured at those doors only; every other door carries on refusing them.
Enrol over the phone: a member rings the access line, presses hash, keys in the site number and has ten minutes to present a new fob at an enrolment door. No trip to the office, and the call never opens a door.
Import people and fobs from a spreadsheet (CSV), or straight from an AC8000 / iCCard3000 backup file.
Bulk actions: tick people and add or remove access levels, set active or inactive, turn phone release on or off, export or delete, all in one go.
A 30-day trash: a deleted person's fobs stop working at once, and restoring them puts their fobs and levels back exactly as they were.
CSV export of everyone, or of whatever a search found.
Photo upload or straight from the webcam.
Search by name, email, phone or fob code.
"Check a fob" tool: type a code and see exactly who it is and where it opens.

People list with photos, search and fob counts — People list with photos, search and fobs.

Full person page: photo, fobs, access levels, phone release and apartment mode — A person: photo, fobs, access levels, phone release, apartment mode. Click to see the full page.

Enrolment page capturing fobs presented at a reader — Enrolment: tick the doors, pick the level, capture fobs and assign names.

Migrating an existing site

Bring the old system across, cards and all.

Import straight from an AC8000 / iCCard3000 backup (.mdb) - the file most standalone sites have, and no export function for.
The backup is read in your browser. Only the people, fob codes and history you confirm are sent to the panel.
People, card numbers, door names and the whole swipe history, with the original dates and times, so the log starts full rather than empty.
Editable door names in the preview: rename what the old system called things, or point the history at doors you have already created.
Bulk access-level assignment: tick the levels everyone imported should get. Existing people have them added, never replaced.
Rows with the same name become one person holding several fobs, so replacement cards do not turn into duplicate members.
Lapsed and disabled members arrive inactive, carrying their old record number and valid-to date in their notes.
Reader format 6 or 8 hex digits, chosen for you when the card numbers say so.
Nothing is written until you confirm the preview, and an existing fob is never overwritten.

Import wizard reading an AC8000 backup in the browser — The wizard reads the backup in the browser and reports what it found.

Import preview with column mapping, bulk access levels and editable door names — Preview: columns, access levels for everyone, and the door names to create.

Room bookings and the resident portal

The lounge, the gym, the laundry. Booked and unlocked.

Turn any door into a bookable room: opening hours per day, slot length, a gap between bookings, how far ahead people may book and how late they may cancel.
Free or priced per slot, with optional extras (a projector, a set of weights) and stock limits.
A room needs no card reader. A door module and an exit button are enough: residents come in from the portal or by ringing the access line.
Residents book on their own phone at your own address, signing in with their mobile number and a texted code. Unknown numbers can register with a name and apartment.
A confirmed booking opens the door for that slot and nothing else: an "Open the door" button on the phone, a call from the mobile they booked with, or their existing fob if a reader is fitted.
Card payment through Stripe Checkout, or bank transfer with a quoted reference that staff mark paid. Unpaid bookings expire and the slot goes back on sale.
Staff see everything on one Bookings page, and can book a room at the desk, mark a transfer paid or cancel.
A public "what is on today" board for a screen by the door, with names shown as initials.

Rooms list with slot length, price, booking window and status — Rooms: slot length, price, how far ahead and how late to cancel.

Room settings with opening hours per day and optional extras — A room: settings, seven-day opening hours and extras.

Bookings page with status, amount and mark-paid action — Bookings: confirmed, awaiting payment, cancelled. Mark a transfer paid in one click.

Resident portal sign-in on a phone: the building name, a mobile number field and a Send me a code button — The resident portal: sign in with a mobile number and a texted code.

Resident portal home on a phone: greeting, the next booking and the list of rooms with the next free slot — Home: what is coming up and which rooms are free next.

A room on the resident portal: slot length and price, then a grid of bookable times for the next seven days — Pick a slot from the seven-day grid. Taken and closed times are greyed out.

A confirmed booking on the resident portal with the Open the door button — During the slot the booking page opens the door, or ring the door from the mobile you booked with.

Access levels and schedules

"Members", "Staff", "24/7". Done.

Access levels group doors and a schedule.
Assign one or more levels per person.
Weekly schedules with a guided editor: presets, copy to weekdays or all days, time windows, all-day and closed days, with a visual timeline.
Changes push to every affected controller within seconds.

Guided weekly schedule editor with a visual timeline — The guided schedule editor with timeline.

Access levels list, each grouping doors and a schedule — Access levels: doors plus a schedule.

Phone access (dial release)

One number, every site.

Known callers are recognised by caller ID: one door opens straight away, or a short keypad menu chooses between several.
Apartment mode for guests: enter the apartment number then a PIN. Ideal for holiday lets and Airbnb; give a guest a code, change it after they leave.
Enrol a fob by phone: press hash at the start of the call, key in the site number, then present the new fob at an enrolment door within ten minutes. The call itself never opens anything.
A confirmed room booking releases the room door for the caller, for the length of their slot, with nothing else to set up.
Runs on the customer's own or our hosted PBX (Asterisk/MiRTA PBX supported out of the box, simple HTTPS API for anything else).
Wrong-PIN lockout with escalating backoff, per-source rate limiting, every call logged with the number and outcome.

Phone access in depth

Person page showing phone release and apartment mode settings — Phone release and apartment mode are set per person.

Reception screen

The front desk sees every entry live.

A live full-screen page for a laptop or wall monitor at the front desk.
Shows each person's photo and name the moment they fob in, granted or denied.
Recent entries down the side, today's scan and denied counts at the top.
Pick which doors each screen watches. Secure link, no login needed on the screen, regenerate the link at any time.

Live reception screen showing a granted entry and recent entries — The reception screen.

Doors list with reception screen link — Doors list, including the reception screen link.

Log and reporting

Who, where, when, and why not.

Every scan, unlock, denial and system event with time, door, person and reason (unknown fob, outside hours, inactive, held open, phone unlock...).
Door events too: door opened, door closed and exit button pressed, so you can see how long a door actually stood open and who let somebody out.
Every way a door was released is labelled: remote unlock from the panel, lock released by command, phone unlock, opened from the portal during a booking.
Filter by door, person and outcome.
Dashboard tiles: people and fobs, doors and controllers, today's scans and denials, controller health.

Access log with filters by door, person and outcome — The access log.

Dashboard with tiles, check-a-fob tool and recent activity — Dashboard tiles, controller health and the check-a-fob tool.

Multi-site and multi-tenant

Every customer its own tenant. Every tenant its own look.

Each customer is a tenant with its own people, doors, settings and users.
Per-tenant branding: logo and accent colour across the panel.
Providers get a super-admin view: see every tenant and "switch in" to work inside any of them.
Controllers arrive in a pool and are assigned to a tenant.

/branding

Branding: logo and accent colour per tenant.

Branded login page — The branded login page a tenant's users see.

The panel on a phone

The whole panel fits in a pocket.

The sidebar folds into a header bar with the logo and a menu button; tapping it drops down every page you are allowed to see, the tenant switcher and the log-out button.
Wide tables scroll inside their own panel, so the log and the people list stay readable.
Everything an admin can do at a desk can be done standing at a door: assign a captured fob, unlock, check why somebody was refused.

The panel on a phone with the header bar and menu button — The panel on a phone.

The mobile menu open showing every page, the theme toggle and log out — The menu open: every page, theme and log out.

Users and permissions

Tick the pages. That is the role.

Fixed roles: super admin, admin, view-only.
Custom roles built by ticking pages in a tree: view or change, per page.
View-only users see no edit controls at all.

Custom role editor: page tree with view and change ticks — A custom role: page tree with view/change ticks.

Users list with roles — Users and their roles.

Security and deployment

Small footprint, serious defaults.

HTTPS with automatic certificates. Controller link over authenticated MQTT.
Passwords hashed (bcrypt), CSRF protection, per-session tokens.
PINs stored hashed and never displayed. Lockouts and rate limits on the phone API.
Secret links for the reception screen and PBX are one click to regenerate.
Full audit trail.
Single small binary with an embedded database and MQTT broker. Runs on a low-cost cloud VM or on-premise. Minutes to install, one file to back up.
Hosted by 2plus1 with monitoring, updates and support, or self-hosted.

Tenant settings: Wi-Fi, controller type and phone API — Tenant settings: Wi-Fi, controller type, phone API and secret links. Click to see the full page.

Want to see it on your doors?

Book a demo and we will walk through the panel with your site in mind.

Book a demo Hardware

Everything the panel does, with the screens to prove it.