Grouped the way the platform is grouped. Each entry says what it does and what it does about the awkward cases, because the awkward cases are where a site access system is actually judged.
Choose any combination. With nothing selected you are looking at all of it.
Showing 28 of 28
Visitors
Invitations and pre-registration
Send a visitor or contractor a single-use link that already knows the site, the window and the requirements.
Email and SMS, per organisation, per event type.
A crew invitation creates one invitation and one approval per person, never one per company.
An invitation can be sent again from the system mailbox when the first one bounced.
Visitors
The visitor register
One record per person, with the visit history attached to it.
Correct a name, merge nothing by accident: a duplicate is refused and the existing record is surfaced instead.
Removing somebody archives the profile. The visit history stays, because an evacuation roll has to be able to name a person who was on site.
Retention keeps running either way, and a disposed profile says so rather than showing a blank.
Visitors
Visit types you configure
What a visitor is asked at the door is a tenant setting, not a code change.
One renderer serves reception, the kiosk and the phone, so a required field cannot be drawn in one place and enforced in another.
The form offers exactly the options the server enforces, and nothing else.
Visitors
Reception
Check a visitor in, print a badge, tell the host, and hold anything that needs a second look.
The host is notified by email and by text, and again if the visitor is still waiting.
A waiting visitor escalates when nobody responds, and can be reassigned to another host.
A held visit is cleared or denied by a named person, and the decision is on the record.
Visitors
QR passes and kiosk check-in
Contactless arrival at an unattended lobby, from a printed poster or a phone.
The kiosk route carries the site’s own check-in token; the site comes back from the server rather than being asserted by the device.
Installable as a kiosk app, and it keeps working through a dropped connection.
Passes expire with the visit window plus a configured late grace period.
Contractors
The contractor register
Every company and every individual working on your sites, with their current status.
Pending, active, suspended, expired. One status, derived from the evidence, never typed in by hand.
A contractor becomes active when an administrator approves them, and not before.
Contractors
Guided onboarding
Request the right documents, assign the right inductions, in one action.
The wizard resolves what this trade at this site actually needs, then sends one link that carries the whole journey.
Documents and induction happen on the same link, in order, with progress saved.
The invitation email names the outstanding documents from the server’s own records, so the list cannot drift from what is being waited on.
Contractors
Shifts and timesheets
Schedule the work, record the hours, approve or reject them.
A contractor accepts, declines or proposes an alternative, and the site team is told which.
Timesheets are submitted, reviewed and approved or returned with a reason.
Contractors
Work orders
Attach the job to the people, the site and the documents it needs.
Assignment notifies the contractor.
Supporting documents live with the order rather than in somebody’s inbox.
Compliance & WHS
Document verification
Licences, insurances and certificates, reviewed by a person and tracked to expiry.
Optical character recognition reads the fields off the upload and puts them in front of a reviewer. It never approves anything on its own.
Approve or decline with a reason; a decline is the message that tells the contractor to upload again.
Expiry is monitored and warned about before it bites.
Compliance & WHS
Document groups
What a trade needs, and what a particular site needs on top of it.
A second site can ask for its own extra documents without asking again for the ones the first site already verified.
Changing a requirement tells the people it now applies to.
Compliance & WHS
Inductions
Author the content, assign it, and hold access until it is passed.
Attempts are limited and counted; running out notifies the site team rather than stranding the contractor.
Completion is recorded against the person, with the version they were shown.
Compliance & WHS
Incident reporting
Near miss, injury or illness, dangerous incident, security breach, property damage, environmental.
Classified by mechanism and severity, with the notifiable categories named the way a regulator names them.
Investigation status is tracked, and the report renders to PDF.
Compliance & WHS
Site policies and acknowledgement
Publish the rules for a site and record who accepted which version, when.
An outstanding acknowledgement can hold site access.
Acceptance is a record with a version and a timestamp, not a checkbox that vanishes.
Site operations
Live on-site roster
Who is on this site right now, updated as it happens.
A server-sent event stream, not a page refresh.
When the roster cannot be read the screen says so, because a headcount that is wrong is more dangerous than a headcount that is missing.
Site operations
Emergency muster
Activate a muster and the on-site list becomes the roll.
Mark people accounted for as they reach the point, and see who is still outstanding.
The evacuation roll downloads as a PDF for a warden who is off the network.
Musters resolve, and the history is reportable afterwards.
Site operations
Geofenced check-in
Arrival is confirmed against the site boundary, on the server.
The device reports coordinates; the server decides. A photographed QR does not work from the car park.
A refusal reports neither the distance nor the radius, so the response cannot be used to map the fence.
Site operations
Access credentials
Issue, revoke and reinstate passes, with the reason on the record.
A credential cannot be issued to somebody who has not been approved.
Archiving a contractor revokes what they hold.
Barrier release can be handed to a site access control system over a documented, signed bridge; where no bridge is configured the platform says so rather than pretending it opened something.
Site operations
Safety alerts
Broadcast to the people who are on site, on the channels they will see.
Email and SMS, with per organisation channel configuration for every event type.
Delivery is tracked, retried with backoff, and counted against a service level.
Insight
Analytics
Arrivals, occupancy, compliance and activity over time.
Today against yesterday, because a bare number answers nothing.
Averages are taken over days that saw arrivals, and the chart says so.
Save a column layout as a view, set a default, and schedule it to arrive by email.
Insight
A verifiable audit log
Append-only, hash-chained, and checkable on demand.
Append-only is enforced rather than assumed, so a deleted row is detectable instead of leaving an intact chain behind it.
A verify endpoint answers the question directly, and reports a failed check differently from a broken chain.
Administration
Roles and permissions
80 granular permissions across 9 console roles, editable per organisation.
Permissions resolve per request, so a change takes effect while the administrator is still looking at the screen.
An actor can only assign roles below their own tier.
The console never gates on a role name. It gates on the permission, and so does the API behind it.
Administration
Site-scoped access
A user restricted to one site cannot read another one, through the console or the API.
Scoping is enforced server-side on the endpoint, not by hiding a menu item.
A record outside your scope answers 404 rather than 403, so identifiers stay unenumerable.
Administration
Sign-in and MFA
Password, Google or Microsoft, with multi-factor that remembers a device for a day.
A known device on a known network is not challenged again for 24 hours; a new device or a new network is.
Revoking a session or resetting MFA revokes every trusted device with it.
Administration
Notification control
59 branded message templates, with the channels for each under your control.
Email through your own SMTP relay or a delivery provider; SMS as an opt-in.
Every message is queued in an outbox with its delivery state, so "was this person actually emailed?" is a question with an answer.
Administration
Retention and disposal
Say how long you keep personal information, and have the platform actually do it.
Identity images live in a separate store, so disposal deletes rows rather than relying on somebody remembering to null a column.
Export or purge everything held about one subject.
Administration
Outbound integrations
Send events where your organisation already looks.
Signed webhooks and Microsoft Teams cards.
SharePoint lists, a SharePoint document mirror and Power BI push datasets, each of which names the exact setting it is missing rather than failing quietly.
See VCMS against your own sites
A walkthrough with your site list, your contractor mix and the compliance evidence you actually have to collect. No obligation, and no access to anybody’s live data.
