Employee Directory
Search the organization directory, review employee roles and access state, and move from approvals into person-level commitment operations.
The directory should open with live employee volume, not a generic people stub.
Operators need approval pressure visible beside the employee roster itself.
Employees with live commitments stay visible as a protected subgroup instead of disappearing into queue-only views.
Managers and admins should not need to jump between approvals, payroll, and commitment history just to understand what one employee can currently do.
That state makes the directory useful for real operations instead of reducing it to a static member list.
That is what turns the organization workspace into a real control center instead of a one-time onboarding tool.
{
"organization_id": "org_northstar_logistics",
"employees": 842,
"active": 716,
"pending": 46,
"continuity_access": 7,
"directory_filters": ["role", "team", "status", "manager"]
}A real employee directory should stay searchable, stateful, and linked directly to approval, payroll, and commitment operations.
The employee lane should feel like a real directory with live people, not a static settings list.
Team ownership stays visible so managers can work from their real operating boundary.
Approval pressure belongs on the employee page because it changes how the roster is actually shaped.
Employees with active commitments and reduced org access remain visible as a protected cohort.
Direct-deposit and wallet setup should stay visible from the same employee operating surface.
The organization’s disclosure posture should stay readable beside the roster.
Most company-managed accounts are already active inside the workspace.
A smaller but meaningful slice still needs company review before entry is granted.
A protected subset still has active commitments and reduced org access.
The organization directory refreshed after the latest company-email signup and invite wave.
A new request wave increased pending employees and updated manager-owned team lanes.
The organization confirmed its current managed visibility template for employee accounts.
The employee directory is the operating surface that ties company-email onboarding, organization roles, current commitments, and access state into one searchable lane.
Managers and admins should not need to jump between approvals, payroll, and commitment history just to understand what one employee can currently do.
Each employee record can show whether the person is invited, active, pending approval, temporarily restricted, or in continuity access mode while active commitments remain open.
That state makes the directory useful for real operations instead of reducing it to a static member list.
The directory should support role review, team filtering, manager-level oversight, and quick jumps into employee detail so a company can work from the roster it actually operates every day.
That is what turns the organization workspace into a real control center instead of a one-time onboarding tool.