Use My Day and check work status¶
Use My Day as a starting point for reviewing your workflow tasks. Confirm deadlines and complete work in the owning WorkOS view.
Before following these steps: the current frontend is work in progress and the HiveAI entry is disabled in the inspected version. The steps below describe the intended Final Screens journey where that experience becomes available. They do not confirm deployment. Status-check and return-to-work controls still need complete screen verification.
Before you begin¶
You need access to HiveAI in your organization and to the relevant WorkOS feature. Your signed-in account must match an active workforce profile with a valid timezone. The service also needs to verify current membership of any work pools used to select your tasks.
Check that you are working in the intended organization. Your permissions and available AI credits still apply. A manager cannot choose another member's identity by writing it in the question.
If the entry is missing, continue in WorkOS and ask your administrator about availability. The absence of HiveAI does not prevent you from using WorkOS features you already have permission to use.
Ask about your work today¶
- In the intended HiveAI conversation, use Your question. If you are unsure what it can check, ask “What can you show in My Day?”
- Ask “Which tasks are due today?” and send the question. This is the wording shown in Final Screens; the current selection also includes overdue and undated eligible tasks.
- Read the response and any message about tasks that could not be checked. The populated design shows Today's workflow tasks; the partial design shows Tasks I could confirm.
- Review the relevant tasks in WorkOS. Check the actual item, current assignment, deadline and available actions before deciding what to do.
- After completing or changing work, check its current WorkOS state. Ask again if you need a refreshed assistant answer; an earlier answer does not update itself.
The inspected screens show task text and advice to review work in WorkOS. They do not establish a tested task-opening control or an automatic return path. Use your normal WorkOS navigation when a direct link is unavailable.
Interpret the list and its order¶
Tasks can be assigned directly to you or belong to a shared work pool you may currently use. A pooled task appearing in the result does not mean it has already been accepted or assigned to you.
The service uses the current day in your verified profile timezone. The current tool does not support selecting an arbitrary day or overriding timezone through the question. If your timezone is wrong, use your organization's profile-correction process or ask your administrator; do not rely on different wording to fix it.
The list is limited, normally to 25 tasks. Selection occurs before the final ordering, and tasks with no due date or an overdue deadline can be included. Do not infer that the first item is the highest priority in your entire workload, or that omitted tasks can be ignored.
Check exact times in WorkOS. The intended design includes example times, but the current assistant result drops due-time details. The examples do not establish actual deadlines for your work.
When no tasks are shown¶
The empty design says No tasks due today. Treat an empty result as no matching tasks returned for the checked scope, rather than proof that you have no work.
Open your WorkOS task list and check current assignments, shared pools and any relevant filters. Work can be outside the current selection, assigned after the response, or require a different feature or permission.
The empty design also suggests asking about another day. That suggestion is ahead of the current tool, which resolves the present day only. Use the task views available in WorkOS to investigate other dates.
When some tasks may be missing¶
The partial design explains that some tasks could not be loaded and asks you to check WorkOS before treating the list as complete.
Review the tasks that are shown, then check your full WorkOS list before planning around the answer. Do not assume that a missing task has been completed, reassigned or removed. Do not use the number shown as a total workload count.
The current limited read does not reliably signal that additional tasks were excluded. Follow the same completeness check even when no warning appears. Asking again can refresh the read, but does not create an exhaustive paginated list.
Recover when tasks cannot be checked¶
The unavailable design says Workflow tasks unavailable and suggests trying again or opening your tasks in WorkOS.
| Situation | What to do |
|---|---|
| HiveAI is missing or unavailable | Continue in WorkOS and confirm feature availability with your administrator |
| You are signed into the wrong organization | Return to the correct organization before asking again |
| Profile identity or timezone is incorrect | Ask for the profile to be corrected; text in a question cannot override verified identity or day |
| Pool membership or permissions changed | Check current access with your administrator; do not borrow another person's account |
| The service could not check tasks | Retry after a short pause or continue in WorkOS; repeated immediate requests may remain unavailable |
| WorkOS and the answer differ | Use the current authorized WorkOS item to verify the state; retain the time of the discrepancy for support |
| A previously visible item is unavailable | Recheck current access and item state; an old answer is not continuing access permission |
An unavailable response does not prove an empty workload. A temporary failure should not be translated into “nothing is due.”
Check a memo, letter or record¶
The backend supports a read-only check of a particular memo, official letter or record. Complete final-screen instructions for selecting that item and returning to it have not yet been established, so this guide does not invent a menu or button.
Where a delivered conversation can identify an item you are allowed to access, ask a clear question about that specific item. If it cannot resolve the item safely, open the item in WorkOS and use its current view. Do not guess an identity from similar names, paste sensitive contents unnecessarily or assume that a quoted reference grants permission.
For correspondence, distinguish the displayed status from the full lifecycle and delivery history. For a record, distinguish its stage from filing, custody and disposition. The current assistant response does not preserve all those separate details. Inspect the corresponding WorkOS view before making a decision that depends on them.
Some records or correspondence are intentionally excluded from this read path; additional access restrictions may also make a status unavailable. That is not proof of deletion or permission to obtain the information another way. Consult records or correspondence for the owning feature's guidance.
Return to work and confirm the outcome¶
Reading status or asking what needs attention does not accept, complete, delegate, dispatch, archive or otherwise change an item.
Before an action, open the correct WorkOS item, check its current state and follow the feature's confirmation steps. After the action, verify its actual outcome there. If HiveAI later offers an action proposal, treat the proposal, your confirmation and the completed result as separate stages; the conversation guide explains this distinction.
Avoid repeating an uncertain mutation merely because an old My Day answer still lists the task. Recover the original action outcome in the owning feature first.
For managers, executives and administrators¶
Managers and executives should use My Day for personal orientation and source follow-up. It does not measure team capacity, compare employees, prove that a deadline was met or certify that all relevant work was considered. Use the organization's authorized reporting and review processes for those decisions.
Tenant administrators should check identity, timezone, current permissions, pool membership and HiveAI availability when a member cannot obtain a useful result. Platform staff should check service and policy conditions through restricted operational procedures. Access to an operational role is not permission to read every member's work.
Support can request the organization, approximate time, which feature was being checked, the visible safe error and any provided request reference. Record whether WorkOS itself was available. Avoid passwords, tokens, private document text or another member's work in support notes.
Example: plan a morning review¶
A member asks for today's tasks and sees two references. One is overdue; another belongs to a shared pool. They open their WorkOS task list, verify both deadlines, check whether the pooled item is still available and review other work omitted from the limited answer.
They accept or complete work only through the appropriate authorized action, then confirm the resulting state. The assistant helped choose a starting point; the WorkOS checks established the facts used to act.