> ## Documentation Index
> Fetch the complete documentation index at: https://docs.z360.biz/llms.txt
> Use this file to discover all available pages before exploring further.

# Approvals and control

> Set a Work pipeline's approval and reasoning defaults, change them for one Work Item, set working hours, and step in on any job.

Work is built so that you choose how much the agent does alone. You can start by approving every action, then loosen the rules as you learn to trust a pipeline.

This page covers the controls that are specific to Work. For what each approval policy and reasoning level means, see [Approvals and reasoning](https://docs.z360.biz/guides/working-with-ask-z/approvals-and-reasoning.md).

## Your controls at a glance

| Control | What it decides | Where to set it |
| - | - | - |
| **Approval policy** | Which actions the Work agent must ask about first | Pipeline → **Agent** step |
| **Reasoning mode** | How capable the AI model is | Pipeline → **Agent** step |
| **Working hours** | When the agent may reach out | Pipeline → **Schedule** step |
| **The goal** | What the agent must ask a teammate about | Pipeline → **Agent** step |

To open a pipeline, go to **Settings → Pipelines**, or click **Manage pipelines** on the Work page.

## Pipeline defaults

Every Work Item's agent starts with the approval policy and reasoning mode set on its pipeline.

1. Go to **Settings → Pipelines** and open the pipeline.
2. Open the **Agent** step.
3. Choose the **Approval policy**: **Ask for approval**, **Auto**, or **Full access**. See [what each policy does](https://docs.z360.biz/guides/working-with-ask-z/approvals-and-reasoning.md#approval-policy).
4. Choose the **Reasoning mode**: **Everyday**, **Advanced**, or **Frontier**. See [how to choose a level](https://docs.z360.biz/guides/working-with-ask-z/approvals-and-reasoning.md#intelligence).
5. Save the step.

New pipelines start on **Auto** and **Everyday**.

> [!TIP]
>
> Put a new pipeline on **Ask for approval** for its first few jobs so you can watch every move. Choose **Advanced** when a job needs planning across several people and follow-ups.

## The Work agent and Inbox agents have separate approval settings

A job involves two kinds of agents, and each takes its approval setting from a different place.

| Agent | What it does | Approval comes from |
| - | - | - |
| **Work agent** | Plans the job, starts conversations, moves stages | The pipeline's **Approval policy** |
| **Inbox agent** | Writes and sends messages in one conversation | The Inbox default for that channel |

So setting a pipeline to **Ask for approval** does not make every customer message wait for you. To review messages before they are sent, also change the Inbox default for the channels the pipeline uses. See [Set Inbox defaults for approval and intelligence](https://docs.z360.biz/Agent-setup-and-schedule-availability.md#set-inbox-defaults-for-approval-and-intelligence).

## Where approval requests appear

* **From the Work agent** — in the Work Item's chat. Open **Work**, then click the Work Item.
* **From an Inbox agent** — in that conversation in **Inbox**. From the Work Item, open **Work Summary → Conversations** and click the conversation. Then click **Agent needs your attention** above the message box, or the agent's icon (the Z logo) in the bar on the right edge. The request opens in the panel on the right.

> [!TIP]
>
> To see every conversation that is waiting on you, open **Inbox** and choose the **Needs Attention** view. In the conversation list, a waiting conversation also shows a small stop icon.

The request shows as a card titled **Approval required**, with **Approve** and **Reject** buttons. For how to answer one, see [Respond to an approval request](https://docs.z360.biz/guides/working-with-ask-z/approvals-and-reasoning.md#respond-to-an-approval-request).

![A Work Item chat. Below the agent's message is a card titled Approval required. It names the action the agent wants to take and has a Reject button and an Approve button. The approval selector at the bottom left shows Ask for approval.](https://mintcdn.com/z360-fe526747/sOi4qySNiv1nnWzq/images/work/approval-request.png?fit=max\&auto=format\&n=sOi4qySNiv1nnWzq\&q=85\&s=6a63395b697171303c863026f47d4989)

An approval request in a Work Item's chat. Here the agent asks before it looks up the Work Item.

## Change the rules for one Work Item

Sometimes one job needs a tighter or looser leash than the rest.

Open the Work Item's chat and use the approval and reasoning selectors in the message box. The change applies to that Work Item only.

> [!NOTE]
>
> A Work Item picks up the pipeline's approval policy and reasoning mode when its agent starts. If you change the pipeline later, new Work Items use the new setting. Work Items already running keep theirs until you change them in their chat.

## Working hours

In the pipeline's **Schedule** step, set the **Weekly Availability**. The agent times its outreach inside these hours.

Working hours belong to the pipeline. A "Maintenance requests" pipeline can run seven days a week while a "Vendor onboarding" pipeline runs on weekdays only.

## When the Work agent asks you a question

The Work agent asks a teammate when your goal tells it to, or when it is missing something only your business knows. A question is different from an approval request, and it can appear under any approval policy.

* The question appears in the Work Item's chat.
* The agent is paused until someone answers.
* Any teammate who can open the Work Item can answer. It does not have to be the assignee.
* Pick one of the suggested answers, or type your own.

![The end of a Work Item chat. A card titled The agent has a question explains what is missing, offers two numbered answers, and has a box to type your own answer.](https://mintcdn.com/z360-fe526747/sOi4qySNiv1nnWzq/images/work/agent-question.png?fit=max\&auto=format\&n=sOi4qySNiv1nnWzq\&q=85\&s=810fc3b21521aa22fef3597bab3e0575)

The agent explains what it needs, suggests answers, and waits.

> [!WARNING]
>
> A paused agent does not send follow-ups. If a Work Item has been **In progress** for longer than you expect, open it and check whether the agent is waiting for you.

## Step in or take over

You are never locked out of a job.

* **Reply yourself.** Open the linked conversation in Inbox and answer the customer directly. Then tell the agent in the Work Item's chat.
* **Redirect the agent.** Tell it in the chat: "Stop contacting the vendor" or "Offer Friday instead".
* **Move the stage.** Change it from the Work page when you know something the agent does not.
* **End the job.** Tell the agent: "This is resolved. Mark it completed."

See [Manage Work Items](https://docs.z360.biz/guides/work/manage-work-items.md) for the steps.

## Protections that are always on

These apply under every approval policy, including **Full access**.

* The Work agent cannot message customers directly. Every message goes through an Inbox conversation your team can read.
* Form answers are treated as information, never as instructions to the agent.
* Blocked and Do Not Disturb contacts keep their restrictions. See [DND and Block Contact](https://docs.z360.biz/DND-and-Block-Contact-in-Z360.md).

## A sensible way to roll out

**1. Week one: watch everything**

Set the pipeline to **Ask for approval**, and review customer messages too by tightening the [Inbox defaults](https://docs.z360.biz/Agent-setup-and-schedule-availability.md#set-inbox-defaults-for-approval-and-intelligence) for the channels the pipeline uses. Approve each step and note where the agent surprises you.

**2. Fix the goal, not the agent**

Each surprise points to something the goal did not say. Add it. See [Write a goal the agent can follow](https://docs.z360.biz/guides/work/write-a-pipeline-goal.md).

**3. Loosen one setting at a time**

Move the pipeline to **Auto** first. When that runs well, relax the Inbox defaults.

**4. Keep the human decisions in the goal**

Even on **Full access**, a goal that says "ask a teammate before agreeing to a cost above \$300" still tells the agent to stop and ask.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.