---
title: "Populate a box with tasks (scope definition)"
canonical: "https://support.appfire.com/space/BGc/3540615567/Populate%20a%20box%20with%20tasks%20(scope%20definition)"
format: markdown
---
> Macro (aura-html)
## About box scope
The box scope is a defined collection of tasks. Tasks can be added to the scope manually or automatically synchronized with Jira or connected tools such as Trello.
In the scope definition, you can specify what range of tasks is included in the scope of a given box (or a sub-box) - those are the tasks you will be able to work on in the App (visualize them on a Gantt chart, manage risks, distribute workload, etc.). You can include multiple Jira projects, simultaneously include tasks bfrom different external tools (such as Trello and Jira), or include only some tasks that meet your particular specifications. The flexibility of the setup ensures that a box can be configured to contain exactly the tasks you need to fit your work.
Less frequently used settings have been hidden under **Advanced configuration**.
There are three different scope types (those settings are [adjusted for a box type](https://appfire.atlassian.net/wiki/spaces/BGcDRAFT/pages/3538525607)):
- [Own-scope](https://appfire.atlassian.net/wiki/spaces/BGc/pages/3540451996)
- [Sub-scope](https://appfire.atlassian.net/wiki/spaces/BGc/pages/3540419235)
- [None (aggregations only)](https://appfire.atlassian.net/wiki/spaces/BGc/pages/3540287929)
See the video explaining the scope definition.
## 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 BigGantt Administration. See the [https://appfire.atlassian.net/wiki/spaces/BGcDRAFT/pages/3538525607](https://appfire.atlassian.net/wiki/spaces/BGcDRAFT/pages/3538525607) page for more information.
- 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 on the box configuration page.
| **Area** | **Security and access** | **What can be configured** |
| --- | --- | --- |
| Box configuration | Box admins, Jira admins, and BigGantt admins can access and manage the box configuration.
There are a few ways to access the **Scope definition** page of an individual box.
 | For a particular box, you can configure:
- Scope definition elements
- Automatic rules
- Manually added tasks
- Additional task types
- Scope of sub-boxes
- Timeboxes
- New integrations |
The sections on the Scope definition page will differ depending on the box hierarchy and the scope type (remember that every box type has a scope definition setting). A box with two levels of sub-boxes will show all possible sections.
See the example
For example, the PI planning box consists of three Program Increment sub-boxes, which consist of Iteration sub-boxes:
The tree levels in the box hierarchy are reflected on the **Scope definition** page:
As the Program Increment box type has the scope type set to 'Sub-scope,' the box admin cannot define the scope for the sub-box, and the screen shows the Iteration synchronization section only:
## Scope definition elements and actions
Visit the [https://appfire.atlassian.net/wiki/spaces/BGc/pages/3539862631](https://appfire.atlassian.net/wiki/spaces/BGc/pages/3539862631) page for more information.
## Add new integration
Visit the [https://appfire.atlassian.net/wiki/spaces/BGcDRAFT/pages/3538524239](https://appfire.atlassian.net/wiki/spaces/BGcDRAFT/pages/3538524239) page to learn how to add a new integration from the Scope definition page.