Last updated 2026-04-25
Team area
/team is the single entry point for everything organised by person rather than by project. Five tabs, one filter bar (date range, department, person), one auth scope (managers see direct reports, admins see the whole company).
When to use which tab
| Tab | Time horizon | Use when |
|---|---|---|
| Overview | Recent (default 30d) | Spot-check the team — hours, billable %, corrections, recent activity per person. |
| Utilization | Past | Who's hitting target billable %, who's under. Default target 70%. |
| Capacity | Present (next 6–12 weeks) | Who's allocated to what; flag over-allocation in red, low utilization in green. |
| Scenario | Future ("what if") | Model a re-allocation without committing. No save button — calculator only. |
| Approvals | Past weeks | Submitted timesheets waiting for your sign-off. |
Mental model
- Past = Utilization ("how much of what we tracked was billable?")
- Present = Capacity ("what's currently allocated this and next month?")
- Future = Scenario ("if I move Sarah to Project X for 4 weeks, who breaks?")
- Per-person deep-dive = Overview row → click name → employee detail page.
What's NOT here
- Project-axis views (project list, Gantt timeline, per-project tasks, plan-vs-actual variance, profitability) live under
/projects. The two areas share the underlying data but answer different questions. - Salary-derived costs and project profitability are admin & finance only. Managers see hours, billable %, and corrections but not dollar costs (the workforce is global and individual salaries are confidential). Setting employee hourly_cost / opening
/projects/profitabilityrequires the admin or finance role. - Adding new employees lives under Admin → Employees. Existing employee scope/role changes too.
Detail pages
Each tab has its own dedicated help article: see Team overview & approvals, Capacity, Utilization, Scenario planner.
See something wrong or outdated in this article? Report it →