---
title: "Sub-scope"
canonical: "https://support.appfire.com/space/SPM/1918799715/Sub-scope"
format: markdown
---
> Macro (aura-html)
## Sub-scope (old navigation)
Expand
## About the sub-scope definition type
When the scope definition is set to **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](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918765868)). It can be automatically synced with a value of a selected field.
The boxes with sub-scope display the tasks already added to a higher-level box with own scope. Any task added to a box with a sub-scope is automatically added to an upper-level box with the own scope.
> ℹ️ Box configuration refers to the settings of a single, individual box. They are dependent on the box type settings. See the [https://appfire.atlassian.net/wiki/spaces/SPMDRAFT/pages/1858864073](https://appfire.atlassian.net/wiki/spaces/SPMDRAFT/pages/1858864073) page for more information.
## Scope definition elements
### Scope of the context box
The scope of the box you're configuring can be managed at the top part of the page.> Macro (excerpt-include)
### Scope of the sub-boxes
> Macro (excerpt-include)
> Macro (excerpt-include)
### Switch between levels of child boxes
> Macro (excerpt-include)
### Basic info and status of child boxes
> Macro (excerpt-include)
## Security roles
Users of sub-boxes with sub-scope can make any changes that match their permissions in a given sub-box, even if they lack appropriate permissions to their own scope box.
Those operations include:
- Create tasks
- Add tasks to own scope as manually added
- Delete tasks
- View tasks
## Automatic timeboxes (synchronize Jira sprints)
Go to the [https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918766987](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918766987) page to find out more about synchronizing Jira sprints
## Sub-scope (new navigation)
Expand
## About the sub-scope definition type
When the scope definition is set to **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](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918765868)). It can be automatically synced with a value of a selected field.
The boxes with sub-scope display the tasks already added to a higher-level box with own scope. Any task added to a box with a sub-scope is automatically added to an upper-level box with the own scope.
> ℹ️ Box configuration refers to the settings of a single, individual box. They are dependent on the box type settings. See the [https://appfire.atlassian.net/wiki/spaces/SPMDRAFT/pages/1858864073](https://appfire.atlassian.net/wiki/spaces/SPMDRAFT/pages/1858864073) page for more information.
## Scope definition elements
### Scope of the context box
The scope of the box you're configuring can be managed at the top part of the page.
Scope information of boxes nested under the box you are currently configuring can be found at the bottom part of the page:
### Scope of the sub-boxes
Scope information of boxes nested under the box you are currently configuring can be found at the bottom part of the page:
> Macro (excerpt-include)
### Switch between levels of child boxes
> Macro (excerpt-include)
### Basic info and status of child boxes
> Macro (excerpt-include)
## Security roles
Users of sub-boxes with sub-scope can make any changes that match their permissions in a given sub-box, even if they lack appropriate permissions to their own scope box.
Those operations include:
- Create tasks
- Add tasks to own scope as manually added
- Delete tasks
- View tasks
## Automatic timeboxes (synchronize Jira sprints)
Go to the [https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918766987](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918766987) page to find out more about synchronizing Jira sprints