Teamwork

Teamwork

Project management platform for client services and agencies. Organizes work into projects with task lists, milestones, time logging, and workload planning. Each customer site has its own subdomain on Teamwork’s domain.

Entity Hierarchy

• Companies — client organizations. Projects and people can be associated with companies.
• Projects — the primary container. Has status (active, archived), category, company association, and budget settings.
  • Project Categories — taxonomy for organizing projects.
• Task Lists — ordered groups of tasks within a project.
  • Tasks — individual work items with assignees, due dates, priority, tags, and time estimates.
• Milestones — key dates/deadlines within a project. Can have task list dependencies.
  • Milestones Deadlines — view milestones by their deadline dates across projects.
• Notebooks — rich-text documents within a project. Support comments.
• Tags — cross-project labels for tasks, projects, and other entities.
• Forms — intake forms for collecting structured requests.
• Dashboards — visual project/portfolio overviews.

Time Tracking

• Time Entries — individual time logs with duration, user, task, date, and billable flag.
• Timesheets — aggregated time view per user and period.
• Timelog Totals — summarized time data for reporting.
• Me Timers — active running timers for the authenticated user.
• Workload Planners — capacity planning views showing availability vs. assigned work.

People

• People — team members and collaborators. Each person has roles, company association, and project access.

Activity

• Latest Activity — feed of recent actions across all projects (task completions, comments, file uploads, etc.).

Workflows

1. Project overview: Enumerate projects (active, billable, or full catalog as the question requires), open each project’s task lists, then drill into tasks for the work breakdown.
2. Deadline tracking: Pull milestones and the cross-project deadline view to see what is due next.
3. Time audit: Raw time entries → rolled-up timelog totals → per-user timesheets → active timers for the signed-in user.
4. Team capacity: Roster → workload planners → tasks assigned to people to see who is overloaded.
5. Documentation: Project notebooks first; load comment threads only after you have the notebook id from that listing.

Gotchas

• Pagination: Uses page and pageSize; responses include total counts.
• Cross-project lists: Many list tools span all projects; narrow in follow-up steps when you need a single project.
• Active vs Billable projects: Filtered project listings mirror the full project shape—pick the slice that matches your question.
• Notebook comments: Need notebookId from the notebooks list before loading comment threads.