Scope Definition (Box Type)

Introduction

The scope type determines whether box admins can define the scope of a created box.

Scope definition	Description
Own scope	The box scope has a separate task structure and serves as a scope base for sub-scopes. Automatic rules can sync it. Use it to define and extend the scope of a box by selecting tasks from boards from monday.
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 with own scope). It can be automatically synced with long field text.
None	The box scope cannot be defined. You can use such a box for calculating respective aggregates in the box hierarchy only (visible in the Overview module). Use is to organize boxes into portfolios, programs, etc. The scope is always a sum of the scopes of the sub-boxes in the box hierarchy.

You cannot adjust settings after a box is created. Changes to the Scope definition page do NOT apply to existing boxes of a given type.

When a new box is created, the scope settings are based on the scope definition of a box type. You cannot manually override individual scope settings of an existing box.

Keep in mind:

A box type contains the default settings applicable to multiple boxes (all boxes of a given type). The settings are adjusted in Administration > Box types.
Box configuration refers to the settings of an individual box and is dependent on the box type settings.

Security and access

App admins can access and modify the default Scope definition page:

Open BigPicture.
Click the wrench button on the right side.
Select Box types.
Click on the box type name link.
Expand the Tasks section.
Go to Scope definition.

Own scope

With the own scope option, users can add boards (new tasks)?? to the scope. Box admins can adjust the scope of a particular box in the Scope definition tab of the box configuration.

In boxes with own scope, you can:

Select items from the list of available boards.
Add elements representing versions, components, sprints, projects, and backlogs by selecting appropriate task types. Those items are represented in the task hierarchy and can be used to organize the task structure.

Boxes with such a scope type show the aggregated status and time-tracking reports in the Hierarchy mode of the Overview module.

Individual boxes with own scope can be edited by:

Box admins
BigPicture admins

The quickest way to set up the scope is to use the automatic rules.

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

You can go to the configuration of a given box to adjust the box Scope definition page (functionalities are different than for a box with own scope).
A sub-scope can be bi-directionally synced with a selected field - assigning a task to a box updates the field with a respective value. Correspondingly, updating the field value of a task automatically plans the task for a box.
Depending on the settings, this can, for example, automatically adjust both the start and end dates of a task, effectively moving it on a timeline and even changing its duration.
Planning a task for a box can have a much bigger impact than putting a task in a labeled container. All scheduling rules come together to determine how time periods of tasks added to the scope react to other changes (e.g., task dependencies or parent or child relationship in the task structure).
The field-based sync is applied to tasks in the upper-level box scope (i.e., a box with own scope).
With sub-scope, a new Sub-scope definition template section appears so you can choose the field to synchronize with.

None (aggregations only)

In the none mode, the Scope definition tab is hidden, and cannot be found in Box configuration > Task as the scope is based on all sub-boxes.
You cannot see any task in any of the modules because such scope type can aggregate data as there is no need to add any tasks to the scope.
Boxes show the aggregated status and time tracking reports in the Hierarchy mode of the Overview module.