Implementation guide
Getting Started
This guide is for new SecurePoint Visitor customers. Use it to plan your first-site pilot and the checks needed before expanding to more locations.
Production Launch Checklist
- Confirm project kickoff roles: executive sponsor, implementation lead, security/compliance owner, and site operations contact.
- Create your production organization and verify admin access for each required team.
- Configure at least one pilot site and validate local time, host routing, and policy scope.
- Enable required check-in controls (photo, ID, NDA/safety prompts) based on your compliance program.
- Validate supported sign-in and MFA, and assign staff roles within SecurePoint before rollout.
- Run pilot check-ins and confirm screening, adjudication, and audit records are generated as expected.
- Complete go-live readiness review with SecurePoint and document post-launch support contacts.
Sites and Locations
Site configuration controls local time behavior, host routing, and policy targeting. Create one site record per physical facility before enabling production check-ins.
Recommended validation
Test each staff role against its intended workflows and confirm that customer data stays within its organization.
Plan a multi-site rollout
Start with a representative pilot site. Use its results to agree on rollout waves, staffing, and acceptance checks with SecurePoint before opening additional locations.
- Record each site. List its time zone, entrances, site owner, host contacts, visitor volume, and required check-in steps. Confirm plan coverage for the intended locations.
- Check local equipment and connectivity. Record the kiosk device, supported print path, printer, labels, network access, and spare check-in station. Test the actual equipment at each location.
- Agree on staff responsibilities. Name the front-desk, IT, security, and compliance contacts. Assign roles and test sign-in, MFA, host routing, and any optional notification channels.
- Run the visit from start to finish. Test a preregistered visitor, a walk-in, a held match and reviewer decision, required documents and ID capture, a badge, checkout, and an evidence export. Confirm a missing required step prevents badge issuance.
- Rehearse interruptions. Check what staff see when the network, scanning service, or printer is unavailable. Agree on a local escalation procedure that preserves required screening and approval checks.
- Approve each rollout wave. Record results, unresolved issues, a site owner, support contacts, and a decision to proceed or delay. Review the next wave after the previous sites have completed their acceptance checks.
Agree on capacity targets and test conditions for your expected peak traffic during implementation. A completed checklist records your review; it does not replace performance testing or site acceptance.
Review supported hardware and printing pathsKiosk Check-In Flow
Configure field requirements and legal acceptance rules before deployment. Start with a pilot check-in path and verify document capture, photo capture, and screening behavior in a controlled environment.
Operational tip
Keep one fallback check-in station ready while you validate printing, scanner devices, and network-dependent services.
Client Go-Live Validation
Before your release date, complete this validation sequence with your internal team and SecurePoint implementation support:
- Run a launch-day walkthrough using real host users and sample visitor traffic.
- Verify screening decisions, escalation routing, and notification behavior for flagged cases.
- Confirm report exports and evidence package generation for your audit process.
- Capture final sign-off from operations, compliance, and IT before opening production check-in.
Store your sign-off notes and first-week support plan so operations and compliance stakeholders have one shared launch record.
Next: Configure Authentication
Continue with SSO setup and role-based access before enabling broad user onboarding.
Open Authentication Guide