Defines an individual space blueprint on your site.

This object comprises a set of key/value pairs that function as specifications or instructions for creating new spaces from this blueprint.

Keys in this object:

• name
• description
• blueprintSpaceKey
• blueprintFields
• spaceName
• spaceKey
• spaceCategories
• spaceDescription
• access

Defines the name of a space blueprint.

The string value assigned to this key will be the name of the blueprint as it appears in the Blueprints Menu.

Describes a space blueprint.

The string value assigned to this key will be the description of the blueprint as it appears directly below the blueprint's name/title in the Blueprints Menu.

Indicates a blueprint source space.

The string value assigned to this key is the space key of the source space that will serve as the template for new spaces generated from this blueprint.

Lists all custom substitution fields included in the blueprint.

The array assigned to this key will comprise the names of all custom substitution fields that will be a part of this blueprint.

These are the fields blueprint users will be asked to provide values for whenever they create new spaces from this blueprint.

Each field name listed here will map to a blueprint field object defined in the JSON file. The substitution field name as it occurs in this array will match the corresponding blueprint field object's id key, which will also match the substitution field name as it occurs in the blueprint source page (enclosed in double brackets: [[substitution-field-name]]).

Defines how new spaces generated from a space blueprint will be named.

The string value of this key will be the name of a new space generated via blueprint.

It is possible and indeed recommended to incorporate at least one custom substitution field into this key's value so that each new space created from this blueprint will have a unique name from the start, without requiring any extra input from the user who is creating the new space. (Built-in substitution fields, however, are not supported here.)

Defines the space key for new spaces generated from a blueprint.

The string value will be the space key of any new spaces generated via blueprint.

As with the spaceName key, it is possible and indeed recommended to incorporate at least one substitution field into this key's value so that each new space created from this blueprint will have a unique key from the start. Otherwise, when blueprint users try to create new spaces from blueprint, they will be prompted to go back and manually enter a unique space key to avoid naming collisions.

Adds labels to new spaces generated from a blueprint.

The string value of this key is a comma-separated list of labels that will automatically be added to any new spaces created from the blueprint.

Custom substitution fields are allowed. The [[CURRENT DATE]], [[SPACE KEY]], and [[SPACE NAME]] built-in substitution fields are supported; however, we do not recommend using [[SPACE NAME]] as doing so will often result in errors (as labels cannot contain spaces and space names often consist of more than one word).

Leave blank or remove this key/value pair from the object altogether if you do not want to add labels to the new spaces.

Assigns a permission scheme to new spaces created from a blueprint.

The array assigned to this key will comprise the name of one or more permission settings objects enumerated in the accessLists array. Defining these objects will give blueprint authors tight control over who can view and edit the new spaces.

Leave this array empty if you wish to restrict access to new spaces to everyone except the space creator.

Lists all permission schemes that may be applied to space blueprints.

Each item in this array is an object that defines space permission settings.

The objects in this list are what the items in spaceBlueprints[i].access may reference.

Defines a set of space permissions that may be applied to new spaces.

This object comprises two key/value pairs that hold information about who can view, access, or administer spaces created from a blueprint.

Keys in this object:

• name
• permissions

Defines the name of a space permissions object whose properties can be applied to new spaces.

The string value assigned to this key is simply the name of the containing permission settings object.

Any instances of spaceBlueprints[i].access that reference this object will do so by this name.

Lists every type of user in the accessLists[m] permission scheme who will have some level of access to new spaces.

Each item in this array is an object that defines specific permission settings for one particular user or group.

Defines space permissions for a particular user or group.

This object comprises a set of key/value pairs that hold information about how a particular user or group may interact new spaces created from any blueprint that references accessLists[m].

Keys in this object:

• type
• name
• grant

Specifies the type of user for whom space permissions are being set.

The string value of this key will indicate whether accessLists[m].permissions[n] is defining space permissions for a Confluence user group, an individual user, or anonymous visitors.

Valid values:

• group
• user
• anonymous

Specifies the name of the user or group for whom space permissions are being set.

The string value of this key will be the name of a user group, an individual's username, or "anonymous", depending on the value of accessLists[m].permissions[n].type.

It is possible to use custom substitution fields for this value, which blueprint users can supply at the time new spaces are created.

Lists all of the specific space permissions granted to the user or group defined in accessLists[m].permissions[n].

Each item in this array is a string value that corresponds with a specific type of access to a space an individual or group may possess.

See valid space permissions array for a complete list of valid values.

Lists all of the different types of permissions that can be granted to a user or group in a new space created from a blueprint.

For your convenience, all of the valid values you may use to populate accessLists[m].permissions[n].grant are listed here.

We recommend keeping this array as it is and not removing any items so that you will always have a complete list to draw from:

• ALL
• VIEWSPACE
• EDITSPACE
• REMOVEPAGE
• EDITBLOG
• REMOVEBLOG
• COMMENT
• REMOVECOMMENT
• CREATEATTACHMENT
• REMOVEATTACHMENT
• SETPAGEPERMISSIONS
• EXPORTSPACE
• SETSPACEPERMISSIONS

Defines an individual page blueprint on your site.

This object comprises a set of key/value pairs that function as specifications or instructions for creating new pages from this blueprint.

Keys in this object:

• name
• description
• spaceKey
• pageTitle
• blueprintFields
• includeChildren or type
• filterGroup
• multiselect
• addLabels
• visibility

Note   : Blueprint Maker version 2.0 changed the includeChildren field to type

Defines the name of a page blueprint.

The string value assigned to this key will be the name of the blueprint as it appears in the Blueprints Menu .

Describes a page blueprint.

The string value assigned to this key will be the description of the blueprint as it appears directly below the blueprint's name/title in the Blueprints Menu.

Indicates the space that holds a page blueprint's source page.

The string value will simply be the key of the space that is holding the blueprint source page.

Another way to think about it: The space indicated here is where the value of pageBlueprints[j].pageTitle lives.

Identifies a source page that will be used as the template for a blueprint.

The string value assigned to this key will be the name of the source page that will be copied whenever new pages are generated from a blueprint.

It is possible and indeed recommended to incorporate at least one custom substitution field into this key's value so that each new page created from this blueprint will have a unique name from the start, without requiring any extra input from the user who is creating the new space.

Of the built-in substitution fields, [[CURRENT DATE]], [[SPACE KEY]], [[PARENT PAGE ID]] and [[SPACE NAME]] are supported.

Lists all custom substitution fields included in the blueprint.

The array assigned to this key will comprise the names of all custom substitution fields that will be a part of this blueprint.

These are the fields blueprint users will be asked to provide values for whenever they create new pages from this blueprint.

Each field name listed here will map to a blueprint field object defined in the JSON file. The substitution field name as it occurs in this array will match the corresponding blueprint field object's id key, which will also match the substitution field name as it occurs in the blueprint source page (enclosed in double brackets: [[substitution-field-name]]).

Indicates whether to include a blueprint source page's child pages when generating new pages from a blueprint.

The boolean value assigned to this key will specify whether a source page's children will be a part of the blueprint, or just the source page indicated in pageBlueprint[j].pageTitle.

Defaults to false if not indicated.

As of Blueprint Maker version 2.0, the type field replaces the includeChildren field.

The type field indicates what kind of page Blueprint is to be created. If you simply want a single page created from a Blueprint (and no children) then enter page. If you would like to a page and its children (child pages) then enter tree.

If you would like to create a Live Blueprint, where content can be refreshed after creation of the Blueprint, then enter live.

Valid values:

• page
• tree
• live

This field lets users list in which spaces they want this Page Blueprint to be made available.

Add the space category label to this list if you want the Page Blueprint to be available in the menu of available Blueprints for use in a space.

Not including this field will mean the Page Blueprint is available to all spaces.

Lists every substitution field used in your Blueprints.

Each item in this array is an object that defines one substitution field.

A substitution field is defined here as an object with properties.

A substitution field object comprises a set of key/value pairs that function as specifications or instructions for creating new spaces from this blueprint.

Keys in this object:

• id
• name
• required
• type
• filterGroup
• addLabels
• multiselect
• values
• helpText
• placeholder
• validation

The id field corresponds with the substitution field used on your Page and Space Blueprints. For example, if you used [[team-member-name]] on a Page Blueprint, then that is the id value used here, minus the brackets.

The id field is the unique identifier for your substitution field. It is typically a string of text, and always corresponds with the field used on your Page and Space Blueprints.

The required field, if set to true, sets a flag for this substitution field that forces users to enter a value during the Blueprint creation process. This means a page or space cannot be created until the user enters a value for this field.

Possible values are:

• true
• false

The type field defines the field length or field type (if a file upload). The field length is useful for indicating to your users if there is an expectation of a short value being entered, such as a single word name, or a long value, such as a sentence or two.

If desiring a file upload, set the type to file and the wizard will allow users to attach a file during the Blueprint creation process.

For a picklist of options , enter list and then use either the filterGroup or values field.

Valid values:

• default
• short
• medium
• long
• file
• list

When you set your type to "list" and addLabels to true, then the options in your values array will be used in the picklist and applied to the resulting page as labels. Read more about Applying Labels via Blueprint.

Possible values are:

• true
• false

If your blueprintField type is set to "list" to use a list of values (or filterGroup) as an array, then set multiselect to true to allow users to select more than one option in the picklist.

Possible values are:

• true
• false

With a type set to "list", then define the picklist options in an array of values here. This is a comma-delimited set of text, each enclosed in quotation marks.

Note 1: if addLabels is true, then the options in the values array must be valid Confluence labels. (if not, an error will occur).

Note 2: if filterGroup and values are both defined, the options will use the filterGroup Filters (in Targeted Search) and ignore the values options.

A list of the Confluence and app metadata packages to be included during the creation of a Space Blueprint.

We recommend keeping this array as it is and not removing any items in order to ensure successful Blueprint creation. The default list items are:

• atlassian.confluence.*

• com.brikit.*

A list of the app metadata packages to be included during the creation of a Page Blueprint.

We recommend keeping this array as it is and not removing any items in order to ensure successful Blueprint creation. The default list item is:

• com.brikit.*