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

# Overview

> Automate recurring identity and access actions with configurable triggers, conditions, and approval steps, built from a template or from scratch.

Workflows automate the identity and access actions your team would otherwise run by hand - finding dormant accounts, checking MFA coverage, or tracking down expiring non-human identity (NHI) credentials - and take action on a schedule, with an optional approval step before anything changes.

## How a workflow is built

Every workflow is made up of the same building blocks:

* **Trigger** - when the workflow runs, for example on a daily schedule.
* **Condition** - a query step that finds the accounts, resources, or identities matching a set of filters, for example accounts inactive for more than 90 days.
* **Approval** - an optional human-in-the-loop step before the action runs. Depending on the workflow, this can be a direct approval (routed to a manager or owner, with an alternate approver and a defined deny behavior), a time-based escalation, or a reviewer sign-off.
* **Action** - what the workflow does once conditions and approvals are met, for example disabling an account.

Each workflow has a **Build** view showing this flow, and a **Runs** tab showing its execution history.

## Workflow templates

Rather than building a workflow from scratch, start from a library of ready-made templates covering common identity and access automation - see [Workflow templates](/posture/workflow-templates). If you need automation a template doesn't cover, you can request a new one.

## Contact us

For questions, contact us at [support@oleria.com](mailto:support@oleria.com).