---
title: "Preventing Task Deletion in BigGantt: Configuring Permissions and Security Settings"
canonical: "https://support.appfire.com/space/SUPPORT/3504308343/Preventing%20Task%20Deletion%20in%20BigGantt%3A%20Configuring%20Permissions%20and%20Security%20Settings"
format: markdown
---
This article explains how to prevent users from deleting tasks in BigGantt or reduce who can remove items from a program or box. It is intended as a reusable support reference for similar customer questions.

> ℹ️ In BigGantt, the ability to delete tasks is controlled through permissions. To remove access to deletion, lower the user’s permissions below the level that allows box content management.

# Problem

A customer is using BigGantt to manage programs and wants to stop users from deleting tasks inside a program. The question is whether the delete option can be removed or controlled.

# Short Answer

Yes. The delete option can be limited by configuring BigPicture/BigGantt box security permissions. If users should not be able to delete box contents, they must have permissions lower than **Box Editor**. If the rule should apply broadly, configure it on the **Root Box** so it cascades to other boxes as appropriate.

# How to Resolve

1. Open the relevant box in BigGantt or BigPicture.
2. Go to the box **Security Configuration**.
3. Review the permissions assigned to the affected users or roles.
4. If users should not delete tasks or other box content, assign them a permission level lower than **Box Editor**.
5. If the restriction should apply across all boxes, update the **Root Box** security settings.

> ℹ️ When responding to similar tickets, first confirm whether the customer wants to restrict deletion in a single box or across the whole structure. That determines whether the change should be made locally or at the Root Box level.

# What Support Should Tell the Customer

You can use the following response pattern:

> Yes, this can be controlled through permissions. To limit the delete option for tasks or other box contents, configure the box security settings and ensure the affected users have permissions lower than Box Editor. If you want this restriction to apply to all boxes, update the Root Box settings as well.

# Key Details to Remember

- There is no separate standalone “hide delete button” feature referenced in this case.
- The behaviour is permission-driven.
- **Box Editor** is the threshold mentioned in support guidance; users below that level should not be able to delete box contents.
- **Root Box** settings are relevant when the customer wants a global rule.

# Known Resolution Pattern from the Ticket

In the referenced case, support confirmed that limiting deletion was possible through permission settings and directed the customer to the documentation for **Delete** behavior and **Security Configuration**. The guidance was to lower permissions below **Box Editor** for the relevant box, or to update the **Root Box** when the customer wanted the rule applied more broadly.

<details>
<summary>Suggested internal macro-style summary</summary>


</details>