--- title: Priority slug: priority description: Set which requests your workforce works on first, with Critical, Normal and Low tiers on top of closest-to-delivery order. createdAt: 2026-11-06T14:37:49.512Z --- :::hint{type="info"} **Beta** This feature is currently only available to certain organizations. The plan is to make it available in all projects as soon as possible. ::: The Priority tab shows the order your workforce picks up work across all requests in a project. Use it when one request matters more than the others, or when a request should wait behind what you upload next. ## Prerequisites The Priority tab is in Project Management, on each project where priority is enabled. Users with the workspace role Admin, Project Manager, Annotation Manager or Developer can see it. To change priority, you need the workspace role Admin or Project Manager, and access to every request in the project. If you can access only some of the requests, you see just those, numbered from 1 in each tier, and cannot change the order. See [Roles & permissions](docId\:Zush2h50kKF5pd3n0dWSL). ## Overview By default, the workforce is always given the task closest to delivery. Priority lets you override that for specific requests by moving them into one of three tiers: Critical, Normal, or Low. ## How priority works Each time someone in your workforce submits a task, the platform picks their next task from all requests in the project. Two things decide the order: the request's tier, and how close each task is to delivery. **Closest to delivery goes first.** Within a tier, a task late in the workflow (for example a correction after Client QA) is picked before a task early in it (a new annotation). This is what shortens turnaround: nothing that is nearly finished waits behind new work. **Tiers override that for whole requests.** | **Tier** | **What it means** | **Order inside the tier** | | ------------------------------ | ---------------------------------------------------------------------------------------------------- | -------------------------------------------------- | | Critical (up to 3 per project) | Worked on before everything else, even ahead of nearly finished work in other requests. | The order you set. | | Normal | The default. Every new request lands here. | Closest to delivery first. Your order breaks ties. | | Low | Ranks below every Normal request, including ones you upload later. Use it for work that should wait. | Closest to delivery first. Your order breaks ties. | :::hint{type="warning"} Use Critical with care. A critical request can push nearly-finished work from other requests back in line, so it is capped at three per project. ::: **Completed requests** stay in their tier, with the status Completed. Archived requests are not shown. ## Change priority Nothing is applied until you save, so you can rearrange freely and discard if you change your mind. ::Image[]{src="https://api.archbee.com/api/optimize/wLEz_RbWP6nIMpY-prjlm/ZlFbFaofWdZ5umvUeFsRf_image.png" size="100" isUploading="false" width="1920" height="1619" darkWidth="1920" darkHeight="1619" showCaption="true" alt="Editing priority"} ::::WorkflowBlock :::WorkflowBlockItem Open the project and go to the **Priority** tab. ::: :::WorkflowBlockItem Click **Edit priority**. Drag handles appear on each request. ::: :::WorkflowBlockItem Drag a request by its handle to a new position, or into another tier. ::: :::WorkflowBlockItem Click **Save changes**, then **Save** to confirm. Your workforce is given tasks in the new order from their next submit. Nobody is moved mid-task. ::: :::: Click **Cancel** to discard all changes. If you changed anything, you are asked to confirm first. The same happens if you leave the page while editing. **Save changes** stays disabled until you change the order. If Critical already holds three requests, you cannot drop a fourth. Move one out first. Each tier has its own search field. Search by request name or ID. Matches are highlighted in place, so you can drag them while searching. ## Common questions :::ExpandableHeading{isOpen="true"} ### Why can I see priority but not edit it? Editing needs the workspace role Admin or Project Manager, and access to every request in the project. Hover the Read-only label to see which one applies to you. Ask your workspace Admin about roles, or your Kognic contact about access to the other requests. ::: :::ExpandableHeading{isOpen="true"} ### I moved a request up in Normal and nothing changed. Why? Inside Normal and Low, the task closest to delivery still goes first. Your order only decides between tasks that are equally close. To put a request ahead of everything else, move it to Critical. ::: :::ExpandableHeading{isOpen="true"} ### Why can I only have three critical requests? A critical request is worked on before everything else, even ahead of nearly finished work in other requests. More than a few at a time would slow down the rest of your project. Use Critical only for a request that has to finish before everything else, and move it back to Normal as soon as it no longer does. ::: :::ExpandableHeading{isOpen="true"} ### My changes were not saved. What happened? Someone else changed priority while you were editing, or a request in the list was archived. The list is reloaded with the current order and you stay in edit mode. Make your changes again. If the save failed for another reason, your changes are kept and you can try again. ::: :::ExpandableHeading{isOpen="true"} ### Where do new requests land? At the bottom of Normal. ::: :::ExpandableHeading{isOpen="true"} ### What happens to a completed request? It stays in its tier, with the status Completed. Archived requests are removed from the list. ::: :::ExpandableHeading{isOpen="true"} ### Does priority move someone off a task they are working on? No. The order applies when a task is submitted, never while it is in progress. Paused tasks are never handed out automatically. ::: ## Related - [My Tasks](docId\:bGTv8PrkHlmdeOxeBBu31), where your workforce sees the prioritized task per project - [Roles & permissions](docId\:Zush2h50kKF5pd3n0dWSL), the roles needed to see and edit priority - [Annotation Workflows](docId:5WO8vmPiFWYst3v5LTfOs), the stages that decide how close a task is to delivery