Loading tutorials…
Loading tutorials…
ClickUp has 40+ ClickApps and 40+ Custom Field types. Most teams turn them all on within the first week and spend the next six months wondering why ClickUp 'feels heavy.' This walks the lean subset that delivers 90% of the value.
Who this is forClickUp admins and ops leads deciding which features to enable for the team. If you have ever wondered whether to turn on Sprints, Dependencies, Multiple Assignees, or 12 other ClickApps — this tutorial gives you a decision framework.
What you'll need
Step 1
ClickApps are toggle-able feature modules. Each ClickApp adds UI complexity. Enable selectively.
A ClickApp is a feature module that adds capability to a Space. Examples: Priorities (urgency tagging), Time Tracking (log hours), Dependencies (link blocking Tasks), Sprints (engineering velocity), Goals (OKR tracking), Mind Maps, Pulse (real-time activity feed).
ClickApps are enabled per Space, not Workspace-wide. Marketing might have Priorities + Time Tracking enabled; Engineering might have Sprints + Dependencies. Each Space gets its own UI.
Every enabled ClickApp adds buttons, fields, and menu options to the Task panel. Five extra ClickApps = a noticeably busier UI.
Default state: most Workspaces ship with ~12 ClickApps enabled out of the box. Audit on day one to confirm each is actually used.
Rule: enable a ClickApp only when there is a documented workflow that needs it. Disable everything else — you can always re-enable later.
Step 2
There is no universal "right set" — but there are sensible defaults per team type. Marketing, sales, engineering, ops, and client services each have a recommended subset.
Marketing Space: Priorities (urgency), Custom Fields (campaign metadata), Tags (cross-cutting labels), Time Tracking (cost tracking), Time Estimates (planning), Custom Task Statuses (campaign stages). Disable: Sprints, Story Points, Multiple Assignees (force single-DRI).
Sales / CRM Space: Priorities, Custom Fields (deal metadata), Tags, Pulse (real-time activity is useful for sales), Email ClickApp (if using ClickUp email), Custom Task Statuses (pipeline stages). Disable: Sprints, Time Estimates, Multiple Assignees.
Engineering Space: Priorities, Custom Fields, Sprints, Story Points, Dependencies, Multiple Assignees (pair work is real), Time Tracking, Custom Task Statuses. Disable: Mind Maps (rarely used), Goals (use Sprints instead for short-term work).
Ops / Admin Space: Priorities, Custom Fields, Tags, Recurring Tasks (huge ClickApp for ops — disable Recurring and you lose 50% of ops value), Time Tracking. Disable: Sprints, Story Points, Mind Maps.
Client Services Space: Priorities, Custom Fields (client metadata), Tags (per client), Time Tracking (billable hours), Multiple Assignees (if multiple ops people serve one client), Custom Task Statuses. Disable: Sprints, Story Points.
Step 3
Custom Fields are how you attach structured data to Tasks. ClickUp has 40+ types — but most teams need 6-8 of them.
Most-used types: Dropdown (single-select from a list), Labels (multi-select tags), Money, Number, Date, User (Person), Text (short), Text Area (long), Checkbox, URL.
Power types: Formula (compute values from other fields), Rollup (aggregate Subtask data into parent), Relationship (link Tasks across Lists), Email, Phone, Files, Progress (percentage), Rating (1-5 stars), Location, Currency.
Niche types: Emoji, Date Range, Auto-Increment, Lookup, Vote, Color Picker. Useful occasionally; do not default to enabling them.
Custom Fields are List-scoped by default, but can be made Required across the Workspace (Settings → Custom Fields Manager).
Cap at 6-10 Custom Fields per List. Beyond that, the Task panel becomes a wall of fields nobody fills out.
Step 4
Define a Workspace-wide set of Custom Fields that every team inherits. This is the equivalent of a corporate metadata standard.
Settings → Custom Fields Manager → "+ Add Field."
Build the starter library: Priority (Dropdown — Urgent/High/Normal/Low), Owner (User), Due Date (Date — though most teams use the built-in Due Date instead), Effort (Number, hours), Channel (Dropdown — per team), Category (Dropdown — per team), Notes (Text Area), Links (URL).
Mark "Required" on Custom Fields critical to reporting. Required fields cannot be skipped at Task creation.
Use the same field for the same concept across Lists. Do not have "Priority" on one List and "Urgency" on another. Standardize names.
Document the Custom Field standard in a ClickUp Doc: "Marketing Campaign Custom Fields," "Sales Deal Custom Fields," etc. Every new List references the doc instead of reinventing.
Step 5
Some Custom Fields exist purely for display. Others drive Automations and Dashboards. Distinguish them.
Display-only fields: Notes (Text Area), Links (URL), Files. Useful context but do not drive logic.
Logic-driving fields: Priority (Dropdown), Owner (User), Channel (Dropdown), Status (built-in but feels like a field). Automations and Dashboards filter on these.
Reporting fields: Effort (Number), Spend (Money), Time Tracked. Roll up into Dashboard Calculation cards.
When building Automations and Dashboards, only logic-driving + reporting fields matter. Display fields are for the human reading the Task.
If you cannot say "this field drives X Automation or Y Dashboard card," reconsider whether the field is worth requiring.
Step 6
Enabling 8 new ClickApps at once overwhelms the team. Roll out 1-2 at a time and train explicitly.
Pick one ClickApp to add. Communicate it in the next team standup: "Starting Monday, we are enabling Time Tracking on the Marketing Space. Here is how it works. Here is what we expect logged."
Wait 7-14 days. Check adoption: are people actually using the new ClickApp? Audit time-entries, fill-in rates, etc.
If adoption is real, move to the next ClickApp. If adoption is zero after 14 days, disable the ClickApp and skip — the team did not need it.
Do not add a new ClickApp while the previous one is still in its first month. Layering changes creates "ClickUp keeps changing" fatigue.
Step 7
Every quarter, walk every Space, disable unused ClickApps, archive Custom Fields nobody fills.
Block 30 minutes quarterly per Space.
For each ClickApp enabled in the Space: open the Space, check usage. Is anyone using Priorities? (look at how many Tasks have Priority set). Is anyone logging Time? (look at Time Tracked totals). If usage is under 20%, disable.
For each Custom Field on each List: check fill-in rate. If under 30% filled across the last 90 days of Tasks, archive the field. Either nobody needs it, or it is unclear what to put in it.
Document audit results in the Conventions Doc. "Q2 2026: disabled Sprints in Marketing Space (0% usage). Archived 4 Custom Fields under 25% fill rate."
Common mistakes
Enabling 25+ ClickApps "to see what they do"
What goes wrong: Every Task panel becomes a wall of buttons, fields, and toggles. New team members take 4+ hours to learn the UI instead of 30 minutes. Cost: ~$200/mo in seat-tier upgrade you do not need + $1,500-3,000 of onboarding friction per new hire.
How to avoid: Start with the 6-8 ClickApps your team actually needs per Space. Document the policy. Quarterly audit disables anything under 20% usage.
14+ Custom Fields per List, half empty
What goes wrong: Team sees 14 fields on a Task and fills 3 of them. Dashboards depending on the empty fields show wrong data. Decisions are made on incomplete reporting: typical cost $3-8K/quarter in misallocated spend or wrong priorities.
How to avoid: Cap Custom Fields at 6-10 per List. Mark critical ones Required. Archive fields under 30% fill rate.
Free-text fields where Dropdowns should be
What goes wrong: A 'Department' free-text field collects 12 variations ('Sales,' 'sales,' 'SALES,' 'sales team,' 'Sales & Biz Dev,' etc.). Dropdown reports are useless. Time wasted manually normalizing data: ~3-5 hrs/quarter (~$300-1,000 in admin time).
How to avoid: Whenever the same handful of values keeps appearing, convert to a Dropdown or Labels field. Lock the picklist. Document it.
Enabling Multiple Assignees by default
What goes wrong: Multi-assignee Tasks have no clear owner. Nobody picks up the work. Marketing campaigns miss deadlines. Engineering bugs linger. Sales deals stall. Cost: 2-4 missed deadlines/quarter at $3-15K each.
How to avoid: Disable Multiple Assignees on most Spaces (Space Settings → ClickApps). Force single-DRI accountability. Re-enable only on Spaces where pair work is genuinely common (some engineering teams, some client services teams).
No quarterly audit
What goes wrong: Workspace accumulates 6 months of unused ClickApps and abandoned Custom Fields. UI is bloated. Onboarding new hires takes 2x longer. Team morale around 'ClickUp is heavy' grows. Either the team disengages (lost ~$8-15K/yr in tool ROI) or you commission a specialist rebuild ($500-1,500).
How to avoid: 30-minute quarterly audit per Space. Disable unused ClickApps. Archive unused Custom Fields. Document changes. Compounds into a clean Workspace over years.
Not standardizing field names across teams
What goes wrong: Marketing calls it 'Channel,' Sales calls it 'Source,' Ops calls it 'Origin.' All three mean the same concept. Cross-team Dashboards cannot roll up. Reporting requires manual normalization in Sheets. Cost: 4-6 hrs/quarter of analyst time (~$400-1,200).
How to avoid: Document a Workspace-wide naming standard for cross-cutting fields (Priority, Owner, Channel, Status). Every team uses the same field name even if values differ.
Recap
Done — what's next
How to set up a ClickUp workspace and hierarchy without painting yourself into a corner
Read the next tutorial
Hand it off
ClickApp and Custom Field sprawl is the #1 reason teams complain ClickUp 'feels heavy.' A specialist who has audited 50+ Workspaces knows which 6-8 ClickApps per team type actually drive value and which 12-15 are clutter. Typical configuration session: $150-300 one-shot, or ongoing ops support at $14-16/hr.
See specialist rates
No — explicitly the opposite. Every enabled ClickApp adds UI clutter. Start with the 6-8 essentials per Space (Priorities, Custom Fields, Tags, Time Tracking, Custom Statuses, plus 2-3 team-specific ones). Add more only when a documented workflow needs it.
A ClickApp is a feature module enabled at the Space level (Time Tracking, Sprints, Dependencies). A Custom Field is structured data attached to a Task (Priority dropdown, Budget number, Owner user). ClickApps add capabilities; Custom Fields add metadata.
Over 10 per List is usually too many. Beyond 10, the Task panel becomes a wall of fields and fill-in rates drop below 30%. If you genuinely need more, you probably need a second List with a different workflow, not 15 fields on one List.
Only the ones that drive reporting or Automations. Required fields slow Task creation, so reserve the friction for fields where missing data breaks something downstream (e.g., 'Owner' is Required; 'Notes' is not). Workspace → Settings → Custom Fields Manager → mark Required per field.
Not directly — you have to archive the old field and create a new one. Plan field types up front. If you might need multi-select someday, start with Labels (multi-select) rather than Dropdown (single-select).
ClickUp
ClickUp is famously deep — five levels of hierarchy and 40+ ClickApps before you even create a task. Most teams end up with 8 Spaces, 60 Lists, and no idea where anything lives. This walks the setup sequence that keeps ClickUp usable past month three.
ClickUp
ClickUp ships with 200+ Automation recipes. Most teams turn on 30, forget what 20 of them do, and watch tasks slip through the cracks. This walks the right way to roll out Automations — and the registry that keeps them maintainable.
ClickUp
ClickUp ships with 15+ view types and 30+ Dashboard cards. Most teams use 3 views and 0 Dashboards because the rest is overwhelming. This walks the views worth building, the cards worth showing, and how to keep the team on the same page.
Monday.com
Monday.com is easy to spin up and easy to scatter. Three weeks in, most teams have 14 boards across 4 workspaces with no naming convention and no governance. This walks the setup sequence that keeps Monday useful past month three.
ClickUp
DIY ClickUp is a great idea — until you have 60+ Lists, 25 enabled ClickApps, and the team has stopped trusting the data. This is the honest framework: when the cost of self-managing exceeds the cost of hiring.