ClickUp workspace administration
Learn to structure ClickUp and define configuration, permission and maintenance criteria so different teams can work within a shared and understandable organisation.
Find your starting point
A good fit when you already know ClickUp and need to configure a structure that reflects the process and is straightforward to maintain.
Another option to consider
Teamwork in ClickUpIf you need to use tasks, views and documentation within a prepared workspace, choose the teamwork course.- Hours and sessions
- 12 hours live · 6 sessions of 2 h.
- Group size
- Up to 12 participants per trainer as a reference, adjusted to the practice and feedback.
What you will learn
- 01
Design a hierarchy suited to a process and its teams.
- 02
Configure lists, statuses, fields and templates, and test the workflow with sample data.
- 03
Document permissions, ownership and maintenance, including how to review incomplete tracking information.
A proposed programme
You will configure a recurring-request area for a fictional Operations team. Decide on an understandable hierarchy, prepare statuses, fields and a template, and test the workflow using different profiles. The aim is to explain each decision and leave instructions for maintaining the configuration when the process changes.
We adapt the selection and depth of the modules to the group's starting point and goals.
01Design the structure
Spaces, folders and lists organised around processes, teams and navigation needs.
You will work on
- Represent the process through a Space and Lists, using Folders only when they provide a useful grouping.
- Agree what counts as a request, when it needs subtasks and where its shared context is kept.
- Prepare names and navigation that help people find work without duplicating Lists for each view.
- Practice
- Design and build the Operations area with a request List and an instruction reference, explaining which levels are needed and which add no value.
- How you will check it
- A small hierarchy and an explanation connecting each level to a process need.
02Configure the work
Statuses, fields, templates and automation options available in your plan.
You will work on
- Configure statuses and fields to identify the request type, owner, period and outstanding review.
- Create a task template and check that a new request does not inherit dates, assignees or details belonging to the previous example.
- Evaluate a simple assignment rule according to the plan, test its result and document the manual alternative if it is unavailable.
- Practice
- Create two requests from the template, one complete and another missing its period; test tracking and assignment using the agreed options.
- How you will check it
- Understandable statuses and fields, a tested template and an incomplete request that can still be found for review.
03Govern changes
Access, conventions and configuration reviews to keep the workspace understandable.
You will work on
- Define what coordination and collaboration profiles can do and test it in the case's locations and tasks.
- Review the effect of a status or field change on existing views and tasks before applying it more widely.
- Document who maintains the structure, how changes are requested and how to review incomplete data and outdated templates.
- Practice
- Test the workflow with two profiles, introduce a controlled configuration change and deliver the guide with results and outstanding adjustments.
- How you will check it
- A permissions and change-test record, together with a guide another person can use to review the area.
A configuration that works for the next request
Teaching example
Suggested practice: configure an area for recurring requests, test its lists, statuses and templates with sample data, and check the workflow with different profiles. We prepare an administration and review guide; features are agreed for each edition.
Fictional classroom case. Operations receives monthly requests to prepare internal materials. Lucía administers the area and Pablo reviews deliveries. The case includes requests for two periods and two profiles for testing the configuration.
- Starting point
- Everyone creates their own List and uses a different status for review. Requests are copied from the previous month and retain dates or assignees that no longer apply.
- First attempt
- The first attempt unifies the process and saves a template, but applying it retains the old date. Another request arrives without a period and is treated as valid because it appears on the Board.
- What we review
- The trainer asks participants to review what the template includes, create requests for two periods and add an incomplete-data check. A task changing status does not prove its information is complete; assignment and access are also checked using test profiles.
- Result
- Requests follow shared statuses and the template is applied with the correct period's data. The incomplete entry is flagged for review; the guide records who maintains the configuration and how to repeat the tests before changing it.
Configure, test and maintain
Structure
Operations · Requests
One shared List for the process
Statuses with a purpose
Received · in preparation · in review · closed
Tests
Two periods
Apply the template without carrying over old details
One incomplete entry
Find and review the missing value
Maintenance
Two profiles
Check actions and effective access
Administration guide
Owner, changes and repeatable tests
Teaching illustration of a fictional case; this is not a ClickUp screenshot.
Before calling it complete
- The new request has the correct period, date and owner rather than inheriting the previous example's details.
- An incomplete request can be found and reviewed even if it can change status.
- Each profile can perform the agreed actions and configuration changes are documented.
Sessions to put it into practice.
Reference edition · 12 h live
Reference edition: 12 live hours across 6 sessions of 2 hours. Configuration, testing and review take place during the sessions using features adjusted to the plan and available permissions. Any preparation or additional work is agreed before starting.
- Session 12 h
Design a useful hierarchy
Define the recurring requests and choose the Space, Lists and groupings based on the case's actual workflow.
By the endA justified hierarchy map and initial structure.
- Session 22 h
Configure statuses and fields
Agree what each status means and prepare the information needed to coordinate and review requests.
By the endA small set of statuses and fields with usage instructions.
- Session 32 h
Build and test the template
Prepare a reusable task, create two examples and identify dates, assignees or context carried over by mistake.
By the endA template tested with requests for different periods.
- Session 42 h
Review the workflow and assignment
Follow a complete request and an incomplete one; evaluate a simple rule according to the plan and its manual alternative.
By the endWorkflow tests and an assignment whose result can be checked.
- Session 52 h
Test profiles and changes
Compare expected and observed access and introduce a controlled change to check its effect on tasks.
By the endAn access matrix and a change record with its checks.
- Session 62 h
Hand over the administration guide
Complete a variation of the case and review conventions, ownership and maintenance with the trainer.
By the endA reviewed classroom area and an administration guide with outstanding work identified.
If your team needs to go further
- Migrations, deploying the structure in production and configuring it for multiple departments require a separately agreed scope and validation.
- Integrations, complex automations, advanced dashboards and organisation-wide security policies require another programme.
Learn with someone who designs work systems.
Guillermo Mascaraque Piña
Work systems consultant
Over two years of experience designing systems for companies across industries and sizes.
Guillermo is the planned trainer for this programme. Dates, language and his availability are confirmed when the edition is agreed.
With guidance, practice and support.
Each delivery includes working materials, feedback on practical work and assessment against the agreed objectives.
Materials you can keep
Downloadable, versioned guides, exercises and review criteria for internal use.
To prepare and complete the delivery
A short recommendation, an editable communications kit and a group learning report.
TOF’s own certificate
A certificate of achievement after the agreed assessment. It is not a vendor certification.
A month of email support
On the content covered, up to two accumulated hours for the whole group.
Your team carries out the practice. Implementation services are agreed separately. See the scope →
ClickUp Solutions Partner
Our experience as a ClickUp Solutions Partner helps put the organisation of spaces, projects and work processes into context.
Our partner profile ↗The partnership belongs to The Optimal Flow. Learn’s certificate is issued by TOF; it is not a vendor certification.
