# Workflows
> A workflow is a trigger followed by steps, read top to bottom. Lodol keeps every version of it, runs it when it should, and records what each run did.
Web page: https://docs.lodol.com/docs/concepts/workflows
A workflow is the thing you build in Lodol: a trigger that says when it runs, followed by the steps it takes, in order. Anyone in your workspace can open it and read what it does, the way you'd read a short checklist.
## A workflow reads top to bottom
Lodol runs the steps in the order they're listed. A step can only use what came before it: the trigger's event and the results of earlier steps. Sections change that order in two ways:
- An **If** section runs its steps only when its condition is true, with an optional **Otherwise** for when it isn't. See [Make decisions](https://docs.lodol.com/docs/guides/conditions.md).
- A **Repeat** section runs its steps once for each item in a list, a set number of times, or while something is true. See [Repeat steps](https://docs.lodol.com/docs/guides/loops.md).
A run ends when it reaches the last step, when a step fails, or when someone stops it.
## It starts in one of three ways
Every workflow starts the same way each time:
| Start | Runs when | Example |
| --- | --- | --- |
| An app trigger | Something happens in a connected app | A new Stripe payment, a new Slack message, a new form response |
| A schedule | At the times you choose | Every 15 minutes, or every Monday at 9:00 |
| On demand | You, your code or another workflow starts it | A monthly report you run for one client at a time |
A workflow with a trigger or a schedule has to be turned on before it runs. [Triggers and schedules](https://docs.lodol.com/docs/concepts/triggers.md) covers all three.
## Every change is a version
Each time a workflow is saved, Lodol keeps a new version. You can see what changed against the version that's running and roll back to any earlier one. Saving a change pauses a workflow that was on, until it's turned back on.
A workflow keeps the same ID across all its versions, so links to it, and code that runs it through the [API](https://docs.lodol.com/docs/api/workflows.md), keep working after it's edited. Each [run](https://docs.lodol.com/docs/concepts/runs.md) records which version it ran.
## Private until you share it
A new workflow is visible only inside your workspace. To show one to someone outside it, make it public: anyone with its preview link can then see how it works, and you can make it private again at any time.
## Who can do what
What each member can do depends on their role in the workspace. The built-in roles are **Owner**, **Admin**, **Member** and **Viewer**:
- **Viewers** can see workflows, runs and apps, but can't change anything. They suit people who only need to follow along.
- Running workflows, deleting them and deleting runs are separate permissions, **Run workflows**, **Delete workflows** and **Delete runs**, which a role may or may not include. Deleting a workflow keeps its runs; only **Delete runs** removes them.
- On the Pro and Enterprise plans you can create custom roles with exactly the permissions each member needs.
The same limits apply to anything acting for a member: an [AI tool they connected](https://docs.lodol.com/docs/build-with-ai.md) and an [API key](https://docs.lodol.com/docs/api/authentication.md) they created can only do what their role allows.
## How many run at once
Each plan sets how many workflows can be running at the same moment: 3 on Free, 10 on Builder and 40 on Pro, with a custom limit on Enterprise. A run you start through the API while you're at the limit is refused, so your code can retry; see [Limits](https://docs.lodol.com/docs/api/limits.md). [Pricing](https://www.lodol.com/pricing) has the current plans.
## Next