diff --git a/docs/automations/custom-automations.md b/docs/automations/custom-automations.md
index b34c3a1..b42bfb6 100644
--- a/docs/automations/custom-automations.md
+++ b/docs/automations/custom-automations.md
@@ -7,48 +7,19 @@ description: Automate repetitive project tasks with trigger-based workflows. Set
Custom automations let you streamline your project management workflow by automatically performing actions based on specific triggers and conditions. This powerful feature eliminates repetitive manual tasks, ensures consistency in your processes, and helps your team maintain focus on high-value work by letting the system handle routine operations.
-Think of automations as your digital assistant that watches for specific events in your projects and responds according to rules you define. Whether it's updating work item statuses, assigning team members, adding labels, or posting comments, automations work behind the scenes to keep your projects moving smoothly.
-
-For built-in automations, see [Automations](/automations/overview).
-
-## How custom automations work
-
-Automations follow a simple but powerful logic: When [trigger] happens, if [conditions] are met, then perform [actions]. This trigger-condition-action framework allows you to create sophisticated workflows that adapt to your team's specific needs.
-
-Every custom automation has three components.
+For default automations, see [Automations](/automations/overview).
-**Triggers** are events that start the automation. A single event fires the automation, which then evaluates conditions before executing actions.
+Every custom automation has three components. When [trigger] happens, if [conditions] are met, then perform [actions]. This trigger-condition-action framework allows you to create sophisticated workflows that adapt to your team's specific needs.
-| Trigger | Fires when… |
-| ----------------- | ----------------------------------------------- |
-| Work item created | A new work item is added to the project |
-| Work item updated | Any property on a work item changes |
-| State changed | A work item moves to a different workflow state |
-| Assignee changed | A work item's assignee is added or removed |
-| Comment created | Someone adds a comment to a work item |
+- **Triggers** are events that start the automation. A single event fires the automation, which then evaluates conditions before executing actions.
+- **Conditions** are optional filters that must be satisfied for the automation to proceed. If you add multiple conditions, all of them must be met (AND logic).
+- **Actions** are what the automation does when fired. Multiple actions execute in sequence.
-**Conditions** are optional filters that must be satisfied for the automation to proceed. If you add multiple conditions, all of them must be met (AND logic).
+## Create a custom project automation
-| Condition | Filters on… |
-| ---------- | ------------------------------------ |
-| State | A specific workflow state |
-| Type | A specific work item type |
-| Label | One or more project labels |
-| Assignees | Specific team members |
-| Created by | The person who created the work item |
-| Priority | A specific priority level |
-
-**Actions** are what the automation does when fired. Multiple actions execute in sequence.
-
-| Action | What it does |
-| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Add comment | Posts an automatic comment on the work item |
-| Change property | Updates a work item property: state, priority, assignee, labels, start date, or due date |
-| Run Script | Executes a [Plane Runner](/automations/plane-runner) script, giving you full programmatic control — call external APIs, create linked work items, enforce custom business logic, or anything else you can write in JavaScript or TypeScript |
-
-## Set up automations
+Project automations apply to work items within a single project.
@@ -57,52 +28,216 @@ Every custom automation has three components.
3. Give your automation a descriptive name and an optional description, then save.
4. Click **Add trigger** and choose the event that should start the automation.
5. Optionally click **Add condition** to narrow when the automation runs. You can add multiple conditions — the automation only fires when all conditions are met.
-6. Click **Add action** to define what happens. Choose from **Add comment**, **Change property**, or **Run Script** . You can add multiple actions — they execute in sequence.
-7. Click **Enable** in the top right corner to activate the automation.
+6. Click **Add action** to define what happens. Choose from **Add comment**, **Change property**, or **Run Script**. You can add multiple actions — they execute in sequence.
+7. Click **Confirm**.
+8. Click **Enable** when you're ready for it to go live.
+
+An automation needs at least one trigger and one action before you can enable it. Until you enable it, it stays in draft and doesn't run.
::: tip
You can add multiple conditions to create more specific rules and multiple actions to perform several operations in sequence on a single trigger.
:::
+## Create a workspace automation
+
+Workspace automations can span your entire workspace or a specific set of projects.
+
+1. Go to **Workspace Settings → Automations**.
+2. Click **Create automation**.
+3. Choose which projects the automation should apply to — all projects in the workspace, or a specific subset.
+4. Follow the same steps as a project automation: name → trigger → conditions → actions.
+5. Enable when ready.
+
+## Configure a scheduled trigger
+
+If you want an automation to run on a timer rather than in response to an event:
+
+1. Open the automation and go to the **Trigger** tab.
+2. Select **Scheduled**.
+3. Choose a frequency: **Daily**, **Weekly**, or **Monthly**.
+ - Weekly: pick which days of the week.
+ - Monthly: pick the day of the month (1–31).
+4. Set the time (hour and minute) and your timezone.
+5. Alternatively, switch to **Cron mode** and enter a 5-field cron expression directly.
+
+When you use a scheduled trigger, the only available action is **Run script**. There's no work item event to react to, so the script handles the logic of fetching and modifying work items itself.
+
+## Add conditions
+
+Conditions filter which work items an automation acts on. Without them, the automation runs on every work item that matches the trigger.
+
+1. Open the automation and go to the **Trigger** tab.
+2. Scroll to **Conditions** and click **Add condition**.
+3. Choose a field (Priority, State, Assignees, Labels, Work Item Type, or Created By).
+4. Choose an operator (is, in, contains, etc.) and set the value.
+5. Add more conditions as needed.
+
+Multiple conditions use **AND** logic by default — all of them must match. You can also create **OR** groups where only one condition in the group needs to match.
+
+## Add actions
+
+1. Open the automation and go to the **Action** tab.
+2. Click **Add action** and choose a type:
+ - **Change property** — update a field on the work item
+ - **Add comment** — post a comment on the work item
+ - **Run script** — execute a saved script via the Runner
+3. Configure the action details (see [Actions](#actions) for parameters).
+4. Add more actions if needed. They run in the order listed.
+
## Manage automations
-
+### Enable or disable an automation
+
+- **Enable**: open the automation and click **Enable**. The automation must have at least one trigger and one action.
+- **Disable**: open the automation and click **Disable** or toggle the status off.
+
+You can't delete an enabled automation — disable it first.
+
+### Check automation run history
+
+Open any automation and click the **Activity** button on the top right. You'll see every run, the work items it acted on, whether the run succeeded or failed, and the full execution log.
+
+## Reference
+
+### Triggers
+
+| Trigger | Fires when |
+| ----------------- | --------------------------------------------- |
+| Work item created | A work item is created |
+| Work item updated | Any field on a work item changes |
+| State changed | A work item's state changes |
+| Assignee changed | An assignee is added or removed |
+| Comment added | A comment is added to a work item |
+| Scheduled | A configured time or cron schedule is reached |
+
+#### Scheduled trigger options
+
+| Option | Notes |
+| -------- | ------------------------------------------------------------------- |
+| Daily | Runs once a day at the time you set |
+| Weekly | Runs on the days of the week you pick, at the time you set |
+| Monthly | Runs on the day of the month you pick (1–31), at the time you set |
+| Cron | Enter a 5-field cron expression for custom schedules |
+| Time | Hour and minute (0–23 and 0–59) |
+| Timezone | Defaults to the project timezone, then workspace timezone, then UTC |
+
+### Conditions
+
+Conditions let you filter which work items an automation acts on. You can combine multiple conditions with AND or OR logic.
-### Activity monitoring
+#### Fields you can filter on
-Track your automation's performance through the Activity panel, which shows:
+| Field | What it checks |
+| -------------- | ---------------------------------- |
+| State | The work item's current state |
+| Priority | Urgent, High, Medium, Low, or None |
+| Assignees | Who the work item is assigned to |
+| Labels | Labels applied to the work item |
+| Work item type | The type set on the work item |
+| Created by | Who created the work item |
-- When the automation was created
-- Trigger additions and modifications
-- Condition updates
-- Action changes
-- Execution history
+#### Operators
-Filter the activity view to see only relevant events or view the complete run history to understand your automation's impact.
+| Operator | Use when |
+| ------------------------ | ----------------------------------------------- |
+| Is | The field exactly matches a specific value |
+| Is not | The field does not match a specific value |
+| In | The field matches any value in a set |
+| Contains | The field includes the value |
+| Greater than | The field is greater than the value |
+| Greater than or equal to | The field is greater than or equal to the value |
+| Less than | The field is less than the value |
+| Less than or equal to | The field is less than or equal to the value |
-### Enable or disable automations
+### Actions
-Toggle automations on or off as needed without deleting them. This is useful for:
+#### Change property
-- Temporarily suspending automations during maintenance
-- Testing new workflows before full deployment
-- Seasonal or project-phase-specific automations
+Updates a field on the work item.
-### Edit and delete automations
+| Property | What you can do |
+| ---------- | ---------------------------------------------------------------------- |
+| Priority | Set, add, or remove a priority level (Urgent, High, Medium, Low, None) |
+| State | Move the work item to a specific state |
+| Assignees | Add or remove assignees |
+| Labels | Add, remove, or replace all labels |
+| Start date | Set, update, or remove the start date |
+| Due date | Set, update, or remove the due date |
-- Modify triggers, conditions, and actions using the **Edit** option
-- Remove automations that are no longer needed
+#### Add comment
+
+Posts a comment on the work item. You write the comment text in a rich text editor. The comment is always internal and appears as coming from Automation Bot in the activity log.
+
+You can include dynamic values in the comment using template variables — for example, inserting the current priority or state name into the comment text.
+
+**Example:** Say you have an automation that triggers when a work item's state changes. You want to leave a note with context each time that happens. Your comment template might look like:
+
+```
+This item has been moved to a new state. Current priority: {{priority}}. Please check if the due date needs updating.
+```
+
+#### Run script
+
+Runs a saved script from your [Plane Runner](/automations/plane-runner) library. You pick the script from a dropdown. This is the only action available when using a scheduled trigger.
+
+## How custom automations work
+
+### How automations run
+
+Every time something changes in Plane — a work item is created, a state changes, a comment is posted — Plane checks whether any of your enabled automations should respond. If a trigger matches, Plane evaluates any conditions you've set. If those pass, it runs the actions in order.
+
+That's the whole flow: something happens → conditions are checked → actions run. If a condition doesn't match, nothing happens and the automation sits quietly. If an action runs into a problem, Plane stops there and marks that run as failed — you can see exactly what happened in the Activity tab.
+
+Each event is only processed once per automation, so you won't end up with the same action firing twice on the same work item.
+
+### Project automations vs. workspace automations
+
+The distinction comes down to scope and reuse.
+
+**Project automations** are the right choice when the rule is specific to one project. They're simpler to configure — the states, labels, and members you pick from are all scoped to that project.
+
+**Workspace automations** are the right choice when you want the same behavior across multiple projects. Instead of recreating the same automation in five different places, you define it once and choose which projects it applies to — all of them, or just a specific subset.
+
+Either way, automations always act on individual work items. Workspace automations aren't doing anything different — they're just defined once and applied more broadly.
+
+### Automation bot
+
+Every custom automation acts through its own dedicated bot account. When an automation changes a field or posts a comment, the activity log shows it came from "Automation Bot" — not from any person on your team.
+
+There are two reasons this matters:
+
+**You always know what made a change.** If a work item's priority changed unexpectedly, one glance at the activity log tells you whether it was a person or an automation. No guessing.
+
+**Automations don't trigger themselves.** Plane knows when a change originates from an automation, so it doesn't feed that change back in as a new event. A "state changed" automation that updates a state won't keep firing on its own output.
+
+### Why scheduled automations only run scripts
+
+Most automations respond to something happening — a trigger gives them a specific work item to act on. Scheduled automations are different. They fire at a time you set, not because of any particular event.
+
+Since there's no work item that kicked off the run, Plane has nothing to apply a property change or comment to. That's why the only available action for scheduled automations is Run script. The script defines the logic — what to look for, which items to act on, and what to do with them.
+
+Scheduled automations check whether they're due roughly every 5 minutes. The time you configure follows your project's timezone, falling back to the workspace timezone, then UTC.
+
+### Why your trigger isn't enough on its own
+
+Triggers tell Plane _what type of event_ to watch for — not which work items to care about. A "state changed" trigger fires for every single state change in the project, across every work item, regardless of type, priority, or who it's assigned to.
+
+Without conditions, an action like "set priority to Urgent" would run on every state change in the project. That's almost never what you want.
+
+Conditions are what make an automation surgical. They let you say "only run this when the work item is a Bug, assigned to this person, with no due date set" — whatever combination of criteria actually defines the case you're building for.
+
+One thing worth knowing: when a work item is first created, some fields like assignees and labels can take a moment to register, even if someone filled them in during creation. Plane handles this — it checks the latest state of those fields before evaluating your conditions, so a filter like "assignee is X" on a creation trigger will work as expected.
## Common use cases
-**State management.** Automatically transition work items between workflow states when conditions are met — for example, move a work item to "In Review" when an assignee is added, or to "Done" when all sub-items are completed.
+Some common things people use automations for.
-**Team assignment and handoffs.** Auto-assign team members when work items reach specific stages. Reassign work based on type or priority to ensure proper handoffs between teams.
+- **State management.** Automatically move work items through your workflow when something changes — for example, transition a work item to "In Review" when an assignee is added, or back to "Backlog" when an assignee is removed.
-**Priority and categorization.** Auto-adjust priorities based on labels or assignees. Apply consistent labeling across similar work item types to keep projects organized.
+- **Triage and routing.** Make sure new work lands in the right place without manual intervention — for example, assign a default owner whenever a specific work item type is created, or apply a label to every incoming bug so nothing slips through untagged.
-**Communication.** Post automatic comments when work items are assigned, reassigned, or move between stages. This keeps stakeholders informed without requiring manual updates.
+- **Priority escalation.** React to signals that indicate urgency — for example, automatically mark a work item as Urgent when a specific label is applied, or raise priority when it gets reassigned to a senior team member.
----
+- **Contextual reminders.** Surface the right information at the right moment — for example, post an internal comment with a checklist when a work item enters "Ready for QA," or flag missing information when a work item is created without an assignee.
-Automations transform reactive project management into proactive workflow orchestration, allowing teams to focus on solving problems rather than managing processes. With the ability to monitor, edit, and control when automations run, you maintain full control over your automated workflows while reducing manual overhead.
+- **Scheduled operations.** Run scripts on a timer to handle things that don't map to a single event — for example, sweep stale items weekly, sync data to an external tool nightly, or generate a status comment on open items every Monday morning.
diff --git a/docs/automations/overview.md b/docs/automations/overview.md
index d60e380..359d5c9 100644
--- a/docs/automations/overview.md
+++ b/docs/automations/overview.md
@@ -5,17 +5,21 @@ description: Automate repetitive project tasks in Plane.
# Automations
-Automations handle repetitive project work so your team can focus on the work that matters. Plane offers two kinds of automations, both configured in **Project Settings → Automations**.
+Automations handle repetitive project work so your team can focus on the work that matters. Instead of manually closing stale issues, archiving completed work, or nudging assignees about deadlines, you set up rules once and let Plane run them.
-- **Built-in automations** are ready-to-use toggles for common housekeeping tasks — archiving closed work items, closing stale ones, and sending deadline reminders.
+There are two kinds of automations:
-- **[Custom automations](/automations/custom-automations)** let you build your own trigger-condition-action workflows — like auto-assigning a reviewer when a work item moves to QA, or adding a label when priority changes.
+**Default automations** come built into every project. They cover the most common housekeeping tasks — archiving completed work items, closing stale ones, and sending due date reminders — and you configure them with a single time-based setting.
+
+**Custom automations** are rules you build yourself. You choose a trigger, optionally add conditions to narrow scope, then define what happens. They run at either the project level or the workspace level. See [Custom automations](/automations/custom-automations).
-## Auto-archive closed work items
+## Set up default automations
+
+### Auto-archive completed work items
-Automatically archive work items that have been completed or cancelled, keeping your active views clean.
+Auto-archive moves work items that have been sitting in a completed or cancelled state into an archived state.
1. Navigate to **Project Settings → Automations**.
2. Toggle on **Auto-archive closed work items**.
@@ -23,23 +27,27 @@ Automatically archive work items that have been completed or cancelled, keeping
Once enabled, work items that have been in a completed or cancelled state for longer than the configured duration are archived automatically. Archived work items remain searchable and accessible in the project's archived view, but they no longer appear in active lists, boards, or spreadsheets.
-## Auto-close work items
+:::info
+Work items in active cycles or modules won't be archived even if they've been completed for longer than your threshold.
+:::
+
+### Auto-close stale work items
-Automatically close work items that have been inactive — not completed or cancelled — after a period you define. This prevents stale work items from cluttering your project indefinitely.
+Auto-close moves unfinished work items — those in Backlog, Unstarted, or Started states — to a closed/cancelled state after a period of inactivity. This prevents stale work items from cluttering your project indefinitely.
1. Navigate to **Project Settings → Automations**.
2. Toggle on **Auto-close work items**.
3. Set the **Auto-close work items that are inactive for** duration — for example, 1 month.
4. Choose the **Auto-close status** — the state that inactive work items will be moved to (e.g., Cancelled).
-Work items that haven't been updated within the configured period are automatically moved to the selected auto-close status. Only work items that are not already in a completed or cancelled state are affected.
+### Set up due date reminders
-## Auto-reminders
-
-Send automatic reminders via email and in-app notifications to keep your team on track with deadlines. When a work item's due date is approaching, assignees receive a reminder so nothing slips through the cracks.
+Plane sends in-app and email notifications to assignees and subscribers when a work item's due date is approaching.
1. Navigate to **Project Settings → Automations**.
2. Toggle on **Auto-reminders**.
3. Set the **Send reminder before** timing — for example, 3 days before the due date.
-Once enabled, assignees and work item subscribers receive both an email and an in-app notification at the configured interval before each work item's due date. Only work items with a due date and at least one assignee or subscriber trigger reminders.
+Only work items with a due date and at least one assignee or subscriber trigger reminders.
+
+Plane sends one reminder per window — not a daily flood. If you've set a 3-day reminder and the due date is 3 days away, each person gets one notification.