---
title: "Scope types"
canonical: "https://support.appfire.com/space/SPM/1918766536/Scope%20types"
format: markdown
---
> Macro (aura-html)

## Scope types (old navigation)

<details>
<summary>Expand</summary>

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

![image-20250313-121926.png](media://5548f97c-bd97-4f0e-bf74-4e80cd98be90)

## 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/SPM/pages/1918634319](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918634319) 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.<br>Go to the** App Administration** >** Box type **>** choose the box type you want to edit** >** Tasks** >** Scope definition**.<br>![image-20250313-121926.png](media://5548f97c-bd97-4f0e-bf74-4e80cd98be90) | For a box type (all boxes of a given type), you can configure:<br>- 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/SPM/pages/1918765868](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918765868) 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 [https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918799715](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918799715) 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.

![Screenshot of the Scope definition page in BigPicture Administration for a sub-scope box.](media://b7074ade-ddda-45dc-b798-188dbf3909c7)

## 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/SPM/pages/1918537743](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918537743) page to learn more about box configuration.
</details>

## Scope types (new navigation)

<details>
<summary>Expand</summary>

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

![work-items-scope-type.png](media://7af81751-43df-4cee-98dc-97b0e6267bf7)

## 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/SPM/pages/1918634319](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918634319) page to learn more about scope 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.<br>Go to the** App Administration** >** Box type **>** choose the box type you want to edit** >** Tasks** >** Add work items from Jira**.<br>![work-items-scope-type.png](media://7af81751-43df-4cee-98dc-97b0e6267bf7) | For a box type (all boxes of a given type), you can configure:<br>- 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/SPM/pages/1918765868](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918765868) 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 [https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918799715](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918799715) 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.

![sub-scope-definition-template.png](media://92a73e98-cf2c-451a-9a38-0642118e4d7d)

## 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 **Work items from Jira** page in the box configuration is unavailable. 

See the [https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918537743](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918537743) page to learn more about box configuration.
</details>