Silent duress
Reception enters a duress code as if doing routine work. The screen carries on as normal while the workspace goes into lockdown and admins are alerted. The code is stored encrypted.
Security & compliance
BeckonDesk treats the gate as a control point. Names are checked before entry, people are accounted for during an evacuation, and each customer’s records stay inside their own workspace. This page explains how each of those works, including the limits.
Denied-party screening
Every sign-in is checked against your own watchlist and five public sanctions lists, more than 100,000 names and aliases in all, refreshed daily. Matching is fuzzy, so a near-spelling still scores. A strong match is refused at the kiosk, a borderline match is held until an admin clears it, and your team is alerted either way.
Evacuation & mustering
Start an evacuation from the admin app, or by pressing and holding on any kiosk; either way your admins are emailed. Everyone signed in at that moment (visitors, contractors and staff who signed in at a kiosk) lands on one live board and stays there until they are marked, even if they sign out. Fire marshals open it on their own phones from a QR link, with no app or login, and mark each person Safe, Missing or Unaccounted. When you give the all-clear, print the board or download the roll-call CSV for your records.
Active security
Reception enters a duress code as if doing routine work. The screen carries on as normal while the workspace goes into lockdown and admins are alerted. The code is stored encrypted.
Lockdown stops new sign-ins at every kiosk and on visitors’ phones, while sign-out and evacuation keep working. Admins are told by email, Teams and Slack, the console shows a banner, a connected door controller gets a lockdown signal, and the event goes in the audit log.
When you turn it on, BeckonDesk sends a signed grant message to your door controller or access middleware at check-in, and a revoke at check-out or automatic sign-out. It is a vendor-neutral webhook that your system consumes.
The Security page lists overstays (6 hours by default), visitors who never signed out, odd-hours arrivals (judged in each site's time zone), and repeated “denied” door events sent in by your own system. The list is worked out when you open the page; it is not pushed to anyone.
Every record created, changed or deleted in your workspace is written to its audit log with the user, time, IP address and what changed. Admins can read it and export it as CSV. The app has no way to edit or delete audit entries, and retention purges leave them in place.
Export the visitor log, contractor compliance, staff timesheets, the screening log, each evacuation's roll call and the audit trail as CSV, plus a 30-day evidence pack for auditors. Admins can also export one person’s records, or erase that person, to answer a privacy request. Erasure reaches their visits’ signatures and custom-field answers too; the DPA lists what it covers and what it doesn’t.
Read more about lockdown and silent duress and about door controller, directory and webhook integrations.
Data & tenancy
BeckonDesk is a multi-tenant service. All customers’ records are held in one shared PostgreSQL database, and every record carries the ID of the workspace it belongs to. The application filters every query by that ID, so people signed in to your workspace see only your records. If the same person visits two customers, each customer has its own separate record of them.
Ask about our data modelThe workspace filter is applied by the data layer to customer tables, and users limited to certain sites are filtered to those sites as well. This is an application control. Customers do not each get a separate database.
BeckonDesk platform administrators can open a workspace to help with a support request. Each session lasts at most 30 minutes and is recorded in our platform log with who opened which workspace and when. Anything changed during the session goes in your own workspace audit log as “BeckonDesk support” with the staff member’s email address.
BeckonDesk doesn’t use facial recognition, take visitor photos or store biometric identifiers. It does store signatures when you collect them, so check how your own state’s privacy laws treat those.
Each workspace chooses how long records are kept: 30 or 90 days, 6 months, 1 or 2 years, a custom number of days, or forever. The default is 365 days. Older visits, pre-registrations, signatures, deliveries, staff attendance, notification logs, access events and roll-call marks are purged on that schedule. The audit log is kept, with the personal details of purged visits cleared from it. For help choosing a period, see US visitor log retention rules and visitor logs under US state privacy laws and visitor records under UK GDPR.
When a subscription ends, the workspace is archived and its data kept so it can be restored. On written request to [email protected], BeckonDesk permanently deletes it: every record it owns, stored files included, in one operation. Backups expire after 7 days.
Platform & infrastructure
The BeckonDesk apps run in Azure’s East US region and the database in Central US. There is no choice of region. Azure holds ISO 27001, SOC 2 and other independent audit reports for its platform; those are Microsoft’s certifications, not BeckonDesk’s. Our own controls are below.
Browsers and kiosks reach BeckonDesk over HTTPS. The database accepts only connections using TLS 1.2 or later, and Azure encrypts the database and its backups at rest with AES-256. Integration secrets are also encrypted inside the database.
Your administrators and staff sign in with BeckonDesk accounts, using an email address or a Microsoft account, through Microsoft Entra External ID. Roles and site limits keep each person to what they need.
The API’s secrets, including the database connection and the payment and email credentials, are held in Azure Key Vault, not in source code. The database firewall does not accept connections from the open internet, only from within Azure, and each connection needs TLS and a password.
Azure backs up the database automatically with a 7-day point-in-time restore window, kept in the same region (there is no geo-redundant copy). An automated health check runs every 6 hours, the API checks its own error logs every 15 minutes while it is running and emails alerts, and Azure platform health alerts are on.
Azure OpenAI, in a US Data Zone deployment, sees three things: the name and company of a visitor with a borderline sanctions match, to add a likely-namesake note for the admin; parcel label images you scan in the mailroom (BeckonDesk doesn’t keep the image); and error-log excerpts for our own troubleshooting, with emails, phone numbers, IP addresses and tokens removed. Under Microsoft’s terms, these prompts are not used to train foundation models.
We collect what’s needed to manage access and don’t store government ID documents. Pre-registered visitors, contractors and staff are emailed a pass link; kiosk walk-ins are not. Platform email is sent through Azure Communication Services in the United States, and Cloudflare carries traffic to app.beckondesk.com. The Data Processing Agreement lists every sub-processor and covers UK and EU GDPR transfers.
Uptime for the API, database, email, admin app and kiosk app over the last 90 days is public on the BeckonDesk status page. The apps sleep when idle, and those periods show as “asleep” rather than down.
Identity & access
People sign in with an email address or a Microsoft account through Microsoft Entra External ID, and a session lasts 8 hours. Sign-in through your own identity provider is not offered today.
Admin, Receptionist and Viewer (read-only) roles. Any user can be limited to certain sites, and an Admin limited that way cannot change workspace-wide settings or billing.
Map Microsoft Entra ID groups to your host list and to the Admin, Receptionist and Viewer roles. Sync runs on the schedule you set or on demand, and can remove people who leave every group.
Any identity provider that supports SCIM 2.0 can create and deactivate users. Users created this way start as Viewers.
Joining an existing workspace is by invitation only, so nobody can sign themselves up into another company’s site.
API keys can be limited to a list of IP addresses and given an expiry date. Outbound webhooks carry an HMAC-SHA256 signature so your system can check they came from BeckonDesk, and a delivery ID that stays the same on a retry, so your system can ignore a repeat.
We’ll screen a real sanctioned name and walk a full muster on a call.