Items Overview

Teams lose clarity when they use one item type for everything. Use this map to pick correctly.

Item map

• Folders: structure, ownership boundaries, inherited context
• Files: binary or office-style document workflows
• Notes: text-first shared knowledge
• Chats: conversational threads tied to work context
• Tasks: accountable executable units
• Contacts/Companies: relationship and directory context
• Events: time-bound schedule artifacts

Decision rule

Ask: “How should this object be reviewed and maintained six months from now?”

• if versioned document lifecycle matters -> file
• if quick collaborative narrative matters -> note
• if completion state and ownership matter -> task
• if discourse and timeline matter -> chat

Governance rule

Do not create duplicate representations of the same unit of work across multiple item types without clear purpose.