Understand personal and team work, list and board views, and relationship choices before setup.
Personal work or team work?#
A personal task workflow keeps records within its explicit personal-access rules. A shared team workflow makes the permitted work available to its members. A workspace manager does not automatically acquire access to another person’s private personal tasks.
| Choice | When it fits | What it changes |
|---|---|---|
| Personal | Work you manage privately. | Uses the selected personal visibility rules; do not use it to share a team queue implicitly. |
| Team | Work that colleagues need to coordinate. | Uses shared membership, assignment and editing permissions. Review who can see and change records. |
| List | A compact ordered view of work. | Emphasises individual tasks, due dates and completion. |
| Board | A visual flow through statuses. | Groups work by stage; it does not change the underlying privacy or ownership. |
Choose the relationships you actually manage#
Customer, vendor, lead and partner describe different business relationships. A person or company can have more than one role when that reflects the real relationship.
People and companies are different entity types. Select the correct type and relationship roles before entering information. Enabling a relationship category does not give that contact a staff login or access to your workspace.
Stages and priorities#
Statuses describe progress; priorities describe urgency. Pick a small, clear set your team understands. Changing a view or priority does not transfer a task to another workspace or override personal privacy.
Keep the active workspace, actual business requirements and current setup summary in view. A guide explains a choice; it does not make that choice for you.