Portal documentation
MANPRA Portal synchronizes workforce identity, access policy, attendance events, and command-center visibility through a single governed lane.
Portal devices pair with ManpraOS (MPOS-1) and MPCLOUD plan lanes to keep identity-to-command workflows consistent.
MANPRA Portal connects Access, Workforce, and Surveillance in one simple identity flow. Portal devices capture identity and credentials, then share updates across access rules, attendance, and command visibility.
Teams can manage access rules and attendance from one command view. Portal events appear in Access, Workforce, and Surveillance together.
Three variants: Portal S (entry), Portal P (pro), and Portal E (enterprise). Each maps to ManpraOS and the right cloud plan.
| Model code | Variant | Tier | Deployment fit | Packaging |
|---|---|---|---|---|
| MPPORTAL-S-G1 | MANPRA Portal S | entry | Entry lane for identity capture and attendance-to-access synchronization | Hardware unit + Portal Basic monthly lane |
| MPPORTAL-P-G1 | MANPRA Portal P | pro | Pro lane for policy-rich access governance and cross-site attendance continuity | Hardware unit + Portal Pro monthly lane |
| MPPORTAL-E-G1 | MANPRA Portal E | enterprise | Enterprise lane for deeper policy governance, auditability, and command-center synchronization | Hardware unit + Portal Enterprise monthly lane |
| Step | Operational action | Command effect |
|---|---|---|
| 1. Employee profile created | HR or operations creates or updates the employee identity profile in Workforce lane. | Identity record appears in readiness queue. |
| 2. Access policy assigned | Role and site policy is mapped to the employee profile through Access controls. | Policy state becomes visible for review and exception handling. |
| 3. Portal credential activated | Face/mobile credential posture is activated according to approved deployment profile. | Credential activation state appears in identity timeline. |
| 4. Entry event processed | Portal validates credential and applies assigned policy (grant, deny, or warning). | Access event enters command-center incident/activity stream. |
| 5. Attendance auto-recorded | Valid entry event triggers attendance state sync in Workforce module. | Attendance and access are linked in one audit trail. |
| 6. Command visibility and audit | Operations teams review synchronized identity, access, and attendance state from one timeline. | Unified visibility supports escalation, reporting, and policy refinement. |
| Area | Readiness | Posture | Note |
|---|---|---|---|
| HRMS sync posture | architecture-ready | Employee identity ingestion and status sync are designed through API-ready connector lanes. | Connector availability depends on approved integration scope and rollout phase. |
| Access policy synchronization | active rollout | Policy profiles can be mapped to roles, sites, and schedule lanes with governed updates. | Advanced policy packs remain staged by deployment profile. |
| Mobile credential posture | architecture-ready | Mobile credential direction supports identity continuity across entry and attendance workflows. | Production configuration follows approved security policy and tenant rollout plan. |
| Event and audit API lane | active rollout | Timeline export and event API posture supports command-center reporting and enterprise governance. | Extended enterprise API packs are available through staged commercial programs. |
| Surveillance event linking | architecture-ready | Access events can be correlated with surveillance timelines in one operational context. | Correlation depth depends on deployed camera/recorder profile and policy configuration. |
