Task Configuration
Route: /org/taskconfig · Permission: Page Access of Task Configuration
Module: task_configuration · Header gear: Show Task Configuration in the header settings menu.
1. What Task Configuration is
Task Configuration defines the vocabulary a project uses to describe its work — what a task can be called, how urgent it can be, what states it can occupy, how it may move between them, and how work is grouped for billing.
It is not where tasks are managed. Nothing on this screen touches a single task directly; it changes the options every task in the project can choose from.
| Task Configuration | Task Management | |
|---|---|---|
| Route | /org/taskconfig | /org/tasks |
| Changes | The options | The tasks |
| Scope | One project | One project |
| Permission | Page Access of Task Configuration | View Tasks |
| Typical user | Project admin, once | Everyone, daily |
| Effect of a change | Every task in the project | One task |
Every tab on this screen writes to /org/projects/{projectId}/config/…. Two projects in the same
organization can — and usually do — have completely different statuses, types and priorities.
There is no organization-wide task vocabulary and no inheritance between projects. Setting up a second project means configuring it again from scratch.
2. How configuration spreads across the application
Nothing here is cosmetic. Each tab feeds a specific control somewhere else.
| Tab | Feeds | Permission to manage |
|---|---|---|
| Priorities | The priority control on every task; grouping in list view | Manage Task Priority |
| Types | The type control; the icon shown on every card | Manage Task Status and workflow |
| Statuses | Kanban columns, the status control, analytics buckets | Manage Task Status |
| Workflow | Which status transitions are legal | Manage Task Status |
| Categories | Task grouping, supervisor routing, billable default | Manage task categories |
3. The screen — step by step
Step 1 · Open it
Two routes in:
| From | How |
|---|---|
| Projects list | The Task Configuration button on /org/projects |
| Header settings gear | Present only if you hold Show Task Configuration in the header settings menu. |
Step 2 · Select a project
The screen is a full-screen settings hub (SettingsHubShell) — the application header and
sidebar are hidden while you are on it. Its rail carries a project selector, and until a project is
chosen the content pane shows:
Select a Project — Choose a project from the rail to configure its tasks.
Because the header is hidden, the in-app Docs button appears as a floating icon at the top right instead of in the header bar. The same is true of Project Details, Resolve Settings and the other isolated hubs.
Step 3 · Pick a section
Five sections, in rail order:
| # | Section | Icon | Tab value |
|---|---|---|---|
| 1 | Task Priorities | Alert circle | priorities |
| 2 | Task Types | List | types |
| 3 | Task Status | Check square | statuses |
| 4 | Task Workflow | Git branch | workflow |
| 5 | Task Categories | Folder | categories |
The active section is written to the URL as ?tab=, so every section is directly linkable —
/org/taskconfig?tab=workflow. An unrecognised value falls back to priorities.
Step 4 · Leave
Exit Task Config in the rail returns you to /org/projects.
4. Field reference — the hub itself
| Control | Type | Behaviour |
|---|---|---|
| Project selector | Rail dropdown | Sourced from the projects you can access. Nothing loads until one is picked |
| Section rail | Five entries | Always all five — the rail does not hide sections you cannot manage |
| Full screen (Workflow only) | Button | Expands the canvas to a fixed overlay. Only rendered on the Workflow section |
| Exit Task Config | Button | Navigates to /org/projects |
5. The permission model — read is one gate, write is five
This screen has an unusual shape, and it is the source of most confusion about it.
| Gate | Permission | Effect |
|---|---|---|
| Page | Page Access of Task Configuration | Without it the page renders Access Denied — "You do not have permission to view task configurations." |
| Priorities | Manage Task Priority | |
| Types | Manage Task Status and workflow | |
| Statuses | Manage Task Status | |
| Workflow | Manage Task Status | Shared with Statuses — there is no separate workflow permission |
| Categories | Manage task categories |
Holding Page Access of Task Configuration alone gets you onto the page, and then every section shows:
You do not have permission to manage this configuration.
Sections are not hidden by permission. A user with only Manage Task Priority still sees all five rail entries and gets the permission message on the other four. That is deliberate — it tells the user the capability exists and who to ask — but it does mean the rail is not a reliable indication of what you can do.
Grant Manage Task Status and you have granted the workflow canvas too. There is no way to let someone rename a status without also letting them redraw the transition graph.
6. Downstream
| Change | Immediate effect elsewhere |
|---|---|
| Add a status | A new Kanban column appears; a new node appears on the workflow canvas |
| Delete a status | The column disappears. The workflow keeps no record of it |
| Reorder statuses | Kanban column order changes |
| Set a default type | New tasks created without a type resolve to it |
| Delete a category | Tasks in it become uncategorised — they are not deleted |
| Toggle a category's billable flag | Applies to new tasks only; existing tasks keep their flag |
7. Don't confuse this with…
| Screen | Route | What it does |
|---|---|---|
| Task Configuration (this page) | /org/taskconfig | The task vocabulary for one project |
| Project Details | /org/projects/:id | The project itself — budget, team, locations, timesheet rules |
| Organization Settings | /org/settings | Organization-wide settings. Has no task tab |
| Resolve Settings | /org/resolve/settings | The service desk's own statuses and workflows — unrelated |
Resolve tickets do not use task statuses, and configuring one does nothing to the other. If you are looking at a ticket, you want Statuses & Workflows in Resolve Settings.
8. Troubleshooting
| Symptom | Cause |
|---|---|
| Access Denied on the whole page | Missing Page Access of Task Configuration |
| Every section says "no permission to manage" | You hold Page Access of Task Configuration but none of the five manage permissions |
| "Select a Project" and nothing else | No project chosen in the rail |
| Workflow section is blank on a phone | The canvas is desktop-only and renders a fallback |
| A change did not appear on the tasks screen | Configuration is per project — check you configured the same project you are viewing |
| No Task Configuration entry in the header gear | Missing Show Task Configuration in the header settings menu.; the page is still reachable from Projects |
Related
- Task Management — where the vocabulary gets used
- Statuses and Workflow — the two tabs that share a permission
- Orbit Ops overview