How to delete projects in Blue.
Delete a Project
The deleteProject mutation permanently removes a project and all its associated data from Blue.
Basic Example
mutation {
deleteProject(id: "{project-id}") {
success
}
}
With Variables
mutation DeleteProject($projectId: String!) {
deleteProject(id: $projectId) {
success
}
}
Variables:
{
"projectId": "abc123-project-id"
}
Project deletion is permanent. Once a project is deleted, all associated data will be permanently removed from the system. This includes:
- All todos and lists
- Comments and attachments
- Custom fields and their values
- Automations
- Tags and dependencies
- User assignments
- File attachments
Please ensure you have backed up any important information before proceeding with the deletion.
- All todos and lists
- Comments and attachments
- Custom fields and their values
- Automations
- Tags and dependencies
- User assignments
- File attachments
Please ensure you have backed up any important information before proceeding with the deletion.
Mutation Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
id |
String! | ✅ Yes | The unique identifier of the project to delete |
Response Fields
| Field | Type | Description |
|---|---|---|
success |
Boolean! | Indicates whether the deletion was successful |
Required Permissions
To delete a project, you must have:
- Company-level access:
OWNER,ADMIN, orMEMBERrole in the company - Project-level access:
OWNERorADMINrole in the specific project
Project Role Permissions
| Project Role | Can Delete Project |
|---|---|
OWNER |
✅ Yes |
ADMIN |
✅ Yes |
MEMBER |
❌ No |
CLIENT |
❌ No |
COMMENT_ONLY |
❌ No |
VIEW_ONLY |
❌ No |
Deletion Process
When you delete a project, Blue performs the following steps:
- Validation: Verifies the project exists and you have permission to delete it
- Backup: Saves project data to a trash table for potential recovery (internal use only)
- Immediate deletion: Removes the project from the active database
- Notifications: Updates related systems and notifies relevant services
- Background cleanup: Asynchronously removes all associated data
Error Responses
Project Not Found
{
"errors": [{
"message": "Project not found",
"extensions": {
"code": "PROJECT_NOT_FOUND"
}
}]
}
Insufficient Permissions
{
"errors": [{
"message": "You are not authorized to delete this project",
"extensions": {
"code": "UNAUTHORIZED"
}
}]
}
Important Notes
- Deletion is cascading - all project data is removed
- The process is asynchronous - large projects may take time to fully clean up
- Consider using archive instead of delete if you might need the project later
- Deleted projects are saved internally for recovery purposes but are not accessible via the API