Projects

Projects at /items/project is where project work lives: the project hierarchy with its deliverables and tasks. Parent Projects, Child Projects, Deliverables, and Tasks are the hierarchy objects behind the surface; shared fields map across them under Field Mappings. The full model lives on the Work items hub.

• A company tree anchors the left: search companies, an Include-closed toggle, and per-company project counts. Pick the company first; the table follows.
• The All Projects table lists name, owner, status, due, and type per row. Expanders open each project.
• Table controls sit above the rows: search, Default View, Columns, Filters, Matching Only, Sort, Expand All, and New Project. Views shape this list; the org default for it is set under Table Views.

• One project means one bounded piece of work. A project holding three engagements forces every view and mapping to guess.
• Deliverables and Tasks are work items: their types, fields, and defaults live under Work Item Types, and their statuses run inside Settings Workflows. Move a row only when the work actually moved.
• Shared facts belong in mapped fields, not in per-project improvisation. Check Field Mappings before adding a field that another level already carries.

What next

• Work items: the hub — hierarchy, lists, customization, workflows, approvals, sessions.
• Programs: the engagement containers above these rows.
• Companies: the client organizations behind the company tree.
• Contacts: the people at those companies.
• Deliverables: the client-facing outputs on the work side.
• Files: the file store behind record attachments.
• Templates: repeatable project shapes instead of rebuilding.
• Field Mappings: the shared fields across the hierarchy.
• Work Item Types: the Deliverables and Tasks types on the work side.
• My Tasks: the personal slice of this workspace.