ClickUp Certification key terms

The top-level container that holds all Spaces, members, billing settings, and security policies for an organization using the platform; everything a team creates lives inside one.

The nested structure of Workspace, Space, Folder, List, and task that organizes work; permissions and views can be set at each level and inherited downward.

A major grouping inside a Workspace that usually maps to a team, department, or project area, and that carries its own members, statuses, ClickApps, and views.

An optional grouping layer inside a Space used to bundle related Lists, such as sprints or client projects, so views and settings can be shared across them.

The container that directly holds tasks; it defines the statuses tasks move through and is the level where most views, automations, and custom fields are configured.

The core unit of work, holding a name, description, assignees, status, dates, priority, tags, checklists, subtasks, and custom field values.

A child task nested under a parent task that tracks a smaller piece of work; it can have its own assignee, status, and due date, and rolls up to the parent.

A named stage a task passes through, grouped into open, custom, and closed types; the set of statuses is defined per List or inherited from the Space.

A user-defined data attribute added to tasks in a location, with a type such as text, number, dropdown, date, currency, or formula, used for filtering and reporting.

A saved way of displaying the same underlying tasks, such as List, Board, Calendar, Gantt, Table, or Timeline, with its own filters, sorting, and grouping.

A toggleable feature module enabled per Space or location, such as time tracking, custom fields, or dependencies, that adds capability without changing the core task model.

A rule built from a trigger, optional conditions, and one or more actions that runs without manual effort, for example changing status when a task is assigned.

The event that starts an automation, such as a task being created, a status changing, a custom field being edited, or a scheduled time arriving.

The built-in AI layer that answers questions about workspace content, summarizes tasks and documents, drafts text, and can take actions through connected AI agents.

A configurable autonomous assistant that watches for defined triggers and performs multi-step actions in the workspace, such as triaging requests or updating tasks.

A Brain feature that generates a written summary of what changed or progressed across selected tasks and Lists, reducing the need to gather updates manually.

A Brain capability that lets teams connect documents and sources so AI answers and agents can reference approved organizational knowledge rather than guessing.

The natural-language instruction a user gives to an AI feature; clear prompts naming the task, format, and constraints produce more reliable output.

The built-in messaging area for real-time conversation in channels and direct messages, with threads, mentions, reactions, and links to tasks and documents.

A named conversation space inside Chat, which can be public to the workspace or private to invited members, and can be organized around a team or project.

A reply chain attached to a specific chat message that keeps side discussion grouped so the main channel stays readable.

A typed reference such as an at-sign followed by a person, task, or document that notifies the person or creates a live link in chat and comments.

An outbound HTTP callback that sends event payloads to a URL you specify when something changes, letting external systems react without polling.

A personal or app credential sent in a request header to authenticate calls to the public API; it carries the permissions of the user or app that created it.

An authorization flow where a user grants an application scoped access without sharing a password, commonly used when distributing an app to other workspaces.

A cap on how many API requests may be made per minute or hour for a token or workspace; exceeding it returns an error and requires backoff and retry.

Model Context Protocol, an open standard that lets AI clients connect to external tool servers; the platform exposes an MCP server so assistants can read and act on workspace data.

A connection between the platform and another product, such as a calendar, code repository, or file storage service, that syncs data or triggers actions.

The phone and tablet client that supports tasks, notifications, chat, and quick capture, with some features adapted or limited compared with the desktop web app.

An alert about activity relevant to you, such as an assignment, mention, comment, or due date, delivered in-app, by email, or as a push message.

A rule controlling what a member or guest can view or change at a given location, ranging from full edit to view-only or comment-only access.

An external collaborator invited to specific locations rather than the whole Workspace, with limited visibility intended for clients or contractors.

A record of security-relevant activity in the Workspace, such as logins, permission changes, and exports, used for compliance review and incident investigation.

A login safeguard requiring a second proof of identity beyond a password, such as a one-time code from an authenticator app, before access is granted.

An identity setup where members authenticate through a central identity provider, so access is granted and revoked from one place rather than per-user passwords.

A page of widgets that visualizes task data, such as counts by status, workload, or time tracked, built from the same tasks shown in views.

A calculated custom field that derives its value from other fields or numbers on the task, useful for scores, budgets, and rollups in reporting.

A condition set that narrows which tasks appear in a view, for example by assignee, status, date range, tag, or custom field value.