---
title: "Repository Installation"
slug: "repository-installation"
description: "This document shows the steps needed to install and configure the Designer Repository within Decisions. Doing this will allow teams the ability to manage changes made to projects more efficiently, and commit, revert, or rollback changes to a project as needed."
updated: 2025-09-03T17:37:41Z
published: 2025-09-03T17:37:41Z
---

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

# Repository Installation

Important Considerations

- It is recommended that the Repository server's version match the version of its connected dev/prod server. For example, install a v9 Repository for a v9 Standard Server.
- A Repository server cannot be installed as a server in a cluster or as a tenant in versions that support Multi-Tenancy.
- Firewall Configuration Required
  - Ensure the firewall ports and rules are configured to allow the Repository Server to send and receive communications with the Development Server.
  - Refer to [Microsoft's documentation on configuring Windows Firewall rules](https://learn.microsoft.com/en-us/windows/security/operating-system-security/network-security/windows-firewall/) for detailed instructions.

---

## Overview

This article explains how to install a [Repository](/v8/docs/repository-overview) server.

Before proceeding, check the [Installation Requirements](/v8/docs/installation-requirements) for recommended specifications.

Once the Repository server is installed, there must be at least one account or group with the ability to create root folders.

A Repository server requires its database to be separate from any dev/prod databases. The Repository database should use the same type of database as the dev/prod database, i.e., a Repository server database should use Postgres if the dev server does.Hosting in Containers:If hosting the Repository server in a container, ensure to add an environment variable to change the server type: `DECISIONS_SERVERTYPE=Repository`.  
For more information, refer to the [Decisions Environment Variables](https://documentation.decisions.com/docs/environment-variables-1).

---

## Installation

1. Right-click the **DecisionsServerInstaller.exe**file and select **Run as administrator**.
2. Under **Select****Installation****Type**, select **Designer****Repository,**then click **Next**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-08-01_16h24_31.png)
3. This ends all Repository-specific changes during installation. Proceed with the installation as detailed in the [Installation Guide](https://documentation.decisions.com/v8/docs/installation-guide).
4. After installation, open up the **System**folder. Go to **System > Settings > Portal Settings.**Find the setting "Groups Allowed To Create Root Folder" and add the Administrator group. At least one account or group must be able to create Root Folders for the Repository to function correctly.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1756920995146.png)

---

For further information on Repository, visit the [Decisions Forum](https://community.decisions.com/categories/Repository).