Introduction
Some workflow actions need a person's input before they proceed. In Copilot Studio, a workflow can pause, ask a designated person for a decision or a missing value, and use the answer in later steps. Placing that pause at the right point keeps a policy-gated action from running until an authorized person answers.
Consider a reimbursement process in which an employee asks an agent to submit an expense. You might let a claim below your organization's threshold proceed without review, while a larger claim waits for a manager's Yes or No decision before reimbursement. If the claim needs a project code that the employee doesn't know, the workflow can ask the project owner to supply that value. Both pauses happen inside the workflow. The person answering the request might be someone other than the employee who talks to the agent, and their answer might take longer than an agent can wait for a workflow to respond.
In this module, you explore:
- How to decide when a workflow step needs a human decision and who supplies the answer.
- How to implement a request-for-information pattern that collects values from a designated person.
- How to branch a workflow on a human decision by using a Yes/No response.
By the end of this module, you can decide where a workflow needs human review, collect the values it needs from a designated person, and keep a policy-gated action behind an explicit approval.