ClickUp default task types control the task type selected when someone creates a new task. They are useful when a team wants new work to start with a predictable classification such as Bug, Request, Feature, Hiring Task, or Client Deliverable.
The setting can usually be applied at multiple levels of the ClickUp hierarchy: Workspace, Space, Folder, and List. A lower-level setting can override a broader one, so the most specific applicable default determines what a new task receives. This lets an organization keep a general standard while allowing a department or workflow to use a more appropriate type.
The important design question is not simply where to click. It is which business state the task type should represent, who owns the setting, and whether the resulting classification will improve filtering, handoffs, automation, or reporting. Configure the default only after that decision is clear.
What a default task type does in ClickUp
A custom task type adds a meaningful category to a ClickUp task. Instead of treating every item as a generic task, a team can distinguish between types such as Bug, Feature, Request, Candidate, Review, or Implementation Task.
The default task type is the type ClickUp selects automatically for new tasks created in a particular location. It does not necessarily prevent a user from changing the type later. Its main purpose is to make the most common or expected starting state easy to apply.
A default should represent the most likely business state for new work, not merely the type that is easiest for an administrator to choose.
For example, a List used exclusively for product bugs may reasonably default new tasks to Bug. A general project List containing several kinds of work may be better served by a broader type, with users selecting a more specific type when they create the task.
Where default task types can be configured
ClickUp uses a hierarchy in which Workspace settings can provide broad defaults and more specific locations can override them. The relevant levels are:
- Workspace: the broadest default for locations that do not define their own setting.
- Space: a department, function, or major operating area with a distinct way of classifying work.
- Folder: a project group or process area that needs a more specific default.
- List: the narrowest location, often representing one workflow, queue, or workstream.
Not every team needs an override at every level. A simple setup may use one Workspace default. A more mature setup may use a common Workspace standard, with carefully chosen Space or List overrides where the work genuinely differs.
Every override creates another rule to understand and maintain. Use a lower-level default only when it reflects a real difference in the work, not because the hierarchy makes it possible.
How inheritance determines the default
When a new task is created, ClickUp checks for the most specific default available in the task’s location. The practical order is:
- Use the List default if one is configured.
- If no List default exists, use the Folder default.
- If no Folder default exists, use the Space default.
- If no Space default exists, use the Workspace default.
This is an inheritance model. A child location inherits from its parent until it has its own value. The result is useful because administrators can set a broad baseline without configuring every List individually.
When troubleshooting an unexpected task type, start at the List and work upward. Check for a local override before assuming the Workspace setting is being ignored. Also check whether the task was created in the expected List, because the location where a task is created affects which default applies.
Use the Workspace or Space level
Choose this when several teams create the same general kind of work and should use a consistent classification for reporting.
Use the Folder or List level
Choose this when a defined project or queue has a different operating process and the narrower default will reduce manual selection.
How to set a Workspace default task type
Workspace-level configuration provides the fallback for locations without a more specific default. The exact navigation labels can vary with ClickUp’s interface, plan, and permission model, but the process is generally:
- Open the relevant Workspace settings.
- Find the area for Custom task types or task type management.
- Review the available task types and identify the type that should be selected for new tasks by default.
- Set that type as the Workspace default and save the change.
Afterward, Spaces, Folders, and Lists without their own default should inherit the Workspace setting. Before applying it, consider whether the default is meaningful across the entire Workspace. A type that makes sense for a support team may be misleading for finance, marketing, or software delivery.
How to set a Space default task type
A Space default is useful when a department or operating area has a consistent workflow that differs from the broader Workspace standard. For example, a recruiting Space may classify new work as Candidate Process, while a product Space may use Feature or Bug.
- Open the Space that needs a different default.
- Open its Space settings or configuration menu.
- Locate the Custom task types or Task types area.
- Select the type that should be used for new tasks in that Space.
- Save the setting and test it by creating a representative task.
Folders and Lists inside the Space should inherit the Space default unless they have their own overrides. If the result is not what you expect, inspect the child location for a previously configured default.
How to set a Folder default task type
Use a Folder-level default when a group of Lists shares a distinct workflow. This can be appropriate for a project portfolio, a delivery stage, or a set of queues that all classify new work in the same way.
- Open the target Folder.
- Open the Folder settings or configuration options.
- Find the Custom task types setting.
- Select the intended default type.
- Save the change and check one or more Lists within the Folder.
A Folder default affects Lists that do not have a List-level override. It should therefore be reviewed as a group rule, not as an isolated setting. If only one List needs the exception, configure the exception at the List level instead.
How to set a List default task type
A List is often the best level for a highly focused workflow. A List for incoming support requests, product defects, or contract reviews may have one obvious default that helps users create correctly classified tasks.
- Open the List where new tasks need a specific type.
- Open the List settings or configuration menu.
- Locate the Custom task types or related task type option.
- Choose the default type for that List.
- Save the change and create a test task to confirm the behavior.
A List-level default takes precedence over Folder, Space, and Workspace defaults. Because it is the most specific rule, it should be used deliberately. Too many List-level exceptions can make the Workspace difficult to explain and can weaken the consistency that defaults are intended to create.
Design task types around business states
Task types work best when they answer a classification question that matters to the operation. They can help distinguish the nature of work, the queue it belongs to, or the reporting category it should enter. They should not duplicate every status, assignee, priority, or activity.
For example, Bug and Feature may describe the nature of product work, while statuses such as Open, In Progress, and Done describe progress. A task type should not be used as a substitute for a workflow status when the team needs to know how far the work has progressed.
A task type should answer “what kind of work is this?” rather than “what happened most recently?”
Before creating or changing a type, ask three diagnostic questions:
- Will a user make a different decision because this type is known?
- Will the type support a filter, handoff, automation, or report that the team actually uses?
- Can a new team member identify the type without needing a long explanation?
If the answer to each question is no, the type may be adding vocabulary without adding operational value.
Use default task types without creating data problems
Defaults improve consistency at the point of creation, but they do not correct poor task design. A default can still be wrong when tasks are created in the wrong List, when the workflow includes several equally common work types, or when users routinely change it after creation.
Use the following operating sequence:
This sequence keeps configuration tied to an operational outcome. If a type does not affect a decision, it may not need to exist.
Example: a recruiting workflow with different defaults
Consider a hypothetical recruiting Workspace. The Workspace default might be a general Recruiting Task because several teams use ClickUp. A hiring Space could override it with Candidate Task. Within that Space, a Folder for interview coordination could use Interview Task, while a List for hiring manager requests could use Hiring Request.
This structure is sensible only if those categories lead to different ownership, fields, views, or handoffs. If every team treats all of them identically, the additional types create maintenance without improving visibility. The decision should be based on the work that follows task creation, not on how detailed the hierarchy can become.
For a real ClickUp implementation, document who can change defaults, which locations have overrides, and what each type means. This makes future troubleshooting easier and prevents local configuration from becoming invisible process logic. ConsultEvo’s ClickUp consulting service covers workspace architecture, workflow design, dashboards, automation, and integrations when the task structure needs to support a wider operating model.
Review permissions, ownership, and reporting
The ability to manage a default depends on the user’s role, permissions, Workspace configuration, and potentially the ClickUp plan. If an expected setting is unavailable, ask a Workspace owner or administrator to check access and the current ClickUp interface rather than assuming the feature is missing.
Ownership should also be explicit. A Workspace owner may govern global task types, while an operations or department owner may be responsible for Space and List exceptions. Without an owner, defaults tend to accumulate, remain after a process changes, and produce inconsistent reports.
- Each type has a clear definition and does not duplicate a status or priority.
- Every default has an identified owner.
- Overrides exist only where the work genuinely differs.
- New tasks receive the expected type at each relevant hierarchy level.
- Reports, views, handoffs, or automations use the classification for a defined purpose.
- Old types and unnecessary overrides are removed when the workflow changes.
Task types are most valuable when they improve a decision. If the team cannot explain what action a type enables, simplify the model before adding more configuration. Broader systems work may also require aligning ClickUp with CRM, automation, or reporting processes. In that situation, a systems and automation implementation service can help connect the task model to the wider operating process.
Key principles for ClickUp default task types
Default task types are a small configuration choice with wider consequences for data quality. A broad default provides a consistent baseline. A carefully chosen override reflects a real difference in the work. A poorly designed hierarchy creates hidden rules that users and reports must work around.
Set the default where the business rule is true, give the rule an owner, test inheritance, and connect the classification to a real operational use. The goal is not to create the most detailed ClickUp taxonomy. The goal is to make task creation, handoffs, and reporting more reliable.
Frequently asked questions
What are default task types in ClickUp?
A default task type is the custom task type ClickUp selects automatically when a new task is created in a particular location. It provides a consistent starting classification for work.
Can ClickUp default task types be set at different levels?
Yes. Defaults can generally be configured at Workspace, Space, Folder, and List levels. A more specific setting can override a default inherited from a higher level.
Which ClickUp default task type takes priority?
The most specific applicable setting takes priority. A List default overrides a Folder default, a Folder default overrides a Space default, and a Space default overrides a Workspace default.
Why is a new ClickUp task using the wrong default type?
Check where the task was created and inspect the hierarchy from List upward. A local List, Folder, or Space override may be taking precedence over the Workspace default.
How should a team choose a default task type?
Choose the type that best represents the most common business category for new work in that location. Confirm that the type supports a useful handoff, filter, automation, report, or decision.
Need a clearer ClickUp task structure?
ConsultEvo can help you design ClickUp hierarchies, task types, workflows, reporting, and automation around the way your operation actually works.
