---
title: "Sub-scope"
canonical: "https://support.appfire.com/space/BPEdc/2533589896/Sub-scope"
format: markdown
---
## 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/BPEdc/pages/2534999202)). It can be automatically synced with a value of a selected field.

<details>
<summary>See the example</summary>

**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**).
</details>

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/BPEdc/pages/2534278271/000+Scope+types?force_transition=71b47b01-cff8-41bd-bee2-c5d1099fd965](https://appfire.atlassian.net/wiki/spaces/BPEdc/pages/2534278271/000+Scope+types?force_transition=71b47b01-cff8-41bd-bee2-c5d1099fd965) page for more information.

![image](media://b0a42799-9350-45a4-b525-0245ef3a5294)

![image](media://580f6404-135c-4da2-bbf3-156183d09845)

## 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

<details>
<summary>See the example</summary>

If Angela is a Viewer in the Program-type Box ("own" scope) but is an Admin in an Iteration sub-box ("Sub" scope), she can execute all Admin operations on the Iteration tasks. 

This means she effectively has Admin powers over some tasks from the Program-type box.

![image2021-5-14_9-17-21.png](media://7d9019cc-5c1e-45b0-8e19-475a97b306b3)
</details>

## Automatic timeboxes (synchronize Jira sprints)

Go to the [https://appfire.atlassian.net/wiki/spaces/BPEdc/pages/2534507931](https://appfire.atlassian.net/wiki/spaces/BPEdc/pages/2534507931) page to find out more about synchronizing Jira sprints