Employee Office
Explore the current Employee Office preview for a role's duties, schedule, activity, tools, and focus without treating unfinished actions as live.
Last reviewed
Availability and purpose
Employee Office is Coming Soon. The preview shows how one Workforce role can have a focused operating space for duties, schedule, activity, tools, and current focus. Nested actions remain gated until those paths are wired and verified end to end.
The surface is an operations dossier, not a private room or a separate user account. It opens from a selected Workforce role and keeps the role identity, ownership, responsibilities, and evidence in one place.
Use Workforce and the role files as the current authority for assignments. Use the office preview to understand how those sources are intended to become easier to inspect.
Identity, focus, and role summary
The top of the office identifies the selected employee, team or office, scope, schedule, status, and role summary. It also provides a space for today's focus, core duties, and operational metrics.
If no role was selected, the page says so instead of inventing an employee. The correct next move is to return to Workforce and open a specific role. Initials, presence, and status are presentation signals; confirm actual role ownership in the source before assigning work.
Today's focus should describe a concrete workspace outcome. It is not permission to create unrelated work when the role has no current direction.
Office navigation
The left navigation separates the dossier into:
- Overview for the current role summary and operational context.
- Duties for recurring responsibilities and their schedules.
- Schedule for the selected day's duty cadence.
- Activity for recent role-linked work.
- Tools for capabilities associated with the role.
- Office settings for office-specific configuration.
An inspector on the right provides detail for the selected duty, activity, or tool. This layout is designed to reduce context switching: select a role, choose one type of evidence, and inspect it without losing the employee identity.
Duties and scheduling boundaries
The preview includes a New Duty form with name, priority, schedule, description, and instructions. A good duty names the outcome, explains what to check, and defines when to escalate. The visible form is not proof that public duty creation is active.
Before a duty can run safely, it needs an owner, valid workspace direction, a schedule, a clear output, and permission boundaries. The schedule options shown in the preview communicate intended cadence; they do not promise that a background job is active.
Do not use an empty office as a reason to invent recurring work. Return to the workspace goal, deadline, and role responsibilities first.
When the office looks wrong
If the page shows “No employee selected,” return to Workforce and open a role from the current workspace. If the identity or team is wrong, inspect the role and organization sources before editing anything.
If a duty appears saved but is missing after reload, treat it as unverified and do not assume it will run. If schedule navigation displays the wrong day, compare the date label with the workspace timezone and duty definition.
If the Call, Activity, Tools, or settings controls do not produce a verified result, stay within the preview boundary. Capture the selected role and visible panel, then use the review path rather than creating duplicate duties.