Implementation guide
Authentication and SSO
Plan supported sign-in and MFA with your IT owner. Assign staff roles within SecurePoint before rollout.
SSO Setup
- Confirm the supported identity-provider setup and exact callback URL with SecurePoint before making IdP changes.
- Use the organization invitation and supported sign-in flow; do not assume custom IdP claims grant access.
- Assign each user a SecurePoint role within SecurePoint before rollout; IdP groups are not mapped to roles.
- Test both initial sign-in and forced re-authentication scenarios.
Application callback path
/auth/callbackRole-Based Access
| Role | Typical Scope |
|---|---|
| org_admin | Organization configuration, users, and policy controls. |
| site_manager | Site configuration, host coordination, and local operations. |
| compliance_manager | Case review, adjudication, and evidence workflows. |
| front_desk | Lobby operations, check-in support, and visitor workflow assistance. |
| auditor_readonly | Read-only audit and evidence review. |
Keep role grants minimal and add elevated roles only where workflow ownership requires it. Organization context and permissions are verified by SecurePoint; this example does not describe claims you can submit to grant access.
Session Security
Validate session timeouts and re-authentication behavior for sensitive actions. Compliance and organization-admin workflows should be tested with MFA enabled where policy requires it.
Illustrative Session Claims
{
"sub": "user-uuid",
"email": "jane@example.com",
"organization_id": "org-uuid",
"role": "org_admin"
}Never store service-role credentials in browser code. Keep privileged secrets on server-side routes only.
Need implementation support?
Our team can provide a guided SSO rollout and RBAC workshop tailored to your environment.
Contact the team