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

# Inputs and approvals

> Collect automation inputs and apply approval policies.

## Inputs

Inputs are the values an automation needs when a run starts. Use clear labels and make a field
required only when the automation cannot continue without it.

Simple text, number, and yes-or-no values appear as manual fields in the test panel. Use **JSON** for
nested objects, lists, or other structured input.

When someone requests a published automation from the catalog, Flow uses its saved defaults for omitted
inputs. Values the requester provides take precedence. Defaults must satisfy the input's validation
rules.

## Test inputs

<Steps>
  <Step title="Open the automation." />

  <Step title="Select Test. After you publish, select the options arrow beside Run, then choose Test." />

  <Step title="Under Input, use Manual fields or JSON." />

  <Step title="Start with Simulated mode." />

  <Step title="Test a valid example and the important missing or invalid values." />
</Steps>

Use **Live** only when you intend to change a connected system.

## Approvals

Flow includes four standard approval procedures for automations in v1:

| Procedure | Stable key | Routes the approval to |
| - | - | - |
| **Manager Approval** | `requester-manager` | The requested-for person's manager |
| **Target Team Managers** | `target-team-managers` | Every active manager of the target team |
| **Organization Administrators** | `organization-administrators` | Every active organization administrator |
| **Workflow-Selected Approvers** | `workflow-selected-approvers` | Active organization users selected by the running automation. Any one can approve |

An approval can run before the automation starts or pause it at a specific step. **Manager Approval**
needs a manager email or directory manager ID in the requested-for person's Flow profile. That
reference must resolve to one active organization user who is eligible to approve. A manager name
alone is not enough.
[Directory Sync](/setup/administration/identity-and-directory#when-to-connect-directory-sync)
can supply and update that relationship. Single sign-on (SSO) alone does not keep it synchronized. If Flow cannot
resolve the manager, the procedure cannot route the approval; it does not guess an approver or skip
the decision.
Check that the manager information is synced before using this procedure, or choose another
procedure that fits your policy.

Target Team Managers requires the target team to have at least one active manager.
Workflow-Selected Approvers is available only at a step inside
the running automation. It requires a non-empty `approvers` list of organization-user IDs or primary
email addresses and supports up to 250 potential approvers.

Select those approvers through trusted automation logic or organization-controlled data.
Do not map a requester-provided approver list directly to the procedure. Use your
organization's policy to decide which access requires approval and who can approve.
For example, a group access automation can approve employee announcements access
automatically and require reviewers for confidential finance access. Map each access
type to a configured group, evaluate that exact group, and grant only the approved group.
Check that the employee receiving access matches the person the request is for before
requesting approval. This keeps self-approval rules tied to the person receiving access.
Deny unsupported groups. A requester must not be able to select announcements access
and substitute a confidential group.

The browser does not support managing custom approval procedures in v1. Organization administrators
can manage them through the [public API](/api-reference).

## Add an approval

<Steps>
  <Step title="Tell Flow which standard procedure to use." />

  <Step title="Tell Flow where the decision belongs." />

  <Step title="Map any procedure input from the automation." />

  <Step title="Save the revision." />

  <Step title="In Simulated mode, test both approval and denial." />

  <Step title="Publish the automation.">
    Do this only after both paths work and Validation scenario review is current for the revision.
  </Step>
</Steps>

Publication is blocked when the procedure is unavailable for a selected audience.

Simulated mode uses the approval outcome you select to test what happens after approval
or denial. It does not verify real approver routing. Before using Live mode, check the
procedure's policy and confirm that an actual request reaches the intended eligible
approvers.

## Related topics

* [Test and publish](/automations/build/test-and-publish) (Validation scenarios, draft testing, and publish)
* [Run history and debugging](/automations/run/run-history-and-debugging)


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