---
title: "Configure task scheduling"
canonical: "https://support.appfire.com/space/DLP/2212004857/Configure%20task%20scheduling"
format: markdown
---
> Macro (aura-html)
> 📝 On this page, you will find the information about the **Task scheduling mode**.
> 📝
> 📝 To read about **Task period alignment, **go to [https://appfire.atlassian.net/wiki/spaces/DLP/pages/2212233858](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2212233858) page.
The scheduling option on the [box type](https://appfire.atlassian.net/wiki/pages/createpage.action?spaceKey=dlpdraft&title=NEW%20Box%20types&linkCreation=true&fromPageId=2024277770) configuration page determines how new tasks added to the box will interact with the scheduling mechanism, including factors like task dependencies and parent/child relationships.
This option sets a default configuration for all newly created boxes of that specific box type.
## Security and access
Keep in mind:
- A box type contains the default settings applicable to multiple boxes (all boxes of a given type). Those settings are adjusted in the BigPicture Administration.
- Box configuration refers to the settings of a single, individual box. They are dependent on the box type settings.
The table presents what you can configure at the box type and box levels.
| **Area** | **Security and access** | **What can be configured** |
| --- | --- | --- |
| Box type configuration | Only a user with the App admin security role can access and manage the box type configuration.
Go to the** App Administration** >** Box type **>** choose the box type you want to edit** >** Tasks **>** Scheduling**.
 | For a box type (all boxes of a given type), you can configure:
- Default box scheduling mode |
| Box configuration | Only a user with a minimum box admin security role can access and manage the box configuration.
Go to **box configuration** >** Tasks **>** Scheduling**.
 | For a particular box, you can configure:
- Box scheduling mode |
## Default scheduling mode
> ℹ️ When the scope definition of a box type is set to **Sub-scope**, the scheduling mode of the new box is inherited from the parent (upper-level) box and cannot be modified.
> ℹ️
> ℹ️ Switching the box type settings from the **Sub-scope** to **Own** does not affect the existing boxes. If a box was created when the scope definition of the box type was set to the **Sub-scope**:
> ℹ️
> ℹ️ - you cannot change that scope,
> ℹ️ - you cannot modify its default scheduling mode.
The default scheduling mode is **auto basic** and applies only to newly created tasks (tasks that were added to the box's scope for the first time.) If a task was added to the scope prior to the scheduling mode change, its existing mode will remain unchanged.
For Boxes with the **Own** scope, you can choose from four available [scheduling modes](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211580702):
- Auto basic
- Auto bottom-up
- Auto top-down
- Lock
- Manual
## Add a new task to the scope of a box
You can add a new task to the scope of a box in the following ways:
- use the **+Task** button in the Scope, Gantt, Board, Risks, and Resources modules.
- change the [scope definition](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211646406) of a box.
Jira sprint, version, component, and project always have the default scheduling mode set to manual, regardless of the scheduling mode you set as default.
> ℹ️ We recommend using the **Manual** scheduling mode to ensure that your task will not be automatically rescheduled based on the configuration of structure builders and dependencies. You can enable automation anytime, but you might not be able to easily revert changes.