---
title: "Scope types"
canonical: "https://support.appfire.com/space/DLP/2211126618/Scope%20types"
format: markdown
---
> Macro (aura-html)
## About scope types
A scope type is set in **Administration **>** Box types** settings. A box type contains the default settings applicable to multiple boxes (all boxes of a given type). Boxes can be created with different types of scope. Those settings determine how a box can be configured and what can be done when defining a scope.
There are three different scope types:
- Own-scope
- Sub-scope
- None (aggregations only)
## 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. Go to the [https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211646406](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211646406) page to learn more about scope definition settings at the box level.
The table presents what you can configure at the box type level.
| **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** >** Scope definition**.
 | For a box type (all boxes of a given type), you can configure:
- Scope type |
## Own-scope
The box scope has a separate task structure and is a scope base for sub-scopes. Automatic rules can sync it. Use it when you want to define and extend the scope of a box by selecting tasks from Jira and connected tools. See the [https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211713546](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211713546) page to learn more about box configuration.
## Sub-scope
The box scope is always a subset of the scope already defined at an upper level of the box hierarchy (the upper-level box must have own-scope). It can be automatically synced with a value of a selected field.
See the example
Example: A sub-scope box may be a parent when the box type is SAFe® Agile Release Train (ART). This box type comprises three levels of boxes, and the following structure is possible:
*First-level box: own scope*
*Second-level box: sub-scope*
*Third-level box: sub-scope *
The second-level **sub-scope** box is a parent for the third-level box, but the first-level box is always set to **own-scope**).
See the [https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211648009](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211648009) page to learn more about box configuration.
### Sub-scope definition template
When you select the sub-scope in the box type settings, a new section **Sub-scope definition template** appears, and you can choose the field to synchronize with it.
See the example
For example, the 'Program Increment 1' subbox of the 'PI planning (Smart house project)' has the scope type set to sub-scope. A box admin cannot change the scope of the 'Program increment' but can configure the synchronization of the 'Iteration 1.1' subbox.
## None (aggregations only)
The box scope cannot be defined. Currently, you can only use such a box to calculate respective aggregates in the box hierarchy (visible in the Overview module). Use this setting to organize boxes into portfolios, programs, etc. The scope is always a sum of the scopes of the sub-boxes in the box hierarchy. For none-scope boxes, the **Scope definition** page in the box configuration is unavailable.
See the [https://appfire.atlassian.net/wiki/spaces/DLP/pages/2212333684](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2212333684) page to learn more about box configuration.