Are you planning a migration to Cloud? Make sure you don't lose your BigPicture data/configurations in the process. Check out this page for information on how to migrate BigPicture's data to Cloud. If you have any questions please email firstname.lastname@example.org
In this section, you can configure the default Task Templates for Gantt, Scope, and Calendarmodules and the inheritance mode of a given Box type.
Changing the configuration might turn off (hide) settings or features in the Box Configuration (of an individual Box) and within the Gantt/ Scope/ Calendar module.
In general, selecting an Inheritance mode determines if an upper-level Box imposes the configuration. As a result, when the Inheritance mode is set to "Inherited" or "Own with inherited," all Task templates from upper-level Boxes appear in the +Add task drop-down of the Gantt module.
The "Own" inheritance mode provides much more flexibility. It lets you define the default Task templates for all boxes of a given type when enabled. The default templates are set up when a new Box is created and can be later adjusted for each Box by a Box admin (the default configuration can be manually overwritten).
The "Inherited only" mode doesn't allow any changes directly in the sub-Box configuration - the Task templates are inherited from the upper-level Box. The Task Template page is not shown in the Box configuration. Box Admins can impact the sub-Box by editing the Task templates directly in the upper-level Box configuration (if they are also Box Admins for the upper-level Box). As a result, users cannot change some of the settings of the Box configuration since it is already preconfigured. Fewer settings to choose from make the App easier to understand.
The "Own with inherited" mode mixes the two - a Box admin can create new Task templates directly in the sub-Box configuration. Additionally, the Column Views are inherited from the upper-level Box (those views can only be edited in the upper-level Box).
Changing the Box type Inheritance mode impacts all Boxes of a given type; however, to find out how Task templates are affected in existing Boxes, go to the Default Task templates section below.
For example, Inheritance mode is set to "Own" for the Portfolio Box type, and the App Admin can create, edit, and remove templates.
The Box Admin can modify the default templates in the Box configuration > Tasks > Task Templates once a Box is created.
Let's look at a more advanced example. Eve, a Box Admin, added a new template for website projects in the Websites Program-type Box. She wants to ensure all project managers sub-Box Admins, use the same schedule template. She set the Inheritance mode of the Hybrid Box type to "Inherited only" (the Portfolio Box type is a parent type Box to the Program type):
As a result, a sub-Box Admin cannot change or remove Eve's templates in the Box configuration as the Task Templates page is hidden. The Program Increment Box configuration doesn't contain the Scope page.
If Eve changes her mind and decides to allow the sub-Box Admin to change the task templates but wants to make sure that her favorite templates from the upper-level Box are not removed, she can set the "Own with inherited" mode. This way, the inherited templates are marked with the arrow pointing upward, and the sub-Box Admin cannot remove or modify the inherited templates (a sub-Box admin can use the upper-level templates and create sub-Box templates).
Default Task Templates
Changes made to the default Task templates don't impact existing Boxes - new settings apply only to Boxes created from that point on.
You can create default templates when the inheritance mode is set to either "Own" or "Own with inherited":
Go to Task templates in the configuration to learn more about creating Tasks Templates.
The default templates are automatically set up when you create a new Box. Afterward, Box Admins can edit and remove the default templates (if the Inheritance mode allows it). Click the '+' drop-down in the Gantt/ Scope/ Calendar module to select from the list of available templates: