> ## Documentation Index
> Fetch the complete documentation index at: https://docs.audimate.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Task boards
> Track repeatable work as cards, hand tasks off to agents, and edit everything in a spreadsheet grid when you need to.
A task board is a shared board your team and its agents work through together, closer to Asana than
to a spreadsheet. Each card is one task, one customer to onboard or one claim to file, and a
[workflow](/concepts/workflows) runs against it.
## When to use a task board
Use a task board when the same procedure runs again for each case. Each task carries what that run
needs and what it produced. Its fields hold the values that change per case, and the list it sits in
says where it has got to.
A task board is not a data table. It is not the place for reference data like lookups, SKUs, or region
codes. If a card is not something that gets done, it does not belong on a task board.
## Where to find it
Open any task board file from **Team Library**, **Private**, or a **team space** in the sidebar.
You can also create one from a
workflow's **Data** tab to link it to that workflow.
Choose **New task board**, enter its name, and click **Create task board**. See [Creating files](/concepts/libraries#creating-files) for where new files are saved.
A blank task board starts without tasks. It includes **Title**, **Description**, **Stage**, **Assignee**, **Due date**, **Priority**, **Tags**, **Attachments**, and **Checklist**. Audimate opens the [intake form builder](#the-intake-form) on arrival,
so your first step is shaping what the task board asks for.
## Field types
| Group | Types |
| ------------ | --------------------------------------------------------------- |
| Basic | Text, long text, number, checkbox, URL, email, phone, checklist |
| Formatted | Currency, percent, date, single-select, tags |
| System | Auto-number, created at, updated at, created by |
| Relationship | Linked task, attachment, assignee |
| Special | [Stage](#stage), [Priority](#priority), Workflow |
Audimate uses the type to render the right editor and validate values. The three special types carry
behaviour the others do not, covered below.
### Stage
A task board carries one **Stage** field, added when the task board is created. Its options **are**
the task board's lists. It cannot be duplicated, deleted, or changed to another type.
**Which list a task is in IS its status.** There is no separate done or failed flag to keep in step
with it: a finished task is a task in the Done list, and moving a card is how its status changes,
whoever moves it.
A new task board starts with four lists, **Pending**, **In progress**, **Done**, and **Failed**, but
they are yours to rename, recolor, reorder, add, and delete. Renaming never loses the tasks in a
list. A task with no stage sits in the [Inbox](#the-inbox) instead.
On a plan that includes agent runs, those four lists carry the four **agent roles**.
| Role | What it is for |
| ------------------------------------- | -------------------------------------------- |
| Pick up from (**Pending**, at first) | Where agents take work from |
| Work in (**In progress**, at first) | Where a task sits while an agent runs it |
| File done in (**Done**, at first) | Where an agent files work it finished |
| File failed in (**Failed**, at first) | Where an agent files work that could not run |
Open **Settings** in the toolbar, choose the **Agents** tab, and pick all four. Agents need every
one, so nothing is saved until each is answered. **Disconnect all** clears all four
and turns it into a plain task board agents never touch. A list holding a role cannot be deleted
until the roles are moved or cleared.
Every new task board arrives with all four already assigned, on every plan. Nothing is picked up
until the workspace is on a plan that runs agents.
Because an agent can tell which tasks are untouched and take one, several agents run at once without
two picking up the same task. A single-select field gives no such guarantee, so use Stage for the
work itself, **Priority** for urgency, and single-select for ordinary fixed choices.
### Done and failed
A task is done when it is in the Done list, and failed when it is in the Failed list. Nothing else
records it, so there is nothing that can disagree with what you see.
You move a card by dragging it, or by changing its **Stage** field. An agent that finishes its task
files it into the list you picked for that role, which is the same move by a different hand. A card
in the Failed list carries a short reason. Open the task to read the full reason, then move it back to **Pending** to retry.
Because the list is the status, putting a card back in the pick-up list is all it takes to have the
work done again. That also resets its retry budget and clears the failure line.
### Starting agents
The roles say **where** agents take work from and file it. What starts them is always something a
person did, because whoever hands a task off supplies the computer it runs on and the identity it
runs as. There is no task board setting that picks a machine, and no way to start work on someone
else's behalf.
Under **Settings → Agents**, pick which workflow the task board runs and set **Start cards
automatically**. The tab's own switch, **Run agents on this task board**, turns it back into an
ordinary kanban board when off. Your lists and workflow settings are kept and stay editable.
With **Start cards automatically** on, a card that lands in the pick-up list starts right away, on
the device of whoever put it there, as them.
| What you do | Does it start the card? |
| ---------------------------------------------- | ------------------------ |
| Drag a card into the pick-up list | Yes |
| Type a new card straight into the pick-up list | Yes |
| Change a card's **Stage** field to that list | No, it files it |
| Reposition a card already in that list | No |
| An agent or integration creates the card | No, nobody handed it off |
With the setting off, the pick-up list is a **staging area** and cards wait until somebody hands
them off. Open the list menu to see whether new arrivals start automatically or wait for you to start an agent.
Auto-run applies to cards added from the moment you switch it on. Cards already waiting are not
picked up on their own, so turning it on asks whether to start them too and says how many there are.
Say no and the pick-up list keeps a **Start them** link while those cards wait.
A run happens on the starter's own computer, so auto-run needs the desktop app open there. A card
added from your browser, or with the app closed, waits in the pick-up list. When a task has been handed off, open it to see who started the agent.
Two other ways to start work exist, neither of them task board settings:
* **A personal schedule.** Point one of your own [scheduled tasks](/concepts/scheduled-tasks) at the
workflow this task board is bound to. Schedules belong to the person who created them and run on their
computer, so several people can each aim one at the same task board and share the work.
* **Run agent.** Use a card's `...` menu and choose **Run agent on this task**, or select rows in
Table view and choose **Run**. The card moves to the top of the pick-up list and starts on your computer,
as you. Both need edit access and appear only in the desktop app.
A card that is not ready is not started. Audimate names what is missing: a required field left
empty, the workflow the card has not chosen on a task board running several, or an app the workflow needs
that you have not connected. Run a selection and the ready ones still start, with the message
counting the ones that did not.
One run starts at most **1,000** waiting tasks. A deeper backlog is refused whole, with nothing started and the number
reported back.
### The task board needs a workflow
Until a workflow is connected, cards in the pick-up list have nothing to run and stay put. Connect one
under **Settings → Agents**.
Building a task board and wiring it up is free on every plan. Free includes 3 workflow runs, so
agents can work a few cards before you pay. Each card an agent picks up counts as one run. Paid
plans remove that limit, and the tab says where you stand. The list offers workflows you can edit, because
connecting one shares it with everyone who can see the task board. Audimate asks you to confirm that
first: editors can edit it, viewers can view it, and the workflow's own collaborators get matching
access to the task board. **New workflow** creates and connects one in the same step, inheriting the
task board's sharing.
Each workflow in the list shows how many task boards it already runs on, against the number your plan
allows. A workflow at that number cannot take another task board. The limit belongs to the workflow, not
to the task board, so a task board can connect as many workflows as you like.
Once a task board is connected to any workflow, every card says which one runs it through the task
board's **Workflow** field. You never add that field yourself: it appears with the first connected
workflow and disappears when you disconnect the last one, so it cannot be renamed away, deleted, or
added by hand.
**None** is one of the choices, and it is not the same as leaving the question unanswered. A card set
to None is a general task: an agent still picks it up and works it, using the card's own fields as the
instructions, with no workflow and no playbook behind it. Cards that already existed when you connected
your first workflow are None, because nobody chose a workflow for them.
Open a card to see or change its **Workflow** field.
Disconnecting a workflow is confirmed too, because it is not the opposite of connecting. Cards that
name it stop starting until you point them somewhere else, and if you disconnect the last workflow the
**Workflow** field is removed along with what every card had chosen in it. The sharing that connecting
granted stays exactly as it is, and you change that from the workflow's own share dialog.
### Who is running a card
Open a card to see whose agent has reserved it: **Your agent**, or a
teammate's name. The reservation does not mean work has started. The card can still be waiting for a free
slot on their computer, since **Cards run at once** under
[Arro's settings](/concepts/desktop-app#arro) takes 1 to 4 and starts at 2. Nobody else's agent
takes a card that is already reserved.
A card can be reserved and still not moving. If the workspace is out of its monthly usage, or the
computer is already running as many tasks as it allows, the card keeps its reservation and tries
again a few minutes later. Waiting like this costs the card none of its three attempts.
A reservation is also what protects a running card: while a card is reserved, only the person who
reserved it can move it. Anyone else who tries is told the card is claimed, so a teammate cannot drag
work out from under an agent mid-run.
Filing a card releases it. A card that lands in **Done** or **Failed** loses its reservation automatically,
whether an agent filed it or you dragged it there yourself.
If a card is reserved by someone who is not coming back, open its `...` menu and choose **Clear
dispatcher**. It confirms, then releases the reservation. The card stays where it is and anyone can
start it again. Clearing never hands the card to someone else.
### Priority
The **Priority** field type carries a fixed four-level scale: **Low**, **Medium**, **High**, and
**Urgent**. The levels are built into the type, so every Priority field means the same thing, and
sorting by it orders tasks by urgency rather than alphabetically.
When a task board has a Priority field, agents take the most urgent waiting tasks **first**, and the
position you drag a card to breaks ties within the same priority. Without one, pickup order is the
order of the cards in the pick-up list.
## Board view and Table view
A task board opens in **Board** view, a column of lists with one card per task. Switch to **Table** view
with the toolbar toggle for the spreadsheet grid, which is better for editing many cells at once.
The choice is remembered per device for that task board. A workflow's **Data** tab opens on the task board
too, and its choice of view is per visit.
Switching back to Board view clears any sort and grouping you set in Table view, because a card's
position in a list is the pick-up order and a sort would disagree with it.
### Lists
Each list is one option of the [Stage field](#stage). Click a list's name, or use its `...` menu, to
rename it. The menu also recolors and deletes it, and **Add list** appends a new one. Drag a list by
its header to reorder. Deleting a list asks for confirmation and moves its cards to the Inbox.
A list agents use carries a robot badge in its header. Hover it to see which step of a run that list
is for. The four are set in **Settings**, under **Agents**.
The `...` menu also sorts a list by any field, except attachments, linked tasks, assignees, checklists, and Stage itself. A
sort changes only how the list is **displayed**, never the order agents pick tasks up in. To change
pickup order, drag cards, or set priorities on a task board with a [Priority field](#priority). A sorted
list shows a "Sorted by" note with a **Clear** link, and dropping a card in clears the sort.
### The Inbox
A task with no stage sits in the **Inbox**, always the first list and always shown, so there is a
consistent place to drop work for triage. The Inbox is outside the lists agents use and an agent never picks up
from it. Tasks imported from a spreadsheet land here, and dragging a card into the Inbox clears its
stage, pulling it out of the pick-up list without deleting it.
### Card actions
Hover a card for a `...` button, or right-click anywhere on it, for **Open task**, **Delete task**,
and the agent actions the card qualifies for. Deleting needs edit access, and without it **Delete
task** is greyed out rather than hidden. There is no confirmation: the task goes straight away, and
the message that follows carries an **Undo** button, as does [Ctrl+Z or ⌘+Z](#undo).
Grab a card anywhere to move it. Dropping it on a list sets that stage and its position in one step.
The last move wins, so dragging a card out of the working list overrides an agent running it right
now.
The toolbar's **Background** button sets the task board's canvas color. New task boards start on Lavender, and
**Plain** turns the wash off. It belongs to the task board, so everyone sees the same color.
### Stalled tasks and retries
An agent's claim on a task lasts **five minutes**, renewed for as long as a worker is genuinely
running. A claim that runs out means the app doing the work stopped, not that the work is slow. Two
thirds of the way through, the task shows an amber **Needs attention** indicator. When the claim runs out the
task returns to the pick-up list keeping its reservation, so the same person's agent picks it back up.
A card you drag into the working list yourself has no agent to renew its claim, so it is held about
**thirty minutes** rather than five before returning to the pick-up list.
An agent may start the same task **three** times. If the third attempt also stops, the task is
filed into the Failed list like any other, so a task that
reliably breaks whatever is working on it comes to rest somewhere visible. Putting it back in the
pick-up list with **Retry task** in the card menu, or by dragging it, gives it a fresh three. Retry counts as adding the card, so
on an auto-run task board from the desktop app it starts straight away.
A failed card shows a short failure message. Hover it or open the card to read it in full.
| Why a card failed | What to do |
| ----------------------------------------------------- | ---------------------------------- |
| It stopped three times | Fix the cause, then **Retry** |
| A **required** field is empty | Fill it in, then put the card back |
| No **Workflow** chosen on a multi-workflow task board | Choose one, then put the card back |
Audimate checks a card before starting it, so auto-run leaves an unready card alone and an explicit
**Run** is refused with a message. The last two reasons are the backstop for a card that got past
those checks, either because something changed after it was reserved or because it was handed off
through the API.
Missing [plugin prerequisites](/concepts/plugins#use-plugins-in-workflows) leave cards queued without marking them failed.
Install and enable the named plugin, then connect or reconnect its app in your current workspace.
Each runner uses their own plugin settings and accounts. Your agents identify the missing setup without changing the card.
A refusal like this costs none of the card's three attempts.
Dropping an unfinished card into the pick-up list does not fail it either. It stays where you put it,
unstarted, with no badge. To hear what it needs, use **Run agent on this task** and read the refusal.
## The intake form
**New task** opens the task board's intake form, so whoever adds work is asked for exactly the fields
that task board needs. Choose its destination with **Stage**. A list's **+ Add task** preselects that list; the toolbar starts with **Inbox**.
The title and description span the form. Shorter controls share a row when space allows; an unpaired control fills the row.
Descriptions use a larger plain text box. **Create another task** keeps the form open and retains your chosen list after creation.
**Customize form** opens the builder, where you set the heading, blurb, and submit button label, add
or remove fields, drag them into order, and toggle each field's **Required**, **On form**, and **On
card**. The trash icon removes a field, the pencil opens the field editor, and the key icon makes a
field the task board's title. Adding, editing, or removing a field saves immediately, while the heading,
blurb, submit label, toggles, and order apply when you press **Save**. Editing the form needs edit
access.
Each list also has a **+ Add task** composer that captures a title only and reopens after every
Enter, for typing several in a row. If the form has any other required field, that button opens the
full form instead, so structure you asked for cannot be skipped.
## Fields
Use the **+** at the right of the field headers to add a field, then configure its type-specific
options. Drag a field header to reorder. Click the chevron on a header, or right-click it, for
**Edit field**, **Duplicate field**, **Insert left**, **Insert right**, **Sort A to Z**, **Sort Z to
A**, **Set as primary field**, **Hide field**, and **Delete field**.
A task board supports one each of **Assignee**, **Priority**, **Stage**, and **Workflow**.
Unavailable types appear at the bottom of the type picker. Hover a greyed-out choice to see why it is unavailable.
Click a header to select a field, and Ctrl-click or Shift-click for several. Right-click a selected
header to act on all of them, for example **Delete 3 fields**.
Three fields cannot be deleted, and **Delete field** is absent for them:
* The **primary field**, which stays fixed at the left while the rest scroll sideways.
* The [Stage field](#stage), whose options are the task board's lists.
* The **Workflow** field, which Audimate adds and removes for you.
### How a field behaves on the intake form
The field editor carries three settings under **On the task form**.
| Setting | What it does |
| --------------- | ---------------------------------------------------------- |
| **Required** | A task cannot be added from the form until it is filled in |
| **Help text** | An explanatory line shown under the input |
| **Placeholder** | An example value, offered for free-text types only |
Placeholder is offered for text, long text, number, currency, percent, URL, email, and phone,
because a checkbox or a dropdown has no empty state to hint into.
A field looks on the form the way it looks in the table. A currency input carries its symbol, a
percent input carries its **%** and its progress bar, and URL, email, and phone inputs carry a
button that opens the link, the mail app, or the dialer once what you typed is valid.
**Required** can also be toggled in the intake form builder, alongside **On form** and **On card**.
The title field is always on the form and always required. Stage appears as a list picker, including the Inbox.
Linked tasks and system fields never appear on the form, and the editor hides these settings for them.
The **Workflow** field is a special case: you neither add it to the form nor take it off. It appears
on the task board, and on the form, once the task board is connected to
[any workflow](#the-task-board-needs-a-workflow). It is required there, which means you have to make a
choice rather than that you have to pick a workflow. **None** is a choice, and choosing it deliberately
is the point.
### Due dates
A task board can designate one **date** field as its due date. Every new task board opens with its **Due
date** field already designated and set to show on cards.
The designation is a setting, never a guess from the column's name: a field called **Due date** on a
task board Arro builds for you is an ordinary date field until you say otherwise. Only the blank task board scaffold designates
one for you.
To set or move it, open **Settings** in the toolbar and choose the **Task board** tab. A task board
has one due date field, so picking another replaces the current one, and changing that field's type
gives the designation up.
Dates appear beside a calendar icon in the card footer, such as Apr 12. Hover or focus a date for its full date and due status.
Untick **Show on card** to hide it. Other visible date fields use the same compact style.
### Card appearance
Descriptions appear on new cards by default and truncate after 2 lines. Tags and priority appear as coloured pills below the description.
Visible fields show their values without labels. The footer groups the assignee, dates, and checklist progress.
Use a list's **Appearance** menu to choose its icon and colour, including the Inbox.
The **Stage** selector in task forms and the **Agent lists** selectors in Settings show the same icon. Only the icon uses the list colour; the text and control stay neutral.
The agent icon appears when you hover an enabled agent list. Agent information also remains available in the list menu.
Choose **Background** in the toolbar for 4 illustrated backgrounds, a colour, or **Plain**. The choice is shared across the task board.
### Assign tasks and track steps
Choose **Assignee** in the task form or click a card's avatar to assign one current workspace member. Choose **Unassigned** to clear it. In Table view, assignees appear as avatars. Double-click the cell to search for and choose a workspace member.
Assignment records responsibility; it does not start an agent or change whose computer runs the task.
In Table view, checklist cells show a progress bar and completed-item count. Finished checklists turn green with a checkmark. Double-click a checklist cell to open its checklist editor without opening the full task. A single click selects the cell.
Checklist additions, checkmarks, reordering, and removals save automatically. Text edits save when you leave the item or press Enter. **Saving...** appears beside the checklist name while changes are saved.
Completing every item does not move the task to Done.
If someone changes the task while you edit, your checklist remains available for review before you replace the latest version.
### Move several tasks
Select cards with their circles, or use Ctrl-click (Command-click on Mac). Shift-click selects a range in the visible board order.
Select up to 100 cards, then drag a selected card or use **Move to...**. **Clear** or Escape clears the selection.
If any selected task cannot move, the entire selection stays in place. Cards already in the destination queue are not restarted.
## Edit cells
Click any cell to edit. Audimate opens a type-specific editor: a date picker, a dropdown, a
rich-text panel, or a file upload. Press **Enter** to commit, **Escape** to cancel, or **Tab** to
move on. Changes save automatically and broadcast in real time.
Click a card, or the expand icon on a grid row, to open a task in a detail modal: the stage picker
up top (moving the task between lists is how you record what happened to it), then every field as
its own editable control. If the last run failed, the reason is shown in full beneath it. Use the
arrows in the top bar to step through tasks without closing the modal.
Select cells and use the **Color** button, or right-click and choose **Fill color**, to give them a
background. Colors save with the task board and sync live.
### Bulk paste
Copy a range from another spreadsheet and paste it in. Audimate detects the shape and prompts before
expanding the task board to fit. Cell background colors travel both ways, so fills survive a round trip
through Excel or Google Sheets.
If your paste has a **Stage** column naming the pick-up list, on a task board that
[starts waiting cards automatically](#starting-agents) you get a second prompt, because those tasks
would begin running on your computer the moment they land.
| Choice | What happens |
| -------------------------- | ------------------------------------------------------------------ |
| **Send them to the Inbox** | Everything imports with Stage empty. Nothing starts |
| **Import as is** | Tasks land in the pick-up list and start. You type `Confirm` first |
**Import as is** also starts anything already waiting in the pick-up list, and the prompt tells you the
total.
### Undo
Press **Ctrl+Z** (**⌘+Z** on a Mac) to undo cell edits, pastes, fill colors, and task or field
deletions while the task board is open. **Ctrl+Y** (**⌘+Shift+Z**) redoes. Deleting several fields
at once asks for confirmation first, since it removes their data from every task.
In Board view the only thing to undo is a deleted task, so undo works back through the ones
you deleted. Cell edits and pastes belong to Table view, and each view keeps its own history.
## Attachments
Attachment fields hold files. Add them from a cell, from the expanded task view, or from the intake
form, and drag files straight onto the field in the latter two. Each file uploads with its own
progress bar, and images show a clickable thumbnail.
Files are stored per task board rather than per task. The add dialog's **Task board files** tab lists
everything already uploaded, so attaching a file to a second task is a matter of ticking it. The
**Link (URL)** tab attaches a file that lives somewhere else.
| Limit | Value |
| --------- | -------------------------------------------- |
| File size | 100 MB per file |
| Storage | Set by your plan, across the whole workspace |
The file limit is the same on every plan, and a file over 100 MB is refused before it uploads. Storage
is the total size of every file attached to any task board in the workspace, and grows with each
seat. The figure for each plan is in [Plan limits](/account/plan-limits#workspace-capacity). Common
document, image, video, audio, archive, and data formats are accepted. Anything a browser would run
or render as a document is refused: executables, HTML, and SVG always, and XML whenever the browser
labels it as XML.
### Manage a task board's files
Task boards with an attachment field get an **Attachments** button in the toolbar, opening the task board's
file manager. Search the files, download one, or delete one permanently. Anyone who can see the
task board can browse and download, and uploading and deleting need edit access. The manager also shows
how much of the workspace's storage is used, warning at 75%.
Deleting a file in the manager removes it from storage and from every task that referenced it, and cannot be undone.
This is the only place storage is freed. Removing a file from a task with the **×** on its chip only detaches it, so
clearing cells reclaims no storage.
## Hide fields, filter, group, and sort
| Control | What it does | Where |
| --------------- | ------------------------------------------------------------- | ---------- |
| **Filter** | Builds conditions like "Amount greater than 1000" | Both views |
| **Hide fields** | Toggles fields on and off, and reorders them | Table view |
| **Group** | Groups tasks by a field, with a count per group | Table view |
| **Sort** | Orders every task on the task board, not only those on screen | Table view |
View controls only affect what you see. They do not modify the data, they reset when you reload, and
sorting and grouping reset when you switch to Board view. A hidden field stays active in any filter,
group, or sort that uses it.
## Working with other people
Task boards sync live across everyone with the task board open. You see remote cursors, a brief flash on a
cell someone is editing, and presence avatars for who else has it open.
Open [**Ask Arro**](/concepts/workspace-agent) from the sidebar and ask it to read or
edit a task board, which does not have to be open. It looks up fields, finds and reads tasks, adds,
updates, and deletes tasks, and adds, renames, or removes fields. Edits apply live with no separate
save step. Deleting tasks, removing a field, and any batch of more than five task changes
[ask first](/concepts/workspace-agent#approvals).
## Linked tasks
A linked-task field points to tasks on another task board. Click the cell to search and pick tasks to
link. Because every card on a task board is a piece of work, a linked task is how one points at another: a dependency,
or the task another was produced from.
## Making a shared task board private
Taking a Team Library task board back to Private, by removing all access entries from its share dialog,
shows the dependents that will be affected and asks you to confirm. It removes linked-task fields on
other task boards that point at this one, along with any links stored in them, and data source
attachments on workflows that referenced this task board. The removal happens in one step alongside the
visibility change, so there is no half-shared state to clean up. Playbooks may need updating to
point at a different data source.
Only the task board's owner can make it private. If that person later leaves the workspace the task board
stays theirs, waiting for them if they return and listed for an admin to claim if they do not. See
[Ownership](/concepts/workflows#ownership).
Private means **not shared**, not sealed. A private task board does not appear in anyone else's lists, search, or the
pickers Arro uses, including your admins and owner, because [roles](/account/organization#roles) govern the workspace
and not its files. An admin can still take ownership of any item, which is recorded in the [audit
log](/account/audit-log) and is never a way to browse.
## Plan limits
Task boards count against a per-member private cap and an organization-wide shared cap, exactly as
workflows do. See [Workflow and task board limits](/account/organization#workflow-and-task-board-limits) for
which action hits which cap and what happens when one is full.
Each task board also holds a limited number of **tasks**, which is per task board and does not grow with
seats. See [Plan limits](/account/plan-limits) for the per-plan figure.
Some limits are the same on every plan.
| Limit | Value |
| -------------------------------------------------- | ---------------------------------------------------------------------------- |
| Fields per task board | 30 |
| Lists per task board | 16 |
| Options on a select field, or tags on a tags field | 30 |
| Attachment file size | 100 MB |
| Attachment storage | Set by your plan, see [Plan limits](/account/plan-limits#workspace-capacity) |
## Related
The workflow a task board's agents run against each task.
Point a schedule at the workflow a task board is bound to.
Read and edit a task board from a plain-language request.