Governed actions and approvals¶
HiveAI can prepare a supported change to your work and ask you to review it before execution. A proposal identifies the work involved, the exact change, its conditions and the decision needed from you. Approval permits that reviewed change to proceed while the relevant permissions and source state remain valid.
For example, a proposal may ask to move a workflow task from one colleague to another. Reading a suggestion does not change the task. Approving the proposal does not mean the reassignment has finished. Check the saved result before treating the new assignment as confirmed.
Availability¶
The backend contains proposal, approval, execution, status, recovery and supported restoration mechanisms. Current Final Screens show the intended review and recovery experience, including spoken decisions. The inspected frontend does not yet provide the complete HiveAI action journey. Use the task guide where the corresponding experience is available in your environment.
Some backend boundaries still need reconciliation, including consistent reviewer authority, recovery after interrupted processing, and reliable restoration of the previous assignment. The designed screens and these draft guides do not establish a completed rollout. Verify the current source result when a change matters to ongoing work.
The life of a change¶
| Stage | What it means | What to do |
|---|---|---|
| Proposed | HiveAI has prepared a specific change for review | Check the target, current and proposed values, effects and expiry |
| Approved and waiting | Your decision has been recorded; execution may not have begun | Read progress; use the available stop control if you change your mind |
| Being processed | The owning application is processing the approved change | Wait for its confirmed result |
| Outcome unconfirmed | HiveAI cannot yet establish what happened | Keep the original request and follow its recovery path |
| Completed | The source has reported the particular change as completed | Open the affected work and verify the result |
| Stopped, rejected or unable to continue | This proposal will not proceed through its current path | Read the reason and any work already completed before deciding what to do next |
| Restoration proposed | A supported corrective change has been prepared | Review and approve it separately |
A conversation can finish updating after the underlying task has changed. A saved preparation step can also remain when the requested business change did not complete. Read the specific result, rather than relying on a general progress label.
Access and human responsibility¶
Governed actions require the relevant HiveAI capability and permission to perform the source operation. Workspace policy, account status, source access, information classification, provider policy and spending controls also affect availability.
Approval does not grant new access. The system checks the requester's current authority and the source state again before execution. A policy change, expired review or changed task can prevent the approved proposal from proceeding.
For reassignment and escalation, the target must have a human-supplied or deterministic basis. Treat a colleague suggested in prose as a suggestion until the exact target appears in a review you can evaluate.
Approval has a precise scope¶
The approval concerns the displayed action and target. It is not standing permission for future changes, a general authorization to “handle everything,” or an approval of every business process the source may subsequently start.
Creating a memo draft differs from submitting it into its normal approval process. Completing a task differs from completing the whole workflow. Attaching a record to a dossier differs from transferring ownership or making that record visible to everyone.
A changed target or instruction needs a new review. Refreshing an expired review reads saved information; it does not extend the original approval period.
Recovery and restoration¶
Refresh status reads the saved state. Recover original change asks the system to resolve the existing approved operation and may allow that same operation to continue after checking the source. These controls have different effects.
A timeout is not proof that nothing changed. Keep the existing request while its result is unresolved. Creating a replacement request can make it harder to distinguish the original outcome from a second change.
Restoration is available only for actions that support it, while current source conditions permit it. It is a separate reviewed change. It does not erase history, automatically recall notifications or reverse every consequence of the original work.
For managers and executives¶
Assess success from the confirmed business result: the correct task moved to the correct person, the intended draft was created, or the correct record was attached. Counts of proposals, approvals or processing attempts do not establish completed business outcomes.
Define who may request and approve each type of work, how unresolved actions are followed up, and when a person should use the owning application directly. The assistant's review is additional to the source application's business rules.
Continue with reviewing and recovering a change, conversation and spoken-input guidance, credits and budgets, and HiveAI access and capabilities.
Review changes within a reusable workflow¶
An assisted workflow can prepare a sequence of supported changes. Starting its run does not approve the first or later tasks. Follow the workflow guide for selected inputs, separate decisions, run progress, stopping and recovery. A confirmed action and a completed saved run remain separate facts.
For actions performed by Zerohive platform staff, see Platform staff assistance and controlled actions. That path uses its own staff authority, exact proposal and source-operation recovery; tenant governed-action rules do not substitute for it.