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

# Workflow Configuration

> Configure workflow behavior, approvals, inputs, and execution scope

After creating a workflow, configure how it runs, who can run it, and what information it needs. This guide provides an overview of all configuration options.

## 1. Create a Workflow

To get started with automations, start by either building a workflow from scratch or installing a workflow.

<CardGroup cols={3}>
  <Card title="Build a Workflow" icon="shapes" href="/sections/documentation/workflows/create-your-first-workflow">
    Build a workflow from scratch by inputting the automation in natural language
  </Card>

  <Card title="Install a workflow" icon="shapes" href="/sections/documentation/workflows/Configure/installable">
    Select a pre-built workflow to start with and configure as needed
  </Card>

  <Card title="Duplicate" icon="copy" href="/sections/documentation/workflows/Configure/duplicate">
    If there's another Team in Serval already set up, you can duplicate workflows across teams
  </Card>
</CardGroup>

## 2. Configure the Workflow

Once you've created a workflow, you can configure that workflow with the following specificiations to meet your organization's needs.

<CardGroup cols={2}>
  <Card title="Workflow Types" icon="shapes" href="/sections/documentation/workflows/Configure/types">
    Choose the right type: help desk, team-only, scheduled, webhook, event-triggered, or access workflows
  </Card>

  <Card title="Triggers" icon="bolt" href="/sections/documentation/workflows/Run/triggers">
    Configure when workflows run: manually, on schedule, via webhook, or on events
  </Card>

  <Card title="Approvals" icon="check-double" href="/sections/documentation/workflows/Configure/approvals">
    Require approval before execution using static approvers or custom approval workflows
  </Card>

  <Card title="Inputs" icon="keyboard" href="/sections/documentation/workflows/Configure/inputs">
    Collect information from users: text, dropdowns, dates, and more. Workflows with form inputs automatically appear as catalog items.
  </Card>

  <Card title="Execution Scope" icon="users" href="/sections/documentation/workflows/Configure/execution-scope">
    Control who can run the workflow: anyone in the org or team members only
  </Card>

  <Card title="Versioning" icon="clock-rotate-left" href="/sections/documentation/workflows/Manage/versioning">
    Track changes and restore previous versions of your workflows
  </Card>
</CardGroup>

***

## Quick Reference

| Setting             | What it controls                  | Options                                                   |
| :------------------ | :-------------------------------- | :-------------------------------------------------------- |
| **Type**            | Who can trigger and how           | Help desk, team-only, scheduled, webhook, event-triggered |
| **Trigger**         | When the workflow runs            | Manual, scheduled, webhook, event-based                   |
| **Approvals**       | Who must approve before execution | None, specific users, groups, manager, custom workflow    |
| **Inputs**          | What information users provide    | Text, textarea, number, date, time, select, checkbox      |
| **Execution scope** | Who can run the workflow          | Anyone in org, team members only                          |

***

## Common Configurations

### Self-Service Help Desk Workflow

For workflows that help desk users can trigger:

| Setting         | Configuration                                    |
| :-------------- | :----------------------------------------------- |
| Type            | Help desk                                        |
| Execution scope | Anyone in the org                                |
| Approvals       | None (or manager approval for sensitive actions) |
| Inputs          | Minimal—agent collects info conversationally     |

### Internal Team Workflow

For workflows restricted to your team:

| Setting         | Configuration               |
| :-------------- | :-------------------------- |
| Type            | Team-only                   |
| Execution scope | Team members                |
| Approvals       | Optional                    |
| Inputs          | As needed for the operation |

### Automated Report

For scheduled reports and notifications:

| Setting   | Configuration                 |
| :-------- | :---------------------------- |
| Type      | Scheduled                     |
| Trigger   | Weekly Monday 9am PST         |
| Approvals | None                          |
| Inputs    | None (or defaults configured) |

### Sensitive Operation

For workflows that need oversight:

| Setting   | Configuration                                  |
| :-------- | :--------------------------------------------- |
| Type      | Help desk or team-only                         |
| Approvals | Manager approval or multi-step approval chain  |
| Inputs    | Justification text area, confirmation checkbox |

***

## Child Workflows

A child workflow is a workflow that the parent workflow calls as a step in its own process. Build a piece of logic once, then reuse it across any number of parent workflows instead of rebuilding it each time.

Use child workflows to keep shared logic in a single source of truth. Common use cases include:

* Shared onboarding and offboarding steps that several team workflows depend on
* Centralized approval flows reused across any workflow that needs approval
* Standard escalation routines that multiple teams run the same way

When you describe a parent workflow calling a child in the workflow builder, the builder agent reads the child's input fields and types. It then wires up the call with the right parameters.

If a child workflow requires approval, that approval surfaces on the parent workflow's ticket and sends a Slack notification, so a pending child never stalls the parent silently. Serval links child runs to the parent run, so the tree in run history shows the entire, combined process.