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

# Flow Settings

> Configure a flow's identity, visibility, permissions, notifications, naming, and reminders

Every flow has a Settings panel (titled **Workflow Settings**) that controls its behavior, visibility, access, and notifications. To open it, go to the **Flows** list, hover the flow you want, click the **⋮** menu on its card, and select **Flow Settings**.

## General

Set the flow's core identity and defaults.

| Setting                | What it does                                                                                 |
| ---------------------- | -------------------------------------------------------------------------------------------- |
| Workflow Name          | The display name team members see when browsing or submitting requests                       |
| Workflow Description   | A short explanation of the flow's purpose, shown to requesters before they submit            |
| Priority               | The default priority (Low, Medium, High) for new tasks — can be changed per task             |
| Ownership              | The user automatically assigned as owner when a task is created                              |
| Global Signing Account | The account DocuSign envelopes are sent from by default, unless overridden at the task level |
| Task SLA               | An optional default due date for tasks created from this workflow                            |

## Steps Visibility

Controls whether requesters can see individual steps as their task progresses.

<Tabs>
  <Tab title="Visible to Requester">
    All steps are visible by default. Individual steps can still be hidden.
  </Tab>

  <Tab title="Hidden from Requester">
    All steps are hidden by default. Use **Visible Steps** to selectively expose specific steps — anything not added there stays hidden.
  </Tab>
</Tabs>

## Permissions

Controls who has access to the flow and what they can do.

### Roles

| Role         | Access                                      |
| ------------ | ------------------------------------------- |
| Manager      | Full control over every aspect of the flow  |
| Collaborator | Can view the flow and its contents          |
| Requester    | Can submit and view only their own requests |

Add users by clicking **+ Add** and selecting Everyone, specific members, or groups. Remove access with the **×** next to an entry, or change a role from the role dropdown.

<Info>
  This is the general flow-access role set. Task-level roles (Owner, Assignee) are separate — see [Roles and Permission Levels](/features/flows/roles-permissions).
</Info>

### Field edit permissions

Choose a default for every field in the flow:

* **All Fields Need Approval** — every field requires approval before a change takes effect, unless overridden at the field level
* **No Approval Required** — every field can be edited immediately, unless overridden at the field level

Use **Fields Require Approval** to name exceptions to whichever default you picked.

## Notifications

For each lifecycle event, choose who's notified: Owner, Assignee, Requester, or All.

| Event              | Fires when                           |
| ------------------ | ------------------------------------ |
| Flow initiated     | A flow is started                    |
| New Assignee       | A task is assigned to someone        |
| Task completed     | A task is marked complete            |
| Task cancelled     | A task is cancelled                  |
| Task owner changed | The task's owner is updated          |
| Task rewind        | A task is rewound to a previous step |
| Task failed        | A task encounters a failure          |
| Task on hold       | A task is put on hold                |
| Task resumed       | A task on hold is resumed            |

## Naming

Build the filename template used for documents this flow produces.

* **Task Title** — Chamelio names tasks automatically. Choose **Agent** (an AI-generated title from the document's content, guided by your own prompt and `@` tokens like `@Workflow name`) or **Manual** (a fixed template you build with `@` fields, with a live preview).
* **Version Preferences** — control how stored versions are named during the negotiate step.
* **Signed Document Preferences** — control how contracts are named once signed.

## Reminders

Automatic nudges based on a task's status and deadlines.

* **Who to remind** — applies across all reminder types below
* **Days in step** — remind assignees after a task has sat in a step for N days, on a repeat cadence
* **Task not assigned** — alert when a task has no assignee, after a configurable delay
* **Task overdue** — escalate when a task misses its due date