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

# Workflow settings

> The settings that belong to the whole workflow — the environment, the execution timeout and the global rules.

Workflow settings belong to the workflow itself. They apply to every node and to every execution.

You edit them as chips along the bottom of the builder.

Three settings live here.

<CardGroup cols={3}>
  <Card title="Environment" icon="monitor" horizontal>Where the workflow runs</Card>
  <Card title="Timeout" icon="clock" horizontal>How long an execution may take</Card>
  <Card title="Global rules" icon="scroll-text" horizontal>Instructions every node receives</Card>
</CardGroup>

## Environment

Choose **Browser** for a Chromium web browser, or **Linux** or **Windows** for a full desktop.

The environment decides which capabilities each Agent node can use. See [Environments](/concepts/environments) and [What a node can do](/concepts/node-capabilities).

## Timeout

**Timeout (minutes)** accepts `1` to `120`.

It is the maximum time an execution may take. An execution that passes the limit ends as `failed`, or as `cancelled` with the reason `timeout`. See [Executions and statuses](/concepts/executions).

## Global rules

Global rules are instructions that apply across the whole workflow rather than to one node. Every Agent node receives them alongside its own instructions.

Put guidance here when it should hold everywhere:

* tone and formatting conventions
* sites or actions to avoid
* how to handle a blocker that can appear at any point in the execution

Rules take the same `{{.variable}}` templating as node instructions, so they can read the workflow's [inputs](/concepts/inputs-and-outputs).

See [Write good instructions](/build/instructions) for how to phrase them.

## Workflow management

The same panel holds the controls for the workflow as a whole.

<AccordionGroup>
  <Accordion title="Name and organization">
    Change the display name of the workflow.

    Set the organization that owns it. Anyone with access to that organization can see and run the workflow.
  </Accordion>

  <Accordion title="Clear browser cache">
    Clear the browser cache held by the [profile](/concepts/profiles) this workflow uses. This removes:

    * cached data and files
    * stored cookies and sessions
    * browser state and preferences
  </Accordion>

  <Accordion title="Delete workflow">
    Delete the workflow for good. This removes every version, the whole execution history, and all associated data.

    <Warning>
      You cannot undo a deletion. Export anything you need first.
    </Warning>
  </Accordion>
</AccordionGroup>

## What lives elsewhere

Credentials, two-factor secrets, cookies, proxy settings, cache persistence and the inbox belong to an [agent profile](/concepts/profiles). A profile is reusable, so several workflows can share one.

<CardGroup cols={2}>
  <Card title="Agent profiles" icon="id-card" href="/concepts/profiles">Credentials, cookies and proxy settings</Card>
  <Card title="Environments" icon="monitor" href="/concepts/environments">Browser, Linux and Windows</Card>
</CardGroup>