Project and task keys give every project a short, unique identifier and every task a permanent number. Instead of copying long titles or links, teams can reference work with simple, readable IDs like MKTG-42. Communication gets clearer. Traceability gets stronger. And your workflows move faster.
Key benefits and use cases
Clearer communication
Reference 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 tooling.Compliance and audit traceability
Create clear documentation trails for invoicing and ISO-style 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 look like MKTG or BRND
Task keys combine the project key and number, like MKTG-42
These keys appear throughout awork and can be searched, copied, and referenced anywhere.
Editable project keys: Project keys can be renamed by authorised users. Task numbers stay fixed for reliable references.
How to access and enable project and task keys
Keys are automatically generated for all projects and tasks based on project names and task creation order.
Keys are hidden by default in workspaces created before the Keys release. In newer workspaces, they are visible by default.
A workspace admin can adjust visibility at any time in Settings → General → Task settings
Toggle on or off Show project & task keys for all projects
Individual projects can override the workspace default via Project Settings → General
Select Show/Hide/Workspace Default for the option Task and project key
Important: Keys will not appear until visibility is enabled at the workspace or project level.
How visibility settings work
Key visibility is controlled at two levels:
Workspace setting: A simple on/off toggle in Settings → General → Task settings Show project & task keys for all projects. This sets the default for all projects.
Project setting — Each project can choose:
Workspace default: Follows the workspace setting (this is the default)
On: Always show keys for this project
Off: Never show keys for this project
What visibility controls:
When keys are hidden, they won't appear in task lists, dropdown menus, task widgets, or other places throughout awork. But they will always be shown on the project detail page, in the Keys column in the project overview, and in URLs.
Key capabilities
Auto-generated project keys
New projects receive 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 using up to 32 characters (uppercase letters, numbers, dashes, and underscores).
Smart search by key
Search across all projects using a full key (MKTG-42) or just a number (42).Flexible visibility controls
Set defaults at the workspace level and override them per project.Click to copy
Click a task key to copy the task URL or a project key to copy the project URL.
Audit log entries
Changes of Project keys are logged for compliance tracking.
Permissions and access control
Visibility and editing depend on your role.
All users can view project and task keys when visibility is enabled in workspace or project settings.
Users with writing rights 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 the keys and can set the default visibility for all projects across the workspace.
Tip: Use workspace defaults to keep visibility consistent, then override only when needed.
Known limitations and considerations
No keys for private tasks
Private tasks without a project do not receive task numbers.Old keys don't redirect after renaming
Old keys stop working after a rename. Only the current key works.
Important: A warning appears when renaming a project key to prevent accidental breakage of existing references.
Please note: Keys are reusable after project deletion
Deleting a project makes its key available again, which may cause confusion in old references.
Frequently Asked Questions (FAQ)
What happens if I rename a project key?
What happens if I rename a project key?
Old references stop working immediately. Only the new project key will work going forward.
Can I search using just a task number?
Can I search using just a task number?
Yes. Typing a number like 42 finds all tasks ending in -42 across projects.
Who can edit project keys?
Who can edit project keys?
Users with writing rights 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?
Do private tasks get task keys?
No. Private tasks do not receive task numbers because they are personal notes and not trackable project work.
Can project keys be hidden?
Can project keys be hidden?
Yes. Visibility can be controlled at both the workspace and project level.