Platform Overview: Objects, Columns, and Permissions
What this domain tests
The Platform Overview domain checks whether you can model work in the correct object and predict how permissions and column types behave. Questions often ask where data lives, which column is read-only, and what a view can change.
Core rules and concepts
- Hierarchy: account > workspace > folder > board > group > item > subitem. Workspaces and folders organize boards; groups organize items inside one board.
- Roles: workspace admins manage settings; board owners configure the board; subscribers edit items; viewers read only. A view never grants edit rights.
- Column behavior: Status stores one label; dropdown stores several; connect boards links items; mirror displays a connected value read-only; formula calculates; dependency drives Gantt scheduling.
- Views: Main table, Kanban, Calendar, Timeline, Workload, Form, and Dashboard are presentations of the same items, not separate data stores.
Worked example
A tasks board must show each task's project status. Add a connect boards column to Tasks pointing at Projects, then a mirror column to display the project's status. The mirror updates automatically but cannot be edited on Tasks; the change must be made on the Projects item.
Traps
Mixing up mirror and connect boards; assuming subitems inherit parent columns; thinking a shared view changes permissions; and forgetting that deleting a board sends it to trash rather than permanently erasing it.