Pending Employer Approval
The employee-side pending state shown when a recognized company email still needs manager or admin approval before organization access is activated.
The employee-side waiting state should stay explicit, calm, and actionable.
The employee should see when the organization queue updates without refreshing a dead-end page.
A good pending state explains exactly what the employee can still do while waiting.
It should also give the employee a clear way to request access again, check status, and understand what will happen once the organization approves the request.
That keeps employee and manager state aligned instead of creating a silent approval gap.
{
"access_state": "pending_approval",
"organization_name": "Northstar Logistics",
"requested_role": "operations_manager",
"request_action": "request_access_again",
"realtime_updates": true
}The pending state should be calm, informative, and connected to the queue in real time.
The employee should know which organization recognized the company email.
The pending state should stay tied to the requested scope rather than feeling generic.
The page should reflect queue changes without forcing the employee into a dead refresh loop.
The waiting state should give the employee one clear follow-up action.
The internal owner should remain visible to admins and support operators.
Once approval clears, the employee should move directly into the organization onboarding flow.
The employee request is already attached to the live company-email approval queue.
The waiting state listens for approval changes instead of leaving the employee in a stale view.
Clear employee-side state should reduce unnecessary support loops while approval is still pending.
The account was matched to Northstar Logistics automatically.
The employee requested manager-level access through the pending-approval flow.
The request is visible in the active approval queue and ready for a decision.
The pending-approval surface should explain that the employee account exists, the company domain was recognized, and the organization still needs to approve access before the managed workspace opens.
It should also give the employee a clear way to request access again, check status, and understand what will happen once the organization approves the request.
Pending employer approval should also create a clean signal inside the organization queue so managers see the request, the requested role, and the originating company-email route immediately.
That keeps employee and manager state aligned instead of creating a silent approval gap.