Skip to main content

Connection Between Project Types and Templates

This article explains how Project Templates are linked to Project Types in Authorium and what this relationship means for creating and maintaining projects.

How Templates Are Associated with Project Types​

Each Project Type in Authorium is linked to a specific Project Template. This association determines the structure, forms, stages, and workflows applied whenever a new project is created under that type. For example, a “Contracting” Project Type might include specific evaluation steps or submission forms. This connection ensures standardization across projects of the same type and simplifies the setup for users.

One-to-One vs. Many-to-One Relationships​

There are two possible relationships between Project Types and Templates. Understanding which applies helps clarify how templates should be managed and reused.

One-to-One (1:1)​

In a 1:1 configuration, each Project Type is tied to a single specific template:

  • Projects of that type always use the same template.
  • Updates to the template automatically apply to future projects of that type.
  • Best suited for standardized workflows with minimal variation.

Many-to-One (Many:1)​

Some systems support more flexible relationships:

  • Shared Templates Across Types: Multiple Project Types may reuse the same core template. This reduces duplication but requires generic design.
  • Multiple Templates per Type: A single Project Type might allow users to choose from several templates during project creation, supporting variation but increasing management complexity.
Note

Authorium currently supports a 1:1 model, where each Project Type is linked to one active Project Template.
To support variations, you can create separate Project Types or manage versions of the template manually.

Implications for Management​

  • The 1:1 model simplifies consistency but may require duplicating types to support variations.
  • When reusing templates, ensure they are flexible enough to meet each use case.
  • Establish naming conventions and clear documentation to prevent misapplication or confusion.

See Also​

To complement your knowledge of this process, check the following pages: