Implementation guide
Administrator Hub
Plan your Visitor site, review staff access, and understand record handling. Use these checks with your implementation lead before rollout.
Sites and Locations
Create a site for each facility you intend to operate. Confirm its name, timezone, and security profile before assigning visitors or configuring a kiosk.
Do this first
- Create your headquarters or primary facility.
- Confirm the site timezone and review the security profile with your security lead.
- Assign a dedicated manager or point-of-contact for every site.
Common mistakes to avoid
- Grouping distinct buildings into a single site, which obscures audit trails and access reporting.
- Failing to align timezone and regional formatting settings with the physical location.
How to know it’s working
- Check that a test visit is associated with the intended site.
- Verify the site and organization shown in the visit record before rollout.
Kiosk Flows
Review the host, visit purpose, agreements, and capture steps required by your site. Test both a completed check-in and an incomplete or held visit on the kiosk you will use.
Do this first
- Review the required check-in steps for your site and visit purposes.
- Review the visitor agreements and safety acknowledgements required by your site or visit purpose.
- Confirm which host notifications your organization has configured and test their delivery.
- Choose a supported badge-print path and test it on your actual kiosk, printer, and label stock.
Common mistakes to avoid
- Overloading the check-in process with unnecessary questions that cause lobby bottlenecks.
- Deploying to the front lobby before running a complete test on the physical kiosk hardware.
How to know it’s working
- A test visitor completes the required steps, or sees the expected waiting state when staff action is needed.
- The configured host notification reaches its intended recipient. Available channels depend on your plan and configuration.
- Required agreement and capture steps are reflected in the visit record; a held or incomplete visit remains unable to badge.
Roles and Permissions
Assign the smallest SecurePoint role that supports each staff member’s work. Hosts and staff have different workflows; test access with the actual roles and sites you intend to use.
Do this first
- Audit the default system roles and understand their access boundaries.
- Assign organization administrators only to staff responsible for organization configuration.
- Assign site managers as needed and verify the access each account has before rollout.
Common mistakes to avoid
- Giving organization-admin access to staff who only need front-desk tasks.
- Assuming that a role name alone proves access is limited to a particular site.
How to know it’s working
- Verify a front-desk account can perform its assigned tasks and is refused privileged actions.
- Check which sites and records each account can reach; resolve unexpected access before launch.
Log Retention and Audit Downloads
Core record retention, report date ranges, and image retention are separate. SecurePoint’s core record-retention baseline is ten years. Confirm your organization’s agreed policy with SecurePoint before rollout.
Do this first
- Confirm the record retention policy that applies to your organization’s screening, review, and audit records.
- Review photo and ID-image retention separately, including any applicable legal hold.
- Run a test export of visitor logs to verify report formatting and data completeness.
Common mistakes to avoid
- Treating a report date filter as a setting that deletes or anonymizes retained records.
- Assuming captured images and core audit records have the same retention period.
How to know it’s working
- Changing a report or export date range changes which records you retrieve; it does not delete or anonymize those records.
- Review the selected export for the visit, screening, and decision details you need. Available fields depend on the export type and completed workflow.
Before Your First Site Goes Live
Complete a pilot with your operations, security, and IT owners. Confirm the required steps and refusal states before opening production check-in.
Do this first
- Schedule a brief training session with your front desk and physical security personnel.
- Provision and pair the application with your lobby hardware devices.
- Conduct a final end-to-end walkthrough by checking in as a test visitor.
Common mistakes to avoid
- Skipping the staff training phase, leading to operational confusion and bypasses on launch day.
- Hard-launching physical kiosks without verifying their network connectivity and power stability.
How to know it’s working
- Staff know how to complete outstanding steps or request an authorized review while required controls remain in place.
- The system correctly records your test visitor data and triggers the appropriate compliance checks and host alerts.