Organization-level permit blueprints

Instead of creating permit templates and categories directly within a project, you can spawn them from organization-level “blueprints”. These blueprints can be created on the organization-level Templates > Permit template blueprints and Templates > Permit category blueprints pages respectively.

Tip

This feature is only available to organizations with an Enterprise-level subscription and is only usable by organization admins.

Utilizing organization-level blueprints is useful in cases where you would like to create similar permit templates and categories across different projects in your organization. The attachments and category items created at the organization level are automatically transferred to the project when the permit template or category is created in the project, eliminating the need for repetitive work in creating them separately in each project.

Organization-level blueprints may be applied to a project in two ways.

1. When creating a project, select templates and/or categories to copy to the project via the Permit templates (Optional) and Permit categories (Optional) dropdowns.
2. To apply to an existing project, navigate to the organization-level admin Templates > Permit blueprints assignment page, select a project as well as templates and categories to copy, then click Copy templates and categories to project.

Tip

Several templates and categories may be created in a project using the same blueprint; name clashes will be avoided using a numbered suffix (e.g. “Template (2)”, “Template (3)” etc.).

Tip

Since the permit template and category blueprints are created at the organization level without any information of the user scoping in the projects to which they will be copied, no user-related properties can be copied at the organization level. Several other properties are also unavailable at the organization level. These include the following:

• Signature requirements (templates and categories)
• Permit holders (templates)
• Close-off users (templates)
• DBYD required (templates)
• Respondents (categories)
• Layers (categories)

As a result, once spawned in a project using organization-level “blueprint” quantities, project-level templates and categories will automatically be invalid and will require signature requirements to be manually assigned in order to become valid. Templates will also require at least one regular category to be valid.

Tip

Unlike with project-level permit templates, organization-level templates are always valid. Organization-level categories, as with project-level categories, require at least one non-header item to be valid.

Tip

Once spawned at the project level, permit templates and categories become independent of their organization-level blueprints. Subsequent changes to the blueprints will not propagate to the project-level templates and categories.