Organization Onboarding Detail
A concrete managed-account onboarding path for one organization, showing role mapping, workspace destination, visibility disclosure, and first-market entry.
The detail page should anchor the actual onboarding template used by this organization.
Managed role assignment belongs on the first screen, not hidden in a secondary policy lane.
The new employee should know where the organization conversation starts the moment access is approved.
This is where enterprise onboarding becomes operational instead of abstract.
That prevents a messy split between what the company thinks it configured and what the employee actually experiences.
{
"template_id": "northstar_managed_account",
"default_workspace": "organization_workspace",
"role_template": "operations_manager",
"visibility_policy": "full_managed_account_visibility",
"first_channels": ["general", "results", "handoff-audit"]
}Managed onboarding detail should connect employee disclosure, workspace routing, and first-market participation in one view.
The employee’s first signed-in destination should be explicit and policy-aware.
The managed onboarding detail should show the exact role mapping being applied.
Visibility scope must be disclosed up front because it shapes what the organization can review.
The employee should know which programs open first after approval.
The first social surfaces should already be attached to the managed onboarding flow.
Onboarding detail should always point to the exact activation outcome.
Role, visibility, and workspace routing are all disclosed before activation.
The first markets and channels for this onboarding path are nearly ready.
Employees can be sent directly into the organization workspace after approval.
The managed-account onboarding template was approved for Northstar rollout.
The employee-facing visibility policy copy and audit state were finalized.
The rollout owner will confirm first-market and first-channel readiness before launch.
A real organization onboarding detail page should show the exact organization, role template, default workspace destination, and first market programs the employee will see after approval.
This is where enterprise onboarding becomes operational instead of abstract.
The detail view should keep managed visibility policy, organization workspace routing, and any payroll-linked next steps visible so the employee and the admin owner share the same understanding.
That prevents a messy split between what the company thinks it configured and what the employee actually experiences.