monday.com Work Management Advanced key terms

A container that holds items organized into groups, with columns defining the fields each item can store. Boards are the fundamental unit of data and work in monday.com.

A single row on a board representing one unit of work, such as a task, project, or deal. Each item carries a name, column values, updates, and files.

A nested record under a parent item that has its own columns, updates, and files. Subitems go only one level deep and are stored on a separate hidden board.

A named, color-coded section of a board that clusters related items, often by phase, owner, or status. Groups can be collapsed and are referenced by many automation actions.

A typed field applied to every item on a board, such as status, date, people, numbers, formula, connect boards, or mirror. Columns define what data the board can hold.

A column of colored labels such as 'Working on it' or 'Done' that represents an item's stage. Status labels drive automations, filters, dashboards, and board-level reporting.

Assigns one or more account members to an item, powering personal views, notifications, and workload analysis. Changing an assignee can also trigger automations and update dashboards.

A relational column that links an item to one or more items on another board. It underpins roll-ups, cross-board automations, and mirrored values.

Displays a value pulled from a connected item on another board, such as its status or due date. Mirrored values are read-only and refresh when the source item changes.

An alternative presentation of the same board data, such as Main Table, Kanban, Calendar, Timeline, Gantt, or Chart. Views change how data looks, not what is stored.

Settings that control whether users can edit board structure, edit items only, or view without changes. They can be granted to users, teams, or the whole account.

A rule composed of a trigger and one or more actions that runs when a board event occurs. Automations remove repetitive manual updates and enforce process consistency.

A prebuilt automation template phrased as 'when this happens, do that'. Users select a recipe and choose the board, group, column, or person it should target.

The event that starts an automation, such as an item being created, a status changing, or a date arriving. Every automation has exactly one trigger.

The operation an automation performs after its trigger fires, such as changing a status, notifying a person, creating an item, or sending a webhook. Actions run in order.

An optional 'only if' filter inside an automation that must be true before actions run, for example only when priority is high. Conditions narrow when a recipe applies.

An automation assembled in the custom builder that combines a trigger, optional conditions, and several actions. It covers logic that a single prebuilt recipe cannot express.

A plan-based monthly allowance of automation executions for an account or board. When it is exhausted, automations pause until the period resets or the plan is upgraded.

A connection between monday.com and an external system such as Slack, Gmail, Teams, Jira, or Zapier, allowing events and data to flow without manual copying.

An outbound HTTP request that sends board or item event data to an external URL as JSON. Webhooks let custom services react to monday.com changes in real time.

A shareable canvas that pulls data from one or more boards into widgets for visualization and monitoring. Dashboards store no data of their own; they read it live.

A configurable element on a dashboard, such as a chart, table, number, calendar, or battery, that displays board data. Each widget has its own source boards and settings.

A widget that visualizes board data as a bar, pie, line, stacked, or battery chart, usually grouping items by a status or dropdown column. Widget filters decide which items count.

A global filter applied to every widget on a dashboard, restricting data by date range, person, status, or other column values. It lets one dashboard serve several audiences.

The aggregate shown beneath a column in the main table, such as count, sum, average, or percent empty. Summaries support number widgets and quick board health checks.

An automated delivery of board or dashboard data at a set interval, such as a weekly PDF or Excel export by email. It keeps stakeholders informed without logging in.

The top-level monday.com instance for an organization, containing users, workspaces, boards, and billing details. It is identified by a unique subdomain.

A container inside an account that groups folders and boards and scopes membership and permissions. Workspaces separate departments, regions, or clients from one another.

A user role with account-wide authority over people, billing, security settings, and permissions. Admins can view and manage content across every workspace.

An external collaborator whose access is limited to the specific boards they were invited to. Guests cannot browse the account directory or see unrelated workspaces.

A named group of users that can be granted board or workspace access, mentioned in automations, and used to organize people. Teams make permissions manageable at scale.

Single sign-on through SAML that authenticates users with the organization's identity provider instead of separate monday.com passwords. It centralizes access control and is offered on enterprise-level plans.

A chronological record of account events such as logins, permission changes, board deletions, and user management actions. It supports compliance reviews and security investigations.

Disabling a user's login while preserving the items, updates, and files they created. Deactivation frees a paid seat without deleting their historical work.

The nesting of account, workspace, folder, board, group, item, and subitem. Knowing it determines where data lives and where permissions and automations apply.

A container inside a workspace that groups related boards and dashboards, often by project, client, or team. Folders improve navigation and inherit workspace permissions.

Aggregating data from many team boards into a single portfolio board or dashboard, typically using Connect Boards and Mirror columns or a dashboard with multiple sources.

The practice of sharing templates, naming conventions, and admin-owned master boards so many teams work consistently and their data can be rolled up reliably.

Subscription-tier caps on items per board, boards per account, automation runs, and dashboard widgets. They influence how work is split across boards and workspaces.

A prebuilt solution for a common workflow, such as CRM, campaign management, or onboarding, that installs boards, automations, and dashboards ready to customize.