Skip to content

Role guide

Hosts video guide

Employees who invite visitors, meet them in the lobby and stay with them on site.

These short videos support your own staff training records. They do not certify anyone and do not replace your security awareness or export-control training.

Start here

4 videos, about 4 minutes

  1. Read the transcript

    At a defense plant or any regulated site, the front desk should know who is walking in, screen them, and keep a record of every decision.

    A host invites their visitor ahead of time. When the visitor fills in their details, SecurePoint screens them against U.S. and international sanctions and restricted-party lists.

    Once they're cleared, a QR code arrives by email.

    At the lobby kiosk, they scan the code and their ID, sign the visitor agreement, and take a badge photo.

    If a name looks like a possible match, the visit is held until a reviewer decides, and their reason goes on the record.

    When everything checks out at check-in, the host gets an email that their visitor has arrived, and the front desk prints the badge.

    Every check-in, screening result and decision is logged, so when an auditor asks, you can export the evidence.

    SecurePoint Visitor. Screen visitors at check-in, and keep the decisions on record.

    Video 1: SecurePoint Visitor product tour

    1:17

    What your visitor goes through.

    A host invites a visitor, the visitor is screened when they register and checks in at the lobby kiosk, and the front desk prints the badge. A possible match holds the visit for a reviewer, and every check-in, screening result and decision can be exported as evidence.

  2. Read the transcript

    Step 1. Open your Host Hub invitation from SecurePoint USA. Don't forward it. Select Open Host Hub.

    Step 2. Check it greets you by name, then select Enter Host Hub.

    Step 3. Create a password: at least 12 characters, with upper and lower case letters and a number. Select Create password and enter Host Hub.

    You're in Host Hub. Bookmark it for next time.

    Step 4. Next time, open your bookmark, enter your email and password, and select Sign in with email.

    If the page says your invitation has expired, ask your administrator for a new link.

    Screen visitors at check-in. Keep the decisions on record.

    Video 2: How to sign in to Host Hub

    0:59

    Sign in to Host Hub the first time, and every time after.

    A how-to for hosts: open your Host Hub invitation, create a password, bookmark Host Hub, and sign in with your email next time.

    Good to know: If your company uses Microsoft accounts, select Sign in with Microsoft instead. This video shows the password steps, for hosts without one.

    • Hosts
  3. Read the transcript

    Step 1. Open Host Hub and start a new invite.

    Step 2. Enter your visitor's name, email and company, then the date and time of the visit.

    Step 3. Pick the purpose, and tick what the visit requires, like the NDA. Then send it.

    Step 4. Your visitor gets an email link. On their phone, they add their details and nationality, and their ID if your organization requires it.

    Step 5. When they submit, SecurePoint screens them. Once they're cleared, their QR code for the kiosk arrives by email.

    Screen visitors at check-in. Keep the decisions on record.

    Video 3: How to invite a visitor

    0:55

    Invite a visitor, step by step.

    A how-to for hosts: start an invite in Host Hub with the visitor's details, including their country, the visit date and time, and what the visit requires. Once the visitor registers on their phone, giving their nationality, and is screened and cleared, their QR code for the kiosk arrives by email.

    Good to know: The invite also asks for your visitor's country. It starts on United States, so change it for a visitor from another country. Your visitor also gives their nationality when they register, and if the two differ, screening uses the one that needs closer review.

    • Hosts
  4. Read the transcript

    Hosts invite their own visitors from Host Hub, with the date and time of the visit and what the visit requires, like the NDA.

    The visitor gets a link by email. On their phone, they add their details and capture their ID if the site asks for it. Sites that require the NDA at every visit have them sign it at check-in.

    When they submit, SecurePoint screens them against sanctions and restricted-party lists. If a name needs a closer look, a reviewer can decide before the visitor arrives.

    Once they're cleared, their QR code arrives by email, and their host is told.

    On the day, the front desk sees them under Expected Today.

    At the kiosk, they scan the code, and their details are already filled in from the invitation.

    When they're checked in, their host gets an email that their visitor has arrived.

    SecurePoint Visitor. Screen visitors at check-in, and keep the decisions on record.

    Video 4: Pre-register a visitor

    1:14

    What happens after you send the invite.

    A host invites a visitor from Host Hub, the visitor registers on their phone and is screened when they submit, and a name that needs a closer look goes to a reviewer before the visit. At sites that require the NDA at every visit, the visitor signs it at check-in. Once cleared, the QR code arrives by email, the front desk sees the visitor under Expected Today, and the kiosk fills in their details from the invitation.

When it comes up

Watch these when the situation applies at your site.

  • Read the transcript

    Step 1. In Host Hub, open the Visitors tab.

    Step 2. Read each visitor's tag. Invite sent means they haven't registered yet. Cleared means they've registered and passed screening. Under security review means your security team is reviewing them.

    Step 3. If a visitor's link has expired, or they're visiting again, click Re-invite.

    Step 4. Pick the new date and start time, then click Create Invite.

    That emails your visitor a new invite with a new link. If sending fails, you'll see Email not sent.

    The new invite appears at the top. Your earlier one stays as it was.

    Screen visitors at check-in. Keep the decisions on record.

    How to check your invites and re-invite a visitor

    1:00

    Check where your invites stand, and re-invite a visitor for a new date.

    A how-to for hosts: in Host Hub, open the Visitors tab and read each visitor's tag. Invite sent means they haven't registered yet, Cleared means they've registered and passed screening, and Under security review means your security team is reviewing them. If a link has expired or the visitor is coming again, select Re-invite, pick the new date and start time, and Create Invite. Your visitor is emailed a new invite with a new link, or you see Email not sent if sending fails, and your earlier invite stays as it was.

    Good to know: A registration link stops working 14 days after the invite, but Host Hub still shows the invite as sent. Re-invite if your visitor says the link doesn't work.

    • Hosts
  • Read the transcript

    Step 1. Open your invitation email and select Complete Pre-Registration.

    Step 2. Check your name and email, then add your phone number and date of birth.

    Step 3. Choose your nationality. It's required, and screening uses it.

    Step 4. Add your company, then take a photo of the front of your ID if it's asked for.

    Step 5. If an agreement appears, read it to the end and type your name to sign. Some sites have you sign it at check-in instead.

    Step 6. Select Complete Registration. Once you're cleared, your QR code appears and arrives by email. Bring it, and your ID, on the day.

    Screen visitors at check-in. Keep the decisions on record.

    How to register for your visit

    1:03

    Send this to your visitor after you invite them: how they register on their phone.

    A how-to for visitors: open your invitation email and select Complete Pre-Registration. Check your name and email, add your phone number and date of birth, and choose your nationality, which is required and used in screening. Add your company, and a photo of the front of your ID if it's asked for. If an agreement appears, read it to the end and type your name to sign; some sites have you sign it at check-in instead. Select Complete Registration. Once you're cleared, your QR code appears and arrives by email, so bring it and your ID on the day.

  • Read the transcript

    Step 1. At the kiosk, tap Scan ID or QR, and show the QR code from your email.

    Step 2. Your details fill in from your invitation. Check them, add anything missing, and continue.

    Step 3. If the kiosk asks, scan the front of your photo ID.

    Step 4. Answer any questions your site asks, like your visitor type or the devices you brought.

    Step 5. If an NDA appears, read it to the end, then sign. You can make the text bigger.

    Step 6. Watch the safety briefing if your site has one, then take your badge photo if asked.

    When the kiosk says Checked In, you're done. If it says Waiting for Host Verification, wait there for your host.

    Screen visitors at check-in. Keep the decisions on record.

    How to check in at the kiosk with your QR code

    1:11

    Send this to your visitor before they arrive.

    Step by step, a visitor checks in at the lobby kiosk with the QR code from their email: they confirm the details from their invitation and add anything missing, scan a photo ID when the site asks, answer the site's questions, read an NDA to the end and sign it if one appears, watch a safety briefing if the site has one, take a badge photo if asked, and see Checked In, or Waiting for Host Verification at sites with autonomous check-in.

  • Read the transcript

    Step 1. Your visitor is at the kiosk. Your arrival email or text tells you.

    Step 2. Go to the kiosk yourself. Don't verify from your desk. Tap Host Verify.

    Step 3. Pick your visitor.

    Step 4. Type your own name.

    Step 5. Check their photo ID, and that they match it. Tick both boxes.

    Step 6. Select Verify and continue to print, then Print Badge. Done.

    If the visit needs an escort, stay with your visitor.

    How to do Host Verify at the kiosk

    0:38

    If your site's kiosk asks visitors to wait for their host: Host Verify, step by step.

    A how-to for hosts at sites with autonomous kiosk check-in: when your visitor is waiting, go to the kiosk yourself, tap Host Verify, pick your visitor, type your own name, check their photo ID and print the badge.

    Good to know: Host Verify is only on kiosks set to autonomous check-in. For a foreign national, the kiosk may ask you to confirm three more things before the badge prints.

    • Hosts
  • Read the transcript

    Step 1. Your visitor is at the kiosk. Your arrival email or text has a four-digit code.

    Step 2. Go to the kiosk yourself. Don't verify from your desk. Tap Host Verify.

    Step 3. Pick your visitor.

    Step 4. Type your own name, then the code from your email.

    Step 5. Check their photo ID, and that they match it. Tick both boxes.

    Step 6. Select Verify and continue to print, then Print Badge. Done.

    If the visit needs an escort, stay with your visitor.

    How to do Host Verify at the kiosk, with a host code

    0:40

    The same Host Verify steps, when your arrival email or text has a four-digit code.

    The same Host Verify how-to for sites that send hosts a four-digit code: go to the kiosk yourself, tap Host Verify, pick your visitor, type your own name and the code from your arrival email or text, check their photo ID and print the badge.

    Good to know: Host Verify is only on kiosks set to autonomous check-in. For a foreign national, the kiosk may ask you to confirm three more things before the badge prints.

    • Hosts
  • Read the transcript

    Your visitor lost their badge. You can print a new one at the kiosk.

    Step 1. Tap Host Verify.

    Step 2. Under Lost or damaged badge, tap Reprint a Badge.

    Step 3. Pick your visitor from the list of people on site.

    Step 4. Tap Send to get your code. Nothing prints without it.

    It comes by email, and by text if you've opted in. It works once, for this visit only, for 15 minutes.

    Step 5. Check it's your visitor, then enter the code at the kiosk.

    Step 6. Choose why you need a new badge. If it's missing, choose Badge lost.

    That also alerts your compliance contacts, because the old badge still looks valid.

    Step 7. Tap Print New Badge, and check the printer.

    The new badge is marked as a reprint, with its number and the time.

    A visitor can't print a new badge without your code.

    How to reprint a lost badge at the kiosk

    1:15

    When your visitor loses a badge: print a new one at the kiosk with a code sent to you.

    A how-to for hosts at sites with autonomous kiosk check-in: when your visitor has lost their badge, tap Host Verify at the kiosk, then Reprint a Badge, pick your visitor and send yourself a one-time code. Check it's your visitor, enter the code, choose why you need a new badge, and print it. The new badge is marked as a reprint, and choosing Badge lost also alerts your compliance contacts.

    Good to know: Reprint a Badge is on the Host Verify screen, so it's only on kiosks set to autonomous check-in. The code goes to the email on file for the visit's host, and no badge prints without it.

    • Hosts
  • Read the transcript

    Step 1. If your site sends end-of-day emails, you get this one when a visitor of yours has no recorded departure.

    Step 2. If they have left, tap Check out.

    Step 3. Choose when they left: Just now, or Earlier, and the time.

    Step 4. Pick a reason if asked, then Confirm Checkout.

    The visit closes with the departure time you confirmed.

    Still on site? There is nothing to do.

    How to check out your visitor from the end-of-day email

    0:40

    If your site sends end-of-day emails: check out a visitor who left without checking out.

    A how-to for hosts at sites that send the end-of-day email: when a visitor of yours still shows as on site at the end of the day, tap Check out in the email, say when they left, pick a reason if asked, and confirm. The visit closes with the departure time you confirmed.

    Good to know: The end-of-day email is off by default. If your site doesn't send it, ask the front desk to check your visitor out.

    • Hosts
  • Read the transcript

    Step 1. When your visitor checks out, you may get an email asking for an After Visit Report. Select Complete After Visit Report. You don't need to sign in.

    Step 2. Answer the two questions. Both start on No.

    If you shared controlled technology or technical data, choose Yes, describe what was shared, and add the ECCN or category if you know it.

    If you discussed pricing or commercial terms, choose Yes and summarize them.

    Step 3. Write a short meeting summary: the program, who visited, and what was discussed. Then select Submit report.

    Once it's filed, you'll see Thanks. Until you file it, you'll get email reminders.

    Screen visitors at check-in. Keep the decisions on record.

    How to file an after-visit report

    1:06

    When your visitor checks out: file the after-visit report your email asks for, step by step.

    A how-to for hosts: when your visitor checks out, you may get an email asking for an After Visit Report. Select Complete After Visit Report; you don't need to sign in. Answer the two questions, which both start on No. If you shared controlled technology or technical data, choose Yes, describe what was shared, and add the ECCN or category if you know it. If you discussed pricing or commercial terms, choose Yes and summarize them. Write a short meeting summary and select Submit report. Once it's filed, you see Thanks; until you file it, you get email reminders.

    Good to know: Your organization chooses whether hosts file a report after every visit, and it's on by default. A foreign national's visit to an ITAR or DCSA site always needs one.

    • Hosts
  • Read the transcript

    When the site requires it, a visitor who lists another country of citizenship acknowledges they're a foreign national, and that the visit may need an escort and more review.

    The kiosk asks the visitor to wait for their host. The host gets an email asking them to come to the kiosk, check the visitor's photo ID, and print the badge. It also says the visit needs an escort.

    At the kiosk, the host enters their name and confirms three things: they checked the visitor's nationality on their ID, they'll escort them at all times, and they won't share export-controlled technical data without authorization. Then the kiosk prints the badge.

    When the visitor checks out, the host is asked for an after-visit report: whether any controlled technical data was shared, and a short summary. If it's late, reminders follow.

    SecurePoint Visitor. Screen visitors at check-in, and keep the decisions on record.

    Foreign-person visits

    1:13

    When your visitor is a foreign national and needs an escort.

    When a site requires it, a visitor who lists another country of citizenship acknowledges they're a foreign national. Their host gets an email to come to the kiosk. There, the host confirms they checked the visitor's nationality on their ID, that they'll escort the visitor at all times, and that they won't share export-controlled technical data without authorization. Then the kiosk prints the badge. At check-out, the host is asked for an after-visit report.

    Good to know: The come-to-the-kiosk email and the host's confirmation at the kiosk happen only on kiosks set to autonomous check-in. At other sites, the visitor waits for the front desk.

  • Read the transcript

    Admins set one NDA and safety briefing for the whole organization, and add exceptions for a site or a visit purpose.

    Before a change makes kiosks refuse visitors, or stops asking for a step, the page names the sites it affects.

    Hosts can add them to an invite. The visitor acknowledges them while registering, or at check-in when the site requires them at every visit.

    At sites that turn it on, visitors who list U.S. citizenship attest they're a U.S. person. Others acknowledge their visit may need an escort and more review.

    At the kiosk, signing stays locked until the visitor reaches the end of the agreement, and the safety briefing comes next.

    At the front desk, visitors can sign on their own phone or right at the desk, with a typed or drawn signature.

    The signature is saved with the visit, along with the name they gave and the time, and staff can open a receipt.

    And if a required step is missing, the front desk sees what's still needed before the badge can print.

    SecurePoint Visitor. Screen visitors at check-in, and keep the decisions on record.

    NDAs and safety briefings

    1:27

    The agreements your visitor is asked to sign.

    Admins set one NDA and safety briefing for the whole organization, with exceptions for a site or a visit purpose, and before a change would make kiosks refuse visitors or stop asking for a step, the page names the sites it affects. Visitors acknowledge them when they register, or at check-in when the site requires them at every visit, and sign at the kiosk, on their phone, or at the desk. A badge waits until the required steps are done.

Other videos

41 more, each labeled with the roles it is for.

Show 41 more videos
  • Read the transcript

    Not every visitor is invited ahead of time. At the lobby kiosk, a walk-in starts by scanning their photo ID.

    Their name fills in from the ID. They add their company and a way to reach them, then pick the person they're here to see and say why they're visiting.

    They give their country of citizenship, and at an export-controlled site, they confirm the attestation the site requires.

    Then they answer any questions the site asks, sign the NDA if one is required, and take a badge photo.

    SecurePoint screens them against sanctions and restricted-party lists. Once they're cleared, the kiosk checks them in, or, at sites with autonomous check-in, asks them to wait for their host.

    Their host gets an email that they've arrived, and the front desk sees them on site, with their photo and ID on file.

    SecurePoint Visitor. Screen visitors at check-in, and keep the decisions on record.

    Walk-in check-in

    1:14

    A visitor with no invite checks in at the lobby kiosk: their photo ID fills in their name, they add their contact details, host, purpose and country of citizenship, answer the site's questions, sign the NDA if one is required and take a badge photo, and are screened before the kiosk checks them in, or, at sites with autonomous check-in, asks them to wait for their host.

    Good to know: If the name doesn't fill in from the ID, type it. Kiosks running the SecurePoint Kiosk app keep the ID photo but don't read it.

  • Read the transcript

    Admins set up a badge template for each visitor type: the shape, a black or red stripe, and what the badge shows.

    A print check confirms the layout fits the label before anything prints.

    At the front desk, a badge is available once the visitor is checked in and cleared.

    It carries their photo, company and host, the hours it's valid, and a QR code. At an export-controlled site, it also shows their screening and escort status.

    It prints on a Brother QL-820NWB label printer. Finish in your browser's print window if one opens.

    The visit record now shows the badge was sent to print.

    At the end of the visit, they scan the badge's QR code at the kiosk to check out.

    SecurePoint Visitor. Screen visitors at check-in, and keep the decisions on record.

    Badges that print

    1:08

    Admins set up a badge template for each visitor type, a print check confirms the layout fits the label, and the front desk prints the badge on a Brother QL-820NWB. At the end of the visit, the badge QR code checks the visitor out at the kiosk.

    Good to know: Red prints only on DK-2251 black-and-red labels. The SecurePoint Kiosk app on an iPad or Android tablet and the Print Connector on a Windows PC print red and black. AirPrint on an iPad and the Android print dialog print black only.

  • Read the transcript

    A badge is only available once the visitor is checked in and approved.

    While a possible match is under review, the visitor is asked to wait for staff, and the badge stays unavailable.

    Here, the visitor agreement and a photo of their ID are missing, so the badge is refused, and the desk sees what's still needed.

    Once those steps are done, the badge is available.

    SecurePoint Visitor. Screen visitors at check-in, and keep the decisions on record.

    When a check-in step is missing

    0:42

    A badge is available once a visitor is checked in and approved. While a possible match is under review, the visitor waits for staff and the badge stays unavailable. In this visit, the visitor agreement and a photo of the ID are missing, so the badge is refused until the front desk completes them.

    Good to know: A missing headshot also blocks the badge, because badge photos are on by default. At sites with autonomous kiosk check-in, the badge also waits for Host Verify: the host verifies at the kiosk, or the desk selects Complete host verify.

  • Read the transcript

    When an auditor asks how visitors were screened, an admin opens the Evidence Center and picks a template and a date range.

    SecurePoint builds a ZIP file with screening results, review decisions and audit records from that period, and its manifest lists an SHA-256 checksum for each file.

    Evidence Pack History keeps each sealed pack, so a later download is the same file, with the same checksum.

    The audit ledger shows who did what, and when: check-ins, screening results, reviewer decisions, and exports.

    Users can't edit or delete ledger records, and exports from this page come with an SHA-256 checksum.

    SecurePoint Visitor. Screen visitors at check-in, and keep the decisions on record.

    Evidence packs and the audit trail

    1:03

    An admin picks a template and a date range in the Evidence Center, and SecurePoint builds a ZIP of screening results, review decisions and audit records, with a manifest that lists an SHA-256 checksum for each file. Evidence Pack History keeps each sealed pack, so a later download is the same file. The audit ledger shows who did what and when, and its CSV export comes with a checksum.

    Good to know: By default, only org admins and compliance managers can build or download evidence packs and export the ledger. Auditor accounts can view the ledger.

  • Read the transcript

    Sites can ask visitors to declare restricted devices, like phones, cameras and laptops, and say where they'll be kept during the visit.

    At the front desk, staff can record a declaration too, and it's saved with the visit.

    Turn on Detached camera mode, and visitors can take their badge photo on their own phone: scan the code, take the picture, and it appears on the kiosk.

    Visitors can make the agreement text larger while they read.

    When a visit is held, your compliance team gets an alert email, and, on plans with SMS, a text message too.

    After midnight, site time, visits still open from that day are closed and marked as not seen leaving, unless a review or Host Verify is still pending. Your compliance contacts get a summary of what closed.

    SecurePoint Visitor. Screen visitors at check-in, and keep the decisions on record.

    Features you might have missed

    1:10

    Restricted-device declarations at the kiosk and the front desk, badge photos taken on the visitor’s own phone with Detached camera mode, larger agreement text, alert emails (and text messages on plans with SMS) when a visit is held, and the overnight close of visits still open, with a summary of what closed.

    Good to know: Detached camera mode is in Admin, Kiosks, and off by default. Held-visit texts need a plan with SMS, and device declarations need SecurePoint to switch them on.

  • Read the transcript

    Continuous Monitoring re-screens the employees, contractors and vendors you enroll, as often as every night.

    Import your roster, or add people and companies one at a time.

    Each run checks them against the sanctions and restricted-party lists your organization has turned on.

    When a name comes back as a possible match, a case opens for review, and your compliance contacts get an email summary.

    Nothing is blocked automatically. Your team reviews each hit and records the outcome.

    Every run is kept in Screening History, and every decision is written to the audit trail.

    SecurePoint. Re-screen the people you work with, and keep the decisions on record.

    Continuous Monitoring

    0:57

    The employees, contractors and vendors you enroll are re-screened as often as every night. A possible match opens a case for review and sends your compliance contacts a summary email. Nothing is blocked automatically: your team records the outcome, and every run and decision is kept.

    Good to know: Continuous Monitoring is an add-on that SecurePoint turns on for your organization. By default, org admins and compliance managers use it.

  • Read the transcript

    The front desk runs the day from one screen: who's on site, who's waiting on a review, who's expected today, and who has left.

    Today's pre-registered visitors are listed ahead of time, and anyone past their expected time is flagged.

    When a visitor checks in and is cleared, their host gets an email, and a text if texting is set up for that host.

    At the end of the visit, the desk checks the visitor out, and the time and the staff member are recorded.

    If someone has to be removed, the desk can revoke the visit with a reason. The visit closes, and the visitor is recorded as denied.

    SecurePoint Visitor. Screen visitors at check-in, and keep the decisions on record.

    The front desk view

    0:58

    One screen for the front desk: who's on site, who's waiting on a review, who's expected today and who has left. Today's pre-registered visitors are listed ahead of time and late arrivals are flagged. When a cleared visitor checks in, their host gets an email. The desk checks visitors out with the time and staff member recorded, and can revoke a visit with a reason.

    Good to know: Revoke is not an early check-out: it records the visitor as denied, so use Check Out for a normal departure. Front desk staff can't check out or revoke a visit still under compliance review.

  • Read the transcript

    Step 1. On the front desk screen, open the visitor's record.

    Badge is available once they're checked in and cleared.

    If it lists steps missing for this visit, like the NDA or ID, finish those first, or the badge is refused.

    Step 2. Select Badge to open the preview, and make sure the print check has passed.

    Step 3. Select Print Badge, then finish in your browser's print window if one opens.

    Step 4. The visit record then shows the badge was sent to print.

    SecurePoint Visitor. Screen visitors at check-in, and keep the decisions on record.

    How to print a visitor's badge

    0:52

    How the front desk prints a badge: open a checked-in, cleared visitor's record, finish any steps missing for the visit, check the preview, then print, and the visit record shows it was sent to print.

    Good to know: If the badge preview shows the printer as Connector ready, the badge prints with no print window, including from a tablet running the SecurePoint Kiosk app. Browser fallback opens your browser's print window; on an iPad that is AirPrint, which prints black only.

  • Read the transcript

    Step 1. An admin turns on device declarations in the site's Device Policy.

    Step 2. At the kiosk, visitors say whether they've brought devices, like phones, cameras or laptops.

    Step 3. They pick each device and where it will be kept.

    For a locker, they type the locker ID, then continue.

    Step 4. If a declaration is missing, front desk staff can record it from the visit record.

    Choose how the devices are handled, add the locker, and save. It's saved with the visit.

    Screen visitors at check-in.

    Keep the decisions on record.

    How to record a visitor's devices

    0:52

    Step by step: an admin turns on device declarations for a site, visitors declare their devices and where each one will be kept at the kiosk, and front desk staff can record a missing declaration from the visit record.

    Good to know: Device declarations also need SecurePoint to switch the feature on. If the kiosk never asks about devices after you turn on Device Policy, contact SecurePoint.

  • Read the transcript

    Step 1. Connect the Brother QL-820NWB to the same network as the kiosk tablet, by Ethernet if you can, and load DK-2251 labels.

    Step 2. In Admin, open Printers and add a printer. Choose the QL-820NWB, give it a name staff will recognize, and pick its site.

    Step 3. Under How badges print, choose The check-in tablet prints directly. Then choose Let the tablet find and save the printer, and get a setup code.

    Step 4. On the tablet, tap the top-right corner five times and enter the PIN. On an iPad, open SecurePoint connection. On an Android tablet, open Badge Printing. Enter the setup code.

    Step 5. Choose the printer the tablet finds on the network. It checks the model, the labels, and that the printer is ready. Name it, then tap Connect to SecurePoint.

    Step 6. Back in Admin, select Send test badge. From then on, badges print from the tablet with no print window, as long as the SecurePoint Kiosk app is open.

    Screen visitors at check-in. Keep the decisions on record.

    How to set up badge printing

    1:17

    How an admin sets up badge printing from the check-in tablet: put a Brother QL-820NWB on the same network as the tablet, by Ethernet if you can, with DK-2251 labels. In Admin, add the printer, choose The check-in tablet prints directly and Let the tablet find and save the printer, and get a setup code. In Kiosk Settings on the tablet, enter the code, choose the printer it finds, and tap Connect to SecurePoint. Then send a test badge: from then on, badges print from the tablet with no print window while the SecurePoint Kiosk app is open.

    Good to know: To print from a Windows computer instead, choose A computer runs the SecurePoint Print Connector under How badges print. A printer with no paired device prints through the browser's print window.

  • Read the transcript

    Step 1. In Reports Overview, open Visitor Audit, and find the visitor's check-in date.

    Step 2. Back in Reports Overview, open Evidence Packs. Pick a template, and dates from before the visit to a few days after.

    Step 3. Select Generate to download a ZIP of screening results, review decisions and audit records for those dates.

    Step 4. Open the ZIP's manifest. It lists an SHA-256 checksum for each data file, so you can check each one.

    Step 5. Need it again later? Select Download ZIP in Evidence Pack History. You get the original sealed file, with the same checksum.

    Screen visitors at check-in. Keep the decisions on record.

    How to build an evidence pack for a past visit

    1:02

    A how-to for compliance teams: from Reports Overview, find the visitor's check-in date in Visitor Audit, generate an evidence pack whose dates cover the visit, and check its files against the SHA-256 checksums in the manifest. Evidence Pack History keeps the sealed pack, so Download ZIP returns the same file later, with the same checksum.

  • Read the transcript

    Step 1. SecurePoint turns on the Screening API for your organization and issues your API key.

    Step 2. POST the name to prescreen as the subject, with your key in the Authorization header. The key identifies your organization, so you don't send one.

    Step 3. Read the result: a screening ID, a risk level and score, the number of possible matches, and whether review is required.

    When review is required, the name goes to your compliance team's review queue, and the status reads pending.

    Step 4. Keep the screening ID. Later, GET the screening by that ID to read the stored result.

    Screen visitors at check-in. Keep the decisions on record.

    How to screen a name with the Screening API

    1:00

    A how-to for developers: once SecurePoint turns on the Screening API for your organization and issues your API key, POST a name to prescreen, read the screening ID, risk level and score, possible matches and whether review is required, then GET the stored result by that ID.

  • Read the transcript

    Step 1. When you're ready to leave, tap Check Out on the kiosk.

    Step 2. Scan the QR code on your badge, or find your name in the list.

    Step 3. Check that it's your visit, choose a reason if asked, then tap Confirm Checkout.

    You're checked out, and your checkout time is saved with the visit.

    Step 4, for admins. Keep Auto-close leftover visits on for each site. Visits still under review are left open.

    Other visits left open overnight are closed and marked as having no verified departure. Your compliance contacts then get a summary email.

    Screen visitors at check-in. Keep the decisions on record.

    How to check out at the kiosk

    0:59

    A how-to for visitors and site admins: tap Check Out on the kiosk, scan the QR code on your badge or find your name, and confirm it's your visit. Visits still under review stay open, and other visits left open overnight are closed and marked as having no verified departure.

  • Read the transcript

    Step 1. In Admin, open Kiosks. Name the tablet, like Lobby iPad, and pick its site.

    Step 2. Select Generate pairing code. A pairing code and a QR code appear.

    Step 3. On the tablet, open /kiosk/setup in Safari, Chrome or Edge. Enter the code, and tap Pair tablet.

    The tablet opens the kiosk welcome screen, and it's listed under Registered devices, with its site.

    Step 4. When you replace or retire a tablet, select Delete next to it and confirm. That revokes its access.

    Screen visitors at check-in. Keep the decisions on record.

    How to set up a lobby kiosk

    0:55

    A how-to for admins: in Admin, open Kiosks, name the tablet and pick its site, generate a pairing code, then open /kiosk/setup on the tablet in Safari, Chrome or Edge, enter the code and tap Pair tablet, and delete a tablet you replace or retire to revoke its access.

    Good to know: This video shows a kiosk in a web browser. For an iPad or Android tablet with the SecurePoint Kiosk app, see How to set up the SecurePoint Kiosk app.

  • Read the transcript

    Step 1. In the Compliance menu, open Adjudication Queue.

    This queue lists possible list matches that need a person's decision before the visit can continue.

    Step 2. Check the tab. Visitor check-ins are people at your sites. Screening reviews are names screened without a visit, such as a list you uploaded.

    Step 3. Read the counts. Needs decision is everything waiting on someone. The last three tiles count the decisions of the last 30 days. Anything that needs attention, such as an escalation, shows as a chip under the counts.

    A check-in from the last twelve hours is listed first. That visitor may still be standing at the front desk.

    A row marked Screening not finished has no complete result yet. That visitor stays on hold.

    Step 4. Select Assign to me. Other reviewers see that you have the case.

    Step 5. Open the case to review it.

    How to work the Adjudication Queue

    1:18

    A how-to for compliance reviewers: in the Compliance menu, open the Adjudication Queue. Visitor check-ins are people at your sites, and Screening reviews are names screened without a visit. Needs decision counts everything waiting on someone, the last three tiles count the decisions of the last 30 days, and anything that needs attention, such as an escalation, shows as a chip under the counts. A check-in from the last twelve hours is listed first, and a row marked Screening not finished keeps its visitor on hold. Select Assign to me so other reviewers see you have the case, then open it.

    Good to know: By default, only org admins and compliance managers can open the Adjudication Queue, run a screening again and record decisions.

  • Read the transcript

    A case opens when a visitor's name is similar to a name on a screening list. This video shows how to read one.

    Step 1. Start at the top. The header shows who the visitor is, who they came to see, and where. It also tells you the visitor is on hold.

    Step 2. Read the summary line. It tells you how many possible matches there are, on which lists, and which is closest.

    Step 3. Check the closest match. The visitor's details sit beside the list entry's, one row per detail.

    Read each row. Here the names are similar and the country is the same.

    The date of birth is different. That is often the clearest sign this is a different person.

    Some details cannot be compared, because one side does not have them. The ID document row is always yours to check against the visitor's document.

    Step 4. Under the table, check which list this is, the entry ID, and the list version that was used.

    Step 5. Look at every other possible match before you decide.

    If a word is new to you, the question mark beside it explains it.

    The similarity percent puts the matches in order. It is not a decision. You decide.

    Step 6. When you have looked at every possible match, move to the decision column on the right.

    A company case reads the same way. There is no date of birth, so compare the company's records with the list entry.

    How to read a possible match

    1:57

    A how-to for compliance reviewers: read a case from the top. The header shows who the visitor is, who they came to see and where, and the summary line shows how many possible matches there are, on which lists, and which is closest. Compare the visitor's details with the list entry's one row at a time, check the ID document yourself, and note the list, the entry ID and the list version. Look at every other possible match before you decide: the similarity percent puts them in order, but it is not a decision. A company case reads the same way, without a date of birth.

  • Read the transcript

    Step 1. Open the case and read the summary line.

    Step 2. Check the closest match. Here the date of birth is different.

    Compare it with the visitor's ID, not only with what they typed at check-in.

    Step 3. In the decision column, choose Not a Match. The text under it tells you what happens next. It clears the list match only. Host verification still applies.

    Step 4. This match is strong, so the program asks why. Choose Date of birth does not match.

    Step 5. Write the note. Say what you compared and what was different. Insert the comparison adds the details from the screen.

    Write it for someone who reads it a year from now.

    Step 6. Select Confirm Decision. Your name, your role and the time are saved with it.

    The case leaves the queue. The host still confirms the visitor before a badge prints.

    How to clear a case that is not the listed person

    1:19

    A how-to for compliance reviewers: when the closest match has a different date of birth, compare it with the visitor's ID, then choose Not a Match. On a strong match the program asks why, so choose the reason, and write a note that says what you compared and what was different. Confirm Decision saves your name, your role and the time. Not a Match clears the list match only: the host still confirms the visitor before a badge prints.

  • Read the transcript

    Sometimes the details match. Here the date of birth and the country are the same as the list entry, and the name is nearly the same.

    Do not clear a case like this on a hunch. For a match this strong, Not a Match needs a different date of birth or ID document, or a second reviewer.

    Step 1. The visitor stays on hold. Nothing on this screen releases them until a decision is recorded.

    Step 2. If you are not sure, choose Send for Senior Review. Choose the reason and write what you found. Your organization's compliance admins get an email.

    Your note stays on the case. The next reviewer sees it with your name.

    Step 3. If you are sure this is the listed person, choose Deny Access. Choose the reason and write the note. The program shows what will happen and asks you to confirm.

    Access is refused and no badge prints.

    Step 4. Follow your organization's own sanctions procedure from here. SecurePoint records the decision. It does not file reports for you.

    When the details match: senior review or deny access

    1:25

    A how-to for compliance reviewers: when the date of birth and the country match the list entry and the name is nearly the same, don't clear the case on a hunch. For a match this strong, Not a Match needs a different date of birth or ID document, or a second reviewer. If you're not sure, choose Send for Senior Review with a reason and a note, and your organization's compliance admins get an email. If you're sure it's the listed person, choose Deny Access: access is refused and no badge prints. SecurePoint records the decision; it does not file reports for you.

  • Read the transcript

    Sometimes a screening does not finish, for example when a list could not be searched in time.

    An unfinished screening is not a clean result. The visitor stays on hold, and the case cannot be cleared.

    Step 1. Open the case. It is marked On hold, screening not finished.

    Step 2. Select Run screening again. It checks the visitor against the lists again and puts the new result on this case. It does not decide the case.

    Step 3. Read the new result the same way as any case. Then record your decision.

    You can still deny or send the case for senior review without running it again.

    How to run a screening again when it did not finish

    0:57

    A how-to for compliance reviewers: sometimes a screening does not finish, for example when a list could not be searched in time. An unfinished screening is not a clean result, so the visitor stays on hold and the case cannot be cleared. Open the case, select Run screening again, and read the new result the same way as any case before you record your decision. You can still deny the case or send it for senior review without running it again.

  • Read the transcript

    Step 1. Find the case. Open Reports Overview, then Adjudication SLA. Choose a date range, then open the case from its row.

    Step 2. The Case closed panel shows the decision, the reason, who recorded it, and when.

    Step 3. The comparison shows what matched: the list, the entry, and the list version used for that screening.

    Step 4. Open Evidence and Timeline. Every decision on the case is here, in order, with the reviewer's name, role and note.

    Step 5. Open Audit Logs under Reports, and filter Action to the decisions. Each decision has its own row in the System Audit Ledger, with an actor ID and the reviewer's role. Audit records cannot be edited or deleted.

    How to find a past decision and who made it

    1:06

    A how-to for compliance staff: open Reports Overview, then Adjudication SLA, choose a date range and open the case from its row. The Case closed panel shows the decision, the reason, who recorded it and when, and the comparison shows the list, the entry and the list version used for that screening. Evidence and Timeline lists every decision on the case with the reviewer's name, role and note, and each decision has its own row in the System Audit Ledger under Audit Logs. Audit records can't be edited or deleted.

    Good to know: By default, only org admins and compliance managers can open the case. Auditor accounts can open the Adjudication SLA report and Audit Logs.

  • Read the transcript

    A visitor's row says On hold, security review. Not checked in. Do not issue a badge.

    Step 1. Ask the visitor to take a seat. You can say, "Your sign-in is still being completed."

    Step 2. Open the visitor. The card tells you the next step: ask the visitor to wait. Compliance has been notified and will decide.

    Step 3. Select Notify Host so the host knows the visitor has arrived.

    The badge button stays off until the visitor is approved. Compliance decides the case, and the row changes when they do.

    Front desk: when a visitor is on hold

    0:52

    A how-to for front desk staff: a held visitor's row says On hold, security review. Not checked in. Do not issue a badge. Ask the visitor to take a seat, open the visitor to see the next step, and select Notify Host so the host knows the visitor has arrived. The badge button stays off until the visitor is approved, and the row changes when compliance decides.

    Good to know: By default, only org admins and compliance managers can decide a held visit in the Adjudication Queue.

  • Read the transcript

    Step 1. In Admin, under Compliance, open NDA & Safety, and select Set up the default NDA. The default is used at every site, unless you add an exception.

    Step 2. It starts with a sample NDA for your counsel to review. Give it a title that says NDA, and paste in your agreement text. What the kiosk shows previews it.

    Step 3. Tick Show visitors the safety video. Paste a YouTube link, or upload an MP4 or WebM file.

    Step 4. Select Save. The overview shows both steps on, and Recent changes lists who saved it.

    Step 5. Under Check what a visitor gets, pick a site to see what a visitor signs and is shown.

    At the kiosk, visitors sign the NDA, then acknowledge the safety briefing. A QR code check-in skips whichever they finished while registering, unless the site requires them at every visit.

    Both are saved with the visit and shown on its Compliance tab.

    Screen visitors at check-in. Keep the decisions on record.

    How to set up NDA and safety documents

    1:23

    A how-to for org admins and compliance managers: in Admin, under Compliance, open NDA & Safety and select Set up the default NDA, which is used at every site unless you add an exception. It starts with a sample NDA for your counsel to review: give it a title that says NDA and paste in your agreement text, and What the kiosk shows previews it. Tick Show visitors the safety video, then paste a YouTube link or upload an MP4 or WebM file, and select Save. Check what a visitor gets shows what a visitor at a site signs and is shown. At the kiosk, visitors sign the NDA and then acknowledge the safety briefing, a QR code check-in skips whichever they finished while registering unless the site requires them at every visit, and both are saved with the visit.

    Good to know: The NDA and safety steps need a plan that includes them. If NDA & Safety says the NDA and safety workflow is off for your organization, contact SecurePoint.

  • Read the transcript

    Step 1. Open Reports Overview, then Visitor Audit. Each row is one visit.

    Step 2. Search by name, email or company, or filter by host.

    Step 3. Select the row to see its purpose, check-in and check-out times, host, and screening decision.

    Auditor accounts can do all of this. By default, only org admins and compliance managers can export.

    Step 4. To export the whole list, empty the search box and select Export CSV. Then select Download.

    The file has a row for each visit, with check-in and check-out times in UTC.

    Screen visitors at check-in. Keep the decisions on record.

    How to find a past visit and export the visitor list

    0:59

    A how-to for compliance, security and audit staff: in Reports Overview, open Visitor Audit, where each row is one visit. Search by name, email or company, or filter by host, and open a row for its purpose, check-in and check-out times, host and screening decision. To export, clear the search and any filters and pick the date range you need, then select Export CSV and Download: the file has a row for each visit, with times in UTC. Auditor accounts can search and open visits; by default, only org admins and compliance managers can export.

    Good to know: Export CSV lists the same visits the page shows: the date range, which starts at the last 30 days, and any search or filter all apply.

  • Read the transcript

    Step 1. Open the visitor's record. Missing for this visit lists what's left.

    Step 2. Select NDA. Have the visitor sign it here, or send it to their phone and keep this window open.

    Step 3. Select Safety Briefing. Have them watch it here, or send it to their device the same way.

    Step 4. Select Headshot, capture the visitor's face, and save it for the badge.

    Step 5. If you have ID Vault, select ID Front, then capture and save their ID.

    Once nothing is missing for a cleared visitor, select Badge to open the preview.

    Screen visitors at check-in. Keep the decisions on record.

    How to finish missing check-in steps at the desk

    1:00

    A how-to for front desk staff: open the visitor's record, where Missing for this visit lists what's left. Have the visitor sign the NDA and watch the safety briefing, at the desk or on their own phone. Capture a headshot for the badge and, if you have ID Vault, the front of their ID. When nothing is missing for a cleared visitor, select Badge to open the preview.

  • Read the transcript

    Step 1. In Admin, open Hosts. Hosts can pre-register visitors in Host Hub.

    Step 2. Click Add Host. Enter their full name and email, and pick their site.

    Keep Send invite email automatically ticked, and click Create Host. They're emailed a link to Host Hub.

    Step 3. To add many hosts at once, click Bulk Upload and choose a CSV file. Each row needs a full name and email.

    Tick Send invite emails to newly created hosts, then click Import Hosts.

    Step 4. Check the summary for any row it skipped or couldn't email. New hosts then appear in your list.

    Screen visitors at check-in. Keep the decisions on record.

    How to add hosts and send Host Hub invites

    1:00

    A how-to for org admins and compliance managers: in Admin, open Hosts, select Add Host, enter a full name and email, pick their site, keep Send invite email automatically ticked and select Create Host, and the host is emailed a link to Host Hub. To add many hosts at once, select Bulk Upload with a CSV file that has a full name and email on each row, tick Send invite emails to newly created hosts, select Import Hosts, and check the summary for any row it skipped or couldn't email.

    Good to know: If any row in the CSV file has a problem, such as a missing name or email or a site that doesn't exist, nothing is imported. Fix the rows it lists, then choose the file again.

  • Read the transcript

    Step 1. When a run flags a possible match, open the Continuous Monitoring add-on under Compliance, then select Hits.

    Step 2. Open the hit. Compare the name screened with the listed party.

    Step 3. Choose a reason code, and add a note if asked.

    Step 4. Select False Positive if it's someone else. Needs More Info and Escalate keep it open.

    Block asks you to confirm and denies the linked case. No decision here changes anyone's access.

    The hit shows your decision, and the audit trail records it with your reason code.

    SecurePoint. Re-screen the people you work with, and keep the decisions on record.

    How to review a Continuous Monitoring hit

    0:59

    A how-to for compliance managers: when a run flags a possible match, open the Continuous Monitoring add-on under Compliance, then Hits. Open the hit, compare the name screened with the listed party, choose a reason code and add a note if asked. Select False Positive if it's someone else; Needs More Info and Escalate keep it open. Block, once you confirm it, marks the linked review case as denied. No decision here changes anyone's badge or system access, and the audit trail records your decision with your reason code.

    Good to know: Continuous Monitoring is an add-on that SecurePoint turns on for your organization. By default, org admins and compliance managers use it.

  • Read the transcript

    On the Front Desk Dashboard, Check Out and Revoke look alike, but do different jobs.

    Step 1. When a visit ends normally, select Check Out.

    Pick a reason, then select Confirm Checkout. The time and who did it are recorded.

    Step 2. To remove someone, select Revoke. It's not an early check-out.

    Revoke requires a reason. Keep it short, with no names, then select Revoke Access.

    The visit ends, and the visitor is recorded as denied, with your reason.

    Recent Activity tells them apart: Out for a check-out, Revoked for a revoke.

    Screen visitors at check-in. Keep the decisions on record.

    How to choose between Check Out and Revoke

    0:57

    A how-to for front desk staff: on the Front Desk Dashboard, Check Out and Revoke look alike but do different jobs. When a visit ends normally, select Check Out, pick a reason and confirm, and the time and who did it are recorded. To remove someone, select Revoke, which is not an early check-out: give a short reason with no names and select Revoke Access, and the visit ends with the visitor recorded as denied. Recent Activity shows Out for a check-out and Revoked for a revoke.

    Good to know: Front desk staff can't check out or revoke a visit that is still under compliance review. A reviewer decides it in the Adjudication Queue.

  • Read the transcript

    Step 1. In Admin, open Badges, and Duplicate the template closest to what you need.

    Step 2. In Quick Edit, name it, choose what the badge shows, and set text sizes.

    For exact positions and sizes, switch to Advanced Design.

    Step 3. Try a long sample name, and check that Preflight says Ready. Then select Save.

    Step 4, for org admins. In Badge Assignments, choose it for a visitor type.

    Nothing is live until you select Review Changes, then Apply Assignments.

    Step 5. What Will Actually Print shows which template each site prints.

    At the front desk, the contractor's badge preview shows the same template.

    Screen visitors at check-in. Keep the decisions on record.

    How to set up and assign a badge template

    1:04

    A how-to for org admins and compliance managers: in Admin, open Badges and duplicate the template closest to what you need. In Quick Edit, name it, choose what the badge shows and set text sizes, or switch to Advanced Design for exact positions and sizes. Try a long sample name, check that Preflight says Ready, and save. Org admins then choose it for a visitor type in Badge Assignments; nothing is live until Review Changes, then Apply Assignments. What Will Actually Print shows which template each site prints, and the front desk's badge preview for that visitor type shows the same template.

  • Read the transcript

    Step 1. When an arrival still needs checking, like a visitor waiting for an escort, the Front Desk Dashboard shows Entry Validation Required.

    Step 2. Check the visitor against their ID and the details on screen. If everything matches, select Admit Visitor.

    Step 3. If something's wrong, choose a reason under Hold for compliance review, like ID does not match the visitor.

    Step 4. Add a note for compliance. It's required when the reason is Other. Then select Hold for compliance review.

    The visitor isn't admitted. The visit goes to the Adjudication Queue, where compliance decides. Only compliance can deny entry.

    Screen visitors at check-in. Keep the decisions on record.

    How to hold a visitor at the desk

    1:03

    A how-to for front desk staff: when an arrival still needs checking, like a visitor waiting for an escort, the Front Desk Dashboard shows Entry Validation Required. Check the visitor against their ID and the details on screen, and select Admit Visitor if everything matches. If something's wrong, choose a reason under Hold for compliance review, add a note for compliance, which is required when the reason is Other, and select Hold for compliance review. The visitor isn't admitted, and the visit goes to the Adjudication Queue, where compliance decides. Only compliance can deny entry.

    Good to know: By default, only org admins and compliance managers can decide a held visit in the Adjudication Queue.

  • Read the transcript

    Step 1. Open Reports, then Evidence Packs.

    Step 2. Choose the CMMC L2 PE Visitor Evidence template, then the dates and sites to cover.

    Step 3. Leave PII redacted for an outside assessor, then generate the pack.

    Step 4. Open the ZIP's physical access register. Each row is one visit: check-in and check-out times, host, site, and whether an escort was required and recorded.

    Escort gap flags a visit that needed an escort with none recorded. Departure verified shows whether anyone saw the visitor leave.

    The manifest lists an SHA-256 checksum for each file, and Evidence Pack History keeps the sealed ZIP.

    Screen visitors at check-in. Keep the decisions on record.

    How to export the physical access register

    1:10

    A how-to for compliance teams: open Reports, then Evidence Packs, and choose the CMMC L2 PE Visitor Evidence template and the dates and sites to cover. Leave PII redacted for an outside assessor, then generate the pack. In the ZIP, the physical access register has one row per visit: check-in and check-out times, host, site, and whether an escort was required and recorded. Escort gap flags a visit that needed an escort with none recorded, and departure verified shows whether anyone saw the visitor leave. The manifest lists an SHA-256 checksum for each file, and Evidence Pack History keeps the sealed ZIP.

    Good to know: By default, only org admins and compliance managers can build or download evidence packs.

  • Read the transcript

    Step 1. Open your account menu at the top right, and select Security & MFA.

    Step 2. Select Enable 2FA. Then, in an authenticator app like Microsoft Authenticator or Duo Mobile, add an account and scan the QR code.

    Can't scan it? Type the key shown below the code into your app instead.

    Step 3. Enter the six-digit code from the app, and select Verify & Enable.

    Two-factor authentication now shows Enabled. If your organization requires it, you'll enter a code from the app each time you sign in with your password.

    Screen visitors at check-in. Keep the decisions on record.

    How to set up two-factor sign-in

    0:58

    A how-to for staff who sign in with a password: open your account menu at the top right, select Security & MFA, then Enable 2FA. In an authenticator app like Microsoft Authenticator or Duo Mobile, add an account and scan the QR code, or type the key shown below it. Enter the six-digit code from the app and select Verify & Enable, and two-factor authentication shows Enabled. If your organization requires it, you enter a code from the app each time you sign in with your password.

    Good to know: People who sign in with Microsoft use the MFA their Microsoft tenant enforces, so SecurePoint doesn't ask them for a code.

  • Read the transcript

    Step 1. In Admin, open Users, and select Add User.

    Step 2. Enter their email address, and pick their role, like Front Desk.

    Step 3. For front desk staff, pick the site they work at. Then select Create User.

    They're emailed an invitation, with a link to the video guide for their role. Until they accept, they're listed under Pending Invitations, where you can resend or delete it.

    Screen visitors at check-in. Keep the decisions on record.

    How to invite staff users

    0:44

    A how-to for org admins and site managers: in Admin, open Users and select Add User. Enter the person's email address and pick their role, like Front Desk; for front desk staff, pick the site they work at. Select Create User, and they're emailed an invitation with a link to the video guide for their role. Until they accept, they're listed under Pending Invitations, where you can resend or delete the invitation.

    Good to know: Org admins and site managers can invite staff, but never with a role above their own.

  • Read the transcript

    Step 1. In Admin, open Security Settings.

    Step 2. Under MFA Sign-In Enforcement, tick Require MFA at sign-in.

    Step 3. Select Save Changes in the bar at the bottom of the page.

    From then on, staff enter a code from their authenticator app each time they sign in, before they reach the dashboard. Anyone who hasn't set one up is sent to do that first.

    That includes you: if you haven't entered your code since you signed in, you're asked for it as soon as you save.

    Kiosks and Host Hub aren't affected, and accounts set up through Microsoft sign-in keep using your Microsoft tenant's MFA.

    Screen visitors at check-in. Keep the decisions on record.

    How to require two-factor sign-in for your organization

    1:02

    A how-to for org admins: in Admin, open Security Settings. Under MFA Sign-In Enforcement, tick Require MFA at sign-in, then select Save Changes in the bar at the bottom of the page. From then on, staff enter a code from their authenticator app each time they sign in, before they reach the dashboard, and anyone who hasn't set one up is sent to do that first. That includes you: if you haven't entered your code since you signed in, you're asked for it as soon as you save. Kiosks and Host Hub aren't affected, and accounts set up through Microsoft sign-in keep using your Microsoft tenant's MFA.

    Good to know: By default, only org admins can change Security Settings. How to set up two-factor sign-in shows your staff how to add the app.

  • Read the transcript

    Step 1. In Admin, open Sites.

    Step 2. Select the pencil on the site's card.

    Step 3. Under Security Compliance Profile, change Normal to ITAR Controlled.

    Step 4. Select Save Changes. The site's card now shows the ITAR badge.

    From the next check-in at that site, every visitor needs a host, and kiosk visitors scan their ID during check-in, even if they registered one beforehand.

    By default, only org admins can change a site's profile, and ITAR Controlled is available once SecurePoint turns ITAR on for your organization.

    Screen visitors at check-in. Keep the decisions on record.

    How to set a site's security profile

    1:00

    A how-to for org admins: in Admin, open Sites and select the pencil on the site's card. Under Security Compliance Profile, change Normal to ITAR Controlled, then select Save Changes, and the site's card shows the ITAR badge. From the next check-in at that site, every visitor needs a host, and kiosk visitors scan their ID during check-in, even if they registered one beforehand. By default, only org admins can change a site's profile, and ITAR Controlled is available once SecurePoint turns ITAR on for your organization.

    Good to know: By default, only org admins can change a site's profile; site managers can open Sites but can't save a profile change. Your organization's compliance mode can make every site stricter than its own profile.

  • Read the transcript

    Step 1. Under Compliance, open the Continuous Monitoring add-on, then select Imports.

    Step 2. Download the example CSV for the columns. A name is required, and an ID keeps re-imports matched to the same person.

    Step 3. Choose your file, and pick what the records are: employees, contractors or vendors.

    Step 4. Keep the default import mode, which adds and updates people and leaves everyone else alone. Then select Preview import.

    When the preview shows no warnings or errors, select Commit import.

    Step 5. Your people now appear in Monitored Parties. They're re-screened on your organization's schedule, or right away with Rescreen now.

    Make sure a policy is enabled on the Policies tab, or no runs are recorded.

    Screen visitors at check-in. Keep the decisions on record.

    How to import a roster into Continuous Monitoring

    1:15

    A how-to for compliance teams: under Compliance, open the Continuous Monitoring add-on and select Imports. Download the example CSV for the columns: a name is required, and an ID keeps re-imports matched to the same person. Choose your file and pick what the records are: employees, contractors or vendors. Keep the default import mode, which adds and updates people and leaves everyone else alone, and select Preview import. When the preview shows no warnings or errors, select Commit import. Your people then appear in Monitored Parties, re-screened on your organization's schedule, or right away with Rescreen now. Make sure a policy is enabled on the Policies tab, or no runs are recorded.

    Good to know: Continuous Monitoring is an add-on that SecurePoint turns on for your organization. By default, org admins and compliance managers use it.

  • Read the transcript

    Step 1. On the Front Desk Dashboard, select New Check-in.

    Step 2. Hold the visitor's ID up to the camera, and select Capture Front. Their name fills in from the ID.

    Step 3. Add their company and mobile number, check their country, and continue.

    Step 4. Choose the host they're here to see and the purpose of the visit, then continue.

    Step 5. Take their headshot for the badge, and accept it.

    Step 6. If an agreement appears, choose where the visitor signs: on their phone, or here at the desk.

    SecurePoint screens them. At Check-in Complete, select Print Badge. If it doesn't come out, select Reprint Badge.

    If it says Under review instead, compliance decides before a badge prints.

    Screen visitors at check-in. Keep the decisions on record.

    How to check in a walk-in at the desk

    1:12

    A how-to for front desk staff: on the Front Desk Dashboard, select New Check-in. Hold the visitor's ID up to the camera and select Capture Front, and their name fills in from the ID. Add their company and mobile number, check their country, then choose the host and the purpose of the visit. Take their headshot for the badge. If an agreement appears, choose whether the visitor signs on their phone or at the desk. SecurePoint screens them: at Check-in Complete, select Print Badge, or Reprint Badge if it doesn't come out. If it says Under review, compliance decides before a badge prints.

  • Read the transcript

    Step 1. At sites that use autonomous check-in, a visitor who checks in at the kiosk waits there for their host.

    Step 2. On the Front Desk Dashboard, their row says Waiting for host verification.

    Step 3. When the visitor is at your desk, select Complete host verify.

    Step 4. Type the host's name, check the visitor's photo ID, and tick both boxes.

    Step 5. Select Complete host verification. If nothing else is holding the visit, they're checked in.

    Then open their record and print the badge.

    Screen visitors at check-in. Keep the decisions on record.

    How to complete Host Verify at the desk

    0:55

    A how-to for front desk staff at sites that use autonomous check-in: a visitor who checks in at the kiosk waits there for their host, and their row on the Front Desk Dashboard says Waiting for host verification. When the visitor is at your desk, select Complete host verify. Type the host's name, check the visitor's photo ID, tick both boxes, and select Complete host verification. If nothing else is holding the visit, they're checked in, and you print their badge from their record.

    Good to know: Visitors wait for host verification at sites set to autonomous check-in, which is off by default. For a foreign national, three more confirmations appear after you first submit.

  • Read the transcript

    If a host hasn't come to meet their visitor, you can send them an arrival email with a note from the desk.

    Step 1. On the Front Desk Dashboard, open the visitor's record.

    Step 2. Next to the host's name, select Notify Host. The host's name and email are filled in from the visit.

    Step 3. Add a message for the host, like where the visitor is waiting. Then select Send Notification.

    Your host gets an arrival email with the visitor's name, the site and the time, and your message under Front desk note.

    Screen visitors at check-in. Keep the decisions on record.

    How to notify a visitor's host from the desk

    0:52

    A how-to for front desk staff: if a host hasn't come to meet their visitor, send them an arrival email with a note. On the Front Desk Dashboard, open the visitor's record. Next to the host's name, select Notify Host; the host's name and email are filled in from the visit. Add a message, like where the visitor is waiting, and select Send Notification. The host gets an arrival email with the visitor's name, the site and the time, and your message under Front desk note.

  • Read the transcript

    Step 1. On the iPad or Android tablet, install SecurePoint Kiosk from the App Store or Google Play, and open it. An Android tablet asks for the camera and to pin the app: tap While using the app, then Got it.

    The app opens on a short setup guide. Tap Get started, then Next. Tick the box to agree to the terms, and tap Agree and continue.

    Step 2. On a computer, in Admin, open Kiosks. Name the tablet, pick its site, and select Generate pairing code.

    Step 3. On the tablet, type the code and tap Pair tablet, or tap Scan QR and scan the code on the computer. The kiosk welcome screen opens.

    Step 4. On an iPad, keep visitors in the kiosk with Guided Access: turn it on in Settings, under Accessibility, then triple-click the top button in the app. An Android tablet stays pinned on its own.

    Step 5. Staff settings sit behind a PIN. Tap the top-right corner five times quickly, and enter 1234 the first time. Then change it in Kiosk Settings.

    Screen visitors at check-in. Keep the decisions on record.

    How to set up the SecurePoint Kiosk app

    1:16

    A how-to for admins and site managers: install SecurePoint Kiosk on an iPad or Android tablet from the App Store or Google Play and open it. An Android tablet asks for the camera and to pin the app. The app's short setup guide ends with agreeing to the terms. Then, in Admin, open Kiosks, name the tablet, pick its site and generate a pairing code, and type the code on the tablet or scan its QR code to open the kiosk welcome screen. On an iPad, Guided Access keeps visitors in the kiosk. Staff settings sit behind a PIN, opened from the top-right corner, and the first PIN is 1234.

    Good to know: SecurePoint Kiosk is on the App Store and Google Play in the United States. To use a web browser on the tablet instead, see How to set up a lobby kiosk.

  • Read the transcript

    Kiosk Settings live on the tablet. Tap the top-right corner of the screen five times quickly, then enter the settings PIN.

    Step 1. Change the PIN from 1234 the first time, under Settings PIN.

    Step 2. Badge printer shows the printer the tablet uses. Print a test label to check it any time.

    Step 3. If check-in looks stuck, tap Reload check-in page. Diagnostics has details you can copy for SecurePoint support.

    On an Android tablet, Leave the kiosk app lets staff use the tablet for something else. Open SecurePoint Kiosk again to go back.

    Screen visitors at check-in. Keep the decisions on record.

    How to use Kiosk Settings on the tablet

    0:47

    A how-to for admins, site managers and the front desk: on a tablet running the SecurePoint Kiosk app, tap the top-right corner five times and enter the settings PIN. Change the PIN from 1234 under Settings PIN, check the badge printer and print a test label, tap Reload check-in page if check-in looks stuck, and copy Diagnostics for SecurePoint support. On an Android tablet, Leave the kiosk app lets staff use the tablet for something else.

    Good to know: Kiosk Settings are in the SecurePoint Kiosk app on an iPad or Android tablet. A kiosk in a web browser doesn't have them.

  • Read the transcript

    In autonomous check-in, visitors check themselves in at the kiosk, and Host Verify finishes the visit there.

    Turn it on for the whole organization in Admin, Kiosks, or for one site in Admin, Sites.

    Once a visitor is cleared, the kiosk asks them to wait for their host.

    The host on the visit gets an arrival email, and a text on plans with SMS, to come to the kiosk. With the host code on, it includes a four-digit code.

    At the kiosk, the host taps Host Verify. A visitor still in compliance review can't be picked.

    They pick their visitor, type their own name and any code, check the photo ID, tick both boxes, and print the badge.

    The visit keeps the typed name and whether the host used the code. At an ITAR or high-security site, if Host Verify is done without the code, a U.S. person gets an escort-only badge.

    SecurePoint Visitor. Screen visitors at check-in, and keep the decisions on record.

    Kiosk autonomous mode

    1:16

    In autonomous check-in, visitors check themselves in at the lobby kiosk, and Host Verify finishes the visit there. Admins turn it on for the whole organization in Admin, Kiosks, or for one site in Admin, Sites. Once a visitor is cleared, the kiosk asks them to wait for their host, who gets an arrival email, and a text on plans with SMS, to come to the kiosk, with a four-digit code when the host code is on. At the kiosk, the host taps Host Verify, picks their visitor, types their own name and any code, checks the photo ID, ticks both boxes and prints the badge. A visitor still in compliance review can't be picked, and the visit keeps the typed name and whether the host used the code.