Project and Task Keys
Project and task keys give every project a short, unique identifier and every task a permanent number. Instead of copying long titles or links, your team can reference work with simple, readable IDs like MKTG-42. Communication becomes clearer, tracking becomes easier. And your workflows get faster.
Main benefits and use cases
- Clearer communication
Name work clearly in conversations, comments, and standups. - Stable task references
Task numbers never change, even if task names do. - Faster developer workflows
Use task keys directly in commit messages and tools. - Compliance and audit tracking
Create clear documentation paths for billing and ISO-compliant audits.
How project and task keys work
Every project gets a short key and every task in that project gets a sequential number.
- Project keys are short codes like MKTG or BRND
- Task keys combine the project key and the number, like MKTG-42
These keys appear everywhere in awork and can be searched, copied, and used anywhere.
Editable project keys: Project keys can be renamed. Task numbers stay the same.
Enabling and using keys
-
Keys are automatically generated for all projects and tasks based on project names and creation order.
-
Keys are hidden by default in workspaces created before keys were introduced. In newer workspaces, they're visible by default.
-
A workspace admin can adjust visibility at any time in Settings (gear icon in the bottom left of the main menu) → Workspace → Tasks: Enable or disable Show project and task keys for all projects
-
Individual projects can override the workspace setting via Project Settings → General: Choose Show, Hide, or Workspace Default for the Task and project key option
Important: Keys only appear when visibility is enabled at the workspace or project level.
How visibility control works
Key visibility is controlled on two levels:
- Workspace setting: A simple on/off toggle in Settings → Workspace → Tasks:
Show project and task keys for all projects
This sets the default for all projects. - Project setting: Each project can choose:
- Workspace Default: Follows the workspace setting (default)
- On: Always show keys for this project
- Off: Never show keys for this project
What visibility controls:
When keys are hidden, they don't appear in task lists, dropdown menus, task widgets, or other places in awork. However, they're always shown on the project detail page, in the Key column in the project overview, and in URLs.
Key features
- Auto-generated project keys
New projects get a 4-character key based on the project name. - Sequential task numbering
Tasks are numbered in creation order within each project and never change. - Editable project keys
Project admins can rename keys up to 32 characters (uppercase letters, numbers, hyphens, and underscores). - Smart key search
Search across all projects using a full key (MKTG-42) or just a number (42). - Flexible visibility control
Set defaults at the workspace level and override per project. - Copy with one click
Click a task key to copy the task URL, or click a project key to copy the project URL. - Audit log entries
Changes to project keys are logged for compliance tracking.
Permissions and access control
Visibility and editing depend on your role.
- All users can see project and task keys when visibility is enabled in workspace or project settings.
- Users with write permissions for project settings or project details, or who can create new projects, can edit the project key and adjust visibility for individual projects.
- Workspace admins can edit keys and set the default visibility for all projects across the entire workspace.
Tip: Use workspace defaults to keep visibility consistent and only override when needed.
Known limitations and notes
- No keys for private tasks
Private tasks without a project don't get task numbers. - Old keys don't redirect after renaming
Old keys no longer work after a rename. Only the current key works.
Important: When renaming a project key, a warning appears to help you avoid accidentally breaking existing references.
Keep in mind: Keys are reusable after project deletion
Deleting a project makes its key available again, which can cause confusion with old references.
FAQ
What happens when I rename a project key?
Old references stop working immediately. From then on, only the new project key works.
Can I search using just a task number?
Yes. If you enter just a number like 42, you'll find all tasks ending in -42 across all projects.
Who can edit project keys?
Users with write permissions for project settings or project details, users who can create new projects, and workspace admins can edit project keys.
Do private tasks get task keys?
No. Private tasks don't get task numbers because they're personal notes, not trackable project work.
Can project keys be hidden?
Yes. Visibility can be controlled at both the workspace and project level.
Powered by happysupport.ai