Orbit Ops
Orbit Ops is where work is planned, tracked, timed and billed. Its centre is the Task Management category: five modules that between them own the task board, the vocabulary tasks are described in, the Gantt chart, resource billing, and the sandbox where sprints are planned before they are committed.
1. The five modules
| Module | Route | Permissions | Documentation |
|---|---|---|---|
| Task Management | /org/tasks | 13 | Task Management |
| Task Configuration | /org/taskconfig | 6 | Task Configuration |
| Task Timelines | /org/project/timelines | 2 | Task Timelines |
| Resource Bills | /org/resource/bills | 4 | Resource Bills |
| Planning | /org/tasks/planning | 4 | Planning workspace |
One module, four routes
task_manage owns /org/tasks, /org/my-tasks, /org/my-timesheets and
/org/timesheets-approval. Orbit's usual one-module-one-route rule does not hold here, which is why
timesheets are permissioned from the task module.
2. How the pieces connect
Two configuration screens govern everything downstream:
| Configures | Where | Governs |
|---|---|---|
| The task vocabulary | Task Configuration | What a task can be |
| The time-capture policy | Project timesheet settings | When and how time is logged |
3. Everything documented
Task workspace
| Page | Covers |
|---|---|
| Overview | Screen anatomy, the URL, all thirteen permissions |
| Creating a task | Fourteen fields, inheritance, validation |
| Filtering and grouping | Four filter mechanisms; server against client |
| List view | Hierarchy, inline editing, pagination |
| Kanban board | Columns, drops, swimlanes |
| Table view | Fifteen columns, thirteen editable |
| Calendar view | Due dates, holidays, leave |
| Task detail | Six tabs, the five field permissions |
| Subtasks | Hierarchy and cascading inheritance |
| Comments and mentions | Rich text, @, notification routing |
| Activity history | The database-level audit trail |
| Time logs | Logging, and the governance around it |
| Bulk actions | Six operations, and the two that expand |
| Jira sync | Mapping, and why a normal sync misses changes |
| My Tasks | Cross-project work; the mobile-capable screen |
Configuration
| Page | Covers |
|---|---|
| Overview | The hub, and one read permission against five write permissions |
| Priorities | The urgency list |
| Types | Kinds of work, and the default |
| Statuses | The states, and the three fixed categories |
| Workflow | The transition canvas |
| Categories | Supervisors and the billable default |
Planning
| Page | Covers |
|---|---|
| Planning workspace | Sandbox scenarios, the five tabs, permissions, deep links |
| Phases, sprints and milestones | Parent phase, warn-or-block date rules, a task's two links, story points |
| Capacity and planned hires | Net hours from holidays, leave and allocation; placeholder hires |
| Scenarios and commit | Board, Suggest with AI, drift and rebase, commit preview, compare, history |
| Goals, burndown and insights | Goals and criteria, AI goal check, burndown, radar signals, report fields |
| Planning settings | Estimation unit, size scale, focus factor, date boundaries, drift rule |
| Planning for integrators and assistants | Public API scopes and endpoints, planning.committed webhook, MCP tools, SDK methods, Orbit Assistant questions |
Timelines, timesheets, billing and analytics
| Page | Covers |
|---|---|
| Task Timelines | Gantt, dependencies, schedule health |
| My Timesheets | Weekly submission |
| Timesheet approvals | The approver's side |
| Project timesheet settings | The governance policy |
| Resource Bills | Managing bills |
| Drilldown | The audit trail behind a bill |
| Adjustments | Corrections, with reasons |
| Task Analytics | Counts and trends |
| Timesheet Analytics | Hours across the team |
| Billing Analytics | Billable value — and bill generation |
| Profitability Control Tower | Margin, leakage, forecast |
4. Five things that surprise people
| Edit Tasks is not enough** | Assignee, due date, estimate and status each need their own permission — see Task detail |
| Everything is per project | Statuses, types, categories and timesheet policy are all per project, with no inheritance |
| Bills are generated from the analytics screen | Not from Resource Bills — from Billing Analytics |
| Category and milestone cascade to subtasks | A database trigger rewrites the whole subtree — see Subtasks |
| A Jira mapping change needs Resync All | A normal sync will never reach those issues — see Jira sync |
5. Not yet documented
These routes exist and belong to other categories. They get their own documentation pass:
| Screen | Route |
|---|---|
| Projects | /org/projects |
| Project Details | /org/projects/:id — except its Timesheet Settings tab |
| Project Access | /org/projectaccess |
| Delegation | /org/me/delegation |
| Personas | /org/persona |
Related
- Task Management — the place to start
- Task Configuration — configure before inviting a team in