> ## Documentation Index
> Fetch the complete documentation index at: https://learn.nextedy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Project Templates

> Set up and deploy Nextedy RISKSHEET project templates to standardize risk analysis configuration across new Polarion projects, with support for multiple configurations per project and document-scoped work item types.

export const LastReviewed = ({date}) => {
  if (!date) return null;
  const formatted = new Date(`${date}T00:00:00Z`).toLocaleDateString("en-US", {
    year: "numeric",
    month: "long",
    day: "numeric",
    timeZone: "UTC"
  });
  return <p className="mt-10 text-sm text-gray-400 dark:text-zinc-500 not-prose">
      Last reviewed on {formatted}
    </p>;
};

## Prerequisites

* Polarion administrator privileges
* Access to the Risksheet administration interface

<Steps>
  <Step title="Install Default Templates">
    Risksheet ships with predefined project templates that provide ready-to-use configurations. To install them:

    1. Navigate to **Administration > Nextedy Risksheet**.
    2. Select the **Setup** option.
    3. Click **Install Templates**.

    The system installs two starter templates:

    | Template           | Purpose                                                                             |
    | ------------------ | ----------------------------------------------------------------------------------- |
    | Standard Risksheet | General-purpose FMEA risk analysis with severity, occurrence, and detection columns |
    | HARA Template      | Hazard Analysis and Risk Assessment template aligned with ISO 26262 workflows       |

    <Tip title="Template Overwrite Behavior">
      Re-installing templates overwrites previous versions. The system removes old template data and performs a clean installation. This is safe for updating templates but will discard any manual customizations made directly to the template files. Installation is atomic -- it either completes fully or rolls back on error.
    </Tip>
  </Step>

  <Step title="Create a New Project from a Template">
    1. In Polarion, go to **Administration > Projects > Create Project**.
    2. Select either the standard Risksheet or HARA template from the template list.
    3. Provide a project name and identifier.
    4. Complete the project creation wizard.

    The new project inherits the full Risksheet configuration including column layouts, formulas, cell decorators, enums, and risk rating scales.
  </Step>

  <Step title="Configure Template Paths">
    Control where users can create new risk documents within a project by configuring template paths. In the project-level Risksheet properties, set:

    ```
    nextedy.risksheet.risksheetTemplatePath=Risks/Risk Specification
    ```

    To allow multiple document locations, separate paths with commas:

    ```
    nextedy.risksheet.risksheetTemplatePath=Risks/Risk Specification,Risks/HARA Documents,Safety/Assessments
    ```

    The default template path is `Risks/Risk Specification`. These paths control which folders appear in the Risksheet home view when creating new documents.
  </Step>
</Steps>

## Configuration Inheritance

Risksheet uses a template-to-document inheritance model for configuration:

<Frame>
  <img src="https://mintcdn.com/none-17b4493f/yWl5nA2D0IzEnZC1/risksheet/diagrams/guides/integration/project-templates/diagram-1.svg?fit=max&auto=format&n=yWl5nA2D0IzEnZC1&q=85&s=c5351b545f89c75e3019b7b03351918a" alt="diagram" style={{ maxWidth: "520px", width: "100%" }} width="520" height="220" data-path="risksheet/diagrams/guides/integration/project-templates/diagram-1.svg" />
</Frame>

When Risksheet loads configuration for a document, it searches in this order:

1. **Document attachment** -- a sheet configuration attached directly to the LiveDoc
2. **Template inheritance** -- the sheet configuration from the document's parent template

The `source` and `templateName` properties in the loaded configuration indicate where the config was found. The `fromTemplate` flag is `true` when configuration was inherited rather than directly attached.

<Tip title="Template vs. Reuse">
  Both Polarion template-based document creation and the Polarion "Reuse" function work with Risksheet. The template approach is recommended because configuration changes to the template propagate to all new documents automatically. The Reuse approach also works but does not propagate template changes.
</Tip>

<Steps>
  <Step title="Customize the Tool Name">
    Organizations can rebrand the tool name displayed in the Risksheet UI:

    | Property                 | Default         | Example                    |
    | ------------------------ | --------------- | -------------------------- |
    | Tool name                | `Risksheet`     | `FMEA Tool`, `Risk Matrix` |
    | Document name (singular) | `Risk Analysis` | `Risk Assessment`          |
    | Document name (plural)   | `Risk Analyses` | `Risk Assessments`         |

    Configure these through Risksheet project properties in **Administration > Nextedy Risksheet > Project Properties**.
  </Step>

  <Step title="Use Multiple Configurations per Project">
    Risksheet supports multiple distinct configurations within a single project. Each LiveDoc document can have its own sheet configuration attached, or inherit from different templates.

    To set up multiple configurations:

    1. Create separate LiveDoc templates for each risk analysis type (e.g., FMEA, HARA, TARA).
    2. Attach a unique sheet configuration to each template.
    3. When creating new documents, select the appropriate template.

    <Tip title="No Mandatory Work Item Types">
      Risksheet has no required specific fields or work item types. You can configure it to work with any custom work item type in your Polarion project. The default demo uses Risk item types, but the tool is fully configurable for any work item type. This makes integration with existing project templates straightforward.
    </Tip>
  </Step>

  <Step title="Scope Work Items to Documents">
    To restrict linked items to a specific LiveDoc rather than the entire project, use the `document` property in your `dataTypes` configuration:

    ```yaml theme={null}
    dataTypes:
      task:
        type: measure
        role: has_measure
        document: Risks/FMEA Measures
    ```

    This ensures that when users search for linked items, only work items from the specified document are shown. This is a common need for FMEA setups with multiple documents in the same project.

    To create new items directly within the current document, use the `createInCurrentDocument` parameter in the data type definition. This controls whether new upstream items are stored in the current document rather than at the project level.
  </Step>
</Steps>

## Verification

After completing the template setup:

1. Create a new project using your Risksheet template.
2. Navigate to the Risksheet home page within the project.
3. You should now see the configured document folders and the ability to create new risk documents.
4. Open a document and verify that column layouts, enums, and formulas match your template configuration.
5. Check the configuration editor to confirm the `templateName` field shows your template name.

## See Also

* [Set Up Global Templates](/risksheet/guides/configuration/global-templates) -- configure global template inheritance
* [Configure Template Paths](/risksheet/guides/configuration/template-path-configuration) -- manage document creation paths
* [Override Template Configuration](/risksheet/guides/configuration/document-config-override) -- customize inherited settings per document
* [Find Configuration Files](/risksheet/guides/configuration/finding-config-files) -- locate sheet configuration files in your project
* [Add Risksheet to Existing Project](/risksheet/guides/administration/project-setup) -- install into an existing project

<LastReviewed date="2026-06-24" />