Blocked Company Email State
The respectful blocked state shown when a company email is explicitly denied by organization policy, role policy, or a domain-level rule.
Blocked state should stay respectful externally while preserving full internal auditability.
The internal cause belongs in the workspace, not in the employee-facing explanation.
If the organization changes policy later, the restore path should stay one click away for the owner.
The state should still point the employee toward a safe next step such as contacting the employer or opening a permitted support path if the block seems incorrect.
That keeps blocked state auditable without making the public-facing employee experience harsh or chaotic.
{
"access_state": "blocked",
"organization_name": "Northstar Logistics",
"employee_view_reason": "Access has not been granted by your organization.",
"admin_policy_reference": "blocked_alias_policy_night_shift"
}Blocked state should remain respectful externally and auditable internally.
The employee-facing message should stay clear without exposing private policy detail.
Admins still need the auditable internal reason bound to the case.
A blocked company-email case should still leave a clean future restore path if policy changes.
A blocked company-email state should explain that the organization has not granted access under the current policy without exposing private admin notes or internal reasoning that the employee should not see.
The state should still point the employee toward a safe next step such as contacting the employer or opening a permitted support path if the block seems incorrect.
The organization workspace should retain the internal policy reason, who blocked access, and whether the email can be restored or moved into a narrower role template later.
That keeps blocked state auditable without making the public-facing employee experience harsh or chaotic.