Get started
Get started
The Get started domain tests whether you can structure a workspace correctly and navigate it quickly. Expect questions on hierarchy, setup order, roles, and the UI conventions that decide whether a workspace scales or turns into a mess.
The hierarchy is fixed
- Workspace → Space → Folder → List → Task → Subtask. A task cannot exist outside a List; a List sits in a Folder or directly in a Space (a folderless List).
- Spaces usually map to departments or major workstreams, Folders to projects or clients, Lists to queues of work.
- Views (List, Board, Calendar, Gantt, Timeline, Workload) are lenses on the same tasks. Creating a view never copies tasks.
- Everything aggregates tasks across the workspace, My Work is your personal queue, and the Command Center (Cmd/Ctrl+K) jumps to any item, view, or setting.
- A setup order that holds up: invite people and assign roles → create Spaces → decide ClickApps and permissions → import or apply a template → connect integrations.
Worked example
A 12-person agency onboards 30 clients. Build one Delivery Space, one Folder per client, and inside each Folder a List for active work and a List for assets. Standardize statuses at the Delivery Space so cross-client reporting works. Keep margin data in a separate private Space. Invite clients as guests and share only their specific List, never the Space, so they cannot see other clients. The reasoning: group by the unit people report on (client), push shared configuration as high as possible (Space-level statuses), and grant the narrowest access that still lets the client work.
Traps that cost marks
- Confusing delete with archive. Deleting a Space or List removes its tasks; archiving hides them and keeps the data.
- Assuming guests behave like members. Guests get a restricted default experience and are scoped item by item.
- Believing a new view duplicates tasks, or that editing a Board card leaves the List row unchanged. It is the same task.
- Forgetting that statuses, Custom Fields, and ClickApps set higher in the tree are inherited unless overridden lower down.