What the Noon Elite kiosk does not do

1. No photo ID or document scanning.

   Where your procedure needs ID seen, the person at the desk looks at the document, and the kiosk keeps the record of the visit around it: name, company, host and both times. The optional badge photograph is of the visitor’s face, not a document.

2. No watchlist.

   Screening a visitor against a list happens before they arrive, by whoever owns the list, such as your export control or security officer; the kiosk records who actually came in.

3. No employee time and attendance.

   Your own staff clock in on your own system, and the fire roll call on the kiosk lists visitors and contractors, not employees, so your marshal still needs your staff list.

   Not built. Staff on the fire roll call is in pilot.

4. No pre-registration or pre-visit email for visitors.

   A visitor is recorded when they sign in at the kiosk, and your host tells them anything they need beforehand; the Permit to Work module is the exception, and emails a contractor a pre-arrival link for their permit.

   Not built. Visitor pre-registration is in pilot.

5. No questions, answers or signatures in the visitor sign in.

   The visitor accepts your wording and that acceptance is recorded, with the exact text; permit questions and signatures belong to the Permit to Work module, not to the visitor sign in.

   Not built. A health questionnaire with questions and answers is in pilot.

6. No separate wording for each kind of visitor.

   There is one wording per site, falling back to the company’s, and everyone who signs in accepts the same text. A line meant for contractors, such as where the asbestos register is kept, is shown to visitors and drivers who sign in as well, so write it to make sense to all of them.

7. No sign in stays open past 23:59 UTC.

   Anyone still signed in at 23:59 UTC, which is 00:59 in summer, UK time, is signed out automatically at that time. A contractor on a night shift drops off the roll call then, while still on site, and is back on it only if they sign in again; the record shows the automatic time, not when they left.

8. No nationality field.

   Where ITAR or List X asks for it, reception asks and records it; your own wording on the kiosk can tell visitors to declare it at the desk, and the kiosk stores only that they accepted that wording.

9. No purpose of visit field.

   The host the visitor came to see is recorded and the reason is not, so a site working to TAPA FSR or ITAR guidance records the purpose somewhere else.

10. No record of a badge coming back.

    With the badge module, the request, approval and print are logged and the sign out time is recorded; collecting the badge at the door, and reconciling it, is reception’s job.

11. Permit to Work is early access and has not yet run at a customer.

    If permits are the reason you are buying, watch the ten minute walkthrough recorded on a demonstration site, treat the first months as a pilot, and keep your paper permit until the module has proved itself on your jobs.

12. No integrations beyond a webhook.

    The kiosk posts a message to one Microsoft Teams or Slack channel per site; there is no link to access control, your staff directory or an HR system, and the register comes out as a spreadsheet export.

How the Teams message worksPermit to Work, and the walkthroughWhich fields each standard namesThese lines in a requirements checklist you can send to any supplier