> ## 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. # Installation > By the end of this tutorial, you will have Nextedy RISKSHEET installed in your Siemens Polarion ALM environment with the administration pages accessible and the Risksheet topic available for your project. 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

Last reviewed on {formatted}

; }; ## What You Will Achieve By the end of this tutorial, you will have Risksheet installed in your Siemens Polarion ALM environment with the administration pages accessible and the Risksheet topic available for your projects. You will be ready to enable Risksheet in a project and create your first risk analysis document. ## Prerequisites Before you begin, confirm the following: * [Supported Polarion ALM](/overview/resources/polarion-version-support) version installed and running * You have **administrator access** to the Polarion server (file system access and Polarion admin role) * You have the Risksheet installation package (`.zip` or `.jar` file) provided by Nextedy * You have a valid Risksheet license file (or plan to use the evaluation period) * Server restart capability (you will need to restart Polarion during the process) If you are adding Risksheet to a Polarion instance that already has projects, you will need to enable Risksheet in each project individually after the server-level installation. This tutorial covers the server-level installation. See [Add Risksheet to Existing Project](/risksheet/guides/administration/project-setup) for project-level setup. ## Installation Steps ### Step 1: Deploy the Plugin Files Copy the Risksheet plugin files to your Polarion extensions directory: ```text theme={null} [POLARION_INSTALL]/polarion/extensions/ ``` Place the Risksheet `.jar` files and any accompanying resources into this directory. If you received a `.zip` archive, extract its contents into the extensions folder. You should see the Risksheet plugin files listed in the extensions directory alongside any other Polarion extensions you have installed. ### Step 2: Delete the Configuration Cache This step is critical. Remove the cached Polarion configuration directory to ensure Polarion detects the new plugin: ```text theme={null} [POLARION_INSTALL]/data/workspace/.config ``` Delete the entire `.config` directory (not just its contents). Polarion will regenerate this directory on the next startup. Failing to delete `[POLARION_INSTALL]/data/workspace/.config` is the most common cause of installation problems. If you skip this step, the Risksheet **Setup** and **License** pages in Polarion administration will appear empty with no content. This step is required both for fresh installations and for updates to newer versions. ### Step 3: Restart Polarion Restart the Polarion server to load the new plugin: diagram Depending on your environment, use the appropriate service command: * **Linux**: `systemctl restart polarion` or the Polarion-provided startup script * **Windows**: Restart the Polarion service through the Services management console Wait for Polarion to fully start. The startup process may take several minutes depending on your server configuration and the number of installed extensions. ### Step 4: Verify the Setup Page Loads After Polarion restarts, log in as an administrator and navigate to: **Administration > Nextedy Risksheet > Setup** You should see the Risksheet Setup page render with content (controls, status indicators, and template management options). This confirms that the plugin loaded successfully and the configuration cache was rebuilt during startup. If the Setup page loads but shows no content, the `.config` directory was not fully removed in Step 2. Stop Polarion, delete the `.config` directory again, and restart. Provisioning solution templates (functional safety, FMEA, HARA, TARA, STRIDE, and similar starting points) is covered separately in [Evaluate Risksheet](/risksheet/getting-started/evaluation), where you can install a ready-to-use sample project and explore solution templates. Risksheet documentation always recommends starting from a solution template that matches your industry or methodology, then modifying its sheet configuration to fit your process — never start from a blank sheet configuration. ### Step 5: Verify the License Page Navigate to **Administration > Nextedy Risksheet > License** to verify your license status. You should see: * Your license type (Standard or Evaluation) * The number of server users detected * The expiration date (if applicable) * The license status showing as **Active** If the License page appears empty with no content, return to Step 2 and confirm the `.config` directory was fully deleted, then restart Polarion again. Risksheet respects Polarion ALM licensing. Risksheet license affects only the Risksheet editor itself. Users with an active (named/concurrent) license can actively edit data on the Risksheet. The rest of the server users get a Reviewer license. Reviewer licenses are read-only. ### Step 6: Add the Risksheet Topic to Your Project Views To make Risksheet accessible inside a project, navigate to that project and open **Administration > Topics**. Add the Risksheet topic entry to your project's navigation views (hats): ```xml theme={null} ``` This entry must be present in every Polarion view (hat) where users need to access Risksheet. Without it, users assigned to that view will be redirected to the space home page when they attempt to open a Risksheet document. If your Polarion instance uses multiple views (hats) for different roles, add the `` entry to **each view** that should have Risksheet access. Missing the topic in a specific view is the most common reason users report that Risksheet is not working for them while it works for others. You should see "Risksheet" (or your configured tool name) appear in the project navigation sidebar after saving the Topics configuration. ### Step 7: Verify the Installation Open a project where you added the Risksheet topic and click the **Risksheet** entry in the navigation sidebar. You should see the Risksheet home page showing: * Available folders for creating new risk documents * Template selection options * Any existing risk analysis documents in the project If you are redirected to the space home page instead, verify the topic configuration in Step 6 for the view your user account is assigned to. ## Post-Installation Checklist | Item | How to Verify | | ------------------------------------------- | ---------------------------------------------------------------- | | Plugin files deployed to `extensions/` | Files visible in `[POLARION_INSTALL]/polarion/extensions/` | | `.config` directory deleted and regenerated | Folder reappears after restart | | Polarion restarted successfully | Polarion logs show clean startup | | Setup page loads with content | **Administration > Nextedy Risksheet > Setup** renders controls | | License page shows active license | **Administration > Nextedy Risksheet > License** loads with data | | Risksheet topic added to project views | Risksheet visible in project sidebar | | Risksheet home page accessible | No redirect to space home | ## Next Steps With Risksheet installed and the administration pages accessible, proceed to: * [Evaluate Risksheet](/risksheet/getting-started/evaluation) -- install the sample project and explore solution templates * [Basic Configuration](/risksheet/getting-started/basic-configuration) -- customize column layouts and risk parameters in the sheet configuration * [Understanding the Interface](/risksheet/getting-started/understanding-interface) -- learn the grid navigation and editing controls