Entrosity Edge
Entrosity Edge is cloud-managed physical access control. It manages who may pass which doors and when, keeps the access controllers on your sites in step with those rules, and records every door event in one access log.
Edge runs at https://hub.entrosity.com/edge. You sign in on
Entrosity Hub, like for every Entrosity product, and
open Entrosity Edge from the Hub's product launcher.
Edge is currently open to platform admins only: organizations and their users do not see it yet. A platform admin releases it to organizations under Products in beta.
What it does
| Area | What you get |
|---|---|
| People and cards | Cardholders with validity periods, Wiegand 26-bit cards and iButton keys, a pool of unassigned cards, blocking and lost cards. |
| Access rules | Weekly schedules with holiday windows, holidays, and access groups that give their members doors during a schedule. |
| Controllers | TRAcK ACCESS TrackBase002 controllers found through an on-site connector, their doors and readers, each kept in sync with its own complete configuration. |
| Live monitor | Every access decision, door alarm and controller event as it happens, and the full searchable history. |
| Remote opening | Operators open a door from the browser; the opening is recorded with their name. |
| Works offline | Controllers decide on their own with the configuration they hold. When the Internet or the connector is down, doors keep working and events are delivered later, exactly once. |
Edge does not do time and attendance: it records access events, not working hours.
Supported hardware
Edge drives TRAcK ACCESS TrackBase002 controllers (NRJ Soft):
| TrackBase002 | |
|---|---|
| Connection | TCP/IP, or RS-485 (Modbus) with bus addresses 1–31 |
| Readers | 2 × Wiegand 26-bit, 2 × iButton |
| Cards | 2,000 per controller |
| Event memory | 32,000 events |
| Relays | 4 |
| Doors | 1 bidirectional door (entry and exit reader) or 2 unidirectional doors |
The connector's trackbase002 driver configures TrackBase002 controllers,
reads their events and opens their doors over TCP/IP; RS-485 is not
supported. Its protocol was reverse-engineered from the vendor's software
and has not been verified against a live controller yet: verify on one
controller before moving a site over. It has limits (no holidays on the
controller, one set of schedules per card, door states not reported):
Controllers → TrackBase002 controllers.
The simulator tries Edge without hardware.
How it fits together
- The Edge web app (
/edge) is where people manage access and watch the doors. It updates live. - The Edge backend stores the rules, compiles each controller's configuration, and keeps the access log.
- The connector is a Windows service on a computer in the site's network. It connects out to Edge over HTTPS/WebSocket, so the site needs no inbound ports, and drives the controllers on its network.
- The controllers decide every badge read locally, from the configuration they hold, and drive the locks.
Concepts
Tenants and sites
A tenant is a customer organization: an organization on Entrosity Hub with Entrosity Edge enabled. Everything in Edge belongs to one tenant. A site is a location of the tenant; its time zone is the time zone of the schedules of the controllers on that site (Tenant settings, sites and audit log).
Connectors
A connector runs on an always-on computer in a site's network and reaches the controllers there. One connector can drive many controllers: on TCP/IP, and on RS-485 buses. Connectors update themselves when Edge has a newer version. See Connectors.
Controllers, doors and readers
A controller is one TrackBase002 (or a simulated one). Depending on its door mode it has one door with an entry and an exit reader, or two doors with one reader each. Each door has a lock relay and an unlock time. See Controllers, doors and readers.
Cardholders and cards
A cardholder is a person who passes doors. A card is a credential: a Wiegand 26-bit card (facility code and card number) or an iButton key. A card belongs to one cardholder or waits in the pool of unassigned cards. See Cardholders and cards.
Schedules and holidays
A schedule is a set of weekly time windows (for example Monday to Friday 08:00–18:00), plus optional holiday windows that apply on the tenant's holidays instead. See Schedules and holidays.
Access groups
An access group says who may pass where and when: its members (cardholders) may pass each of its doors during the schedule chosen for that door. See Access groups.
Configuration sync
Every controller holds a complete configuration: its doors and readers, the schedules it needs, the holidays, and every card that may pass one of its doors (at most 2,000). Any change that affects a controller gives it a new wanted version; Edge sends the new configuration through the connector until the controller has applied it. See Configuration sync and troubleshooting.
The access log
Controllers record events: access granted or denied, unknown cards, doors forced or held open, remote openings, controllers going online or offline. The connector uploads them in order, Edge stores each one once, and shows them live and in the history. See Live monitor and event history.
Signing in
- Sign in on Entrosity Hub (
https://hub.entrosity.com). - Open Entrosity Edge for your organization. You need a role in Edge: Tenant admin, Operator or Viewer (Roles and permissions). Organization admins give roles on the Hub (Organization members).
- If you belong to several tenants, choose one; the tenant menu in the sidebar switches between them.
The header has the language button (English, Български; the choice is shared with the Hub and the other products in this browser), the theme button, and the Entrosity Hub button back to the product launcher.
Finding your way around
The sidebar shows the pages of your tenant. Pages your role cannot use are hidden.
| Sidebar item | What it is | Page |
|---|---|---|
| Dashboard | The tenant at a glance | Dashboard |
| Live monitor | Door events as they happen, and the history | Live monitor and event history |
| Doors | Every door, its lock state, remote opening | Doors and remote opening |
| Cardholders | People and their cards and groups | Cardholders and cards |
| Cards | Every card, and the pool of unassigned cards | Cardholders and cards |
| Access groups | Who may pass which doors, and when | Access groups |
| Schedules | Weekly time windows and holidays | Schedules and holidays |
| Controllers | Controllers, their doors, readers and sync | Controllers, doors and readers |
| Connectors | Connectors and enrollment tokens | Connectors |
| Tenant settings | Default time zone, retention | Tenant settings |
| Sites | Locations and their time zones | Sites |
| Audit log | Who changed what | Audit log |
The menu under your name links to your account on the Hub (Manage account on Entrosity Hub), the Hub's products (All products, and Manage members for tenant admins) and signs you out (Sign out). Global admins (the Hub's platform admins) also get an Administration area with an Overview of all tenants and a global Audit log.
In this section
- Getting started: from an empty tenant to the first card read.
- Connectors, Controllers, doors and readers: the hardware side.
- Schedules and holidays, Access groups, Cardholders and cards: who may pass where and when.
- Live monitor and event history, Doors and remote opening, Dashboard: day-to-day work.
- Configuration sync and troubleshooting: what the sync statuses mean and what to do when something does not work.
- Roles and permissions, Tenant settings, sites and audit log.
- Trying Edge with the simulator: a complete trial without hardware.
For operators of the server: Running Entrosity Edge. For integrators: Edge API, Edge connector protocol and Edge connector.