---
title: "Public"
slug: "public"
status: "update"
updated: 2026-07-16T16:06:26Z
published: 2026-07-16T16:06:35Z
canonical: "documentation.decisions.com/public"
---

> ## 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.

# Public

## Overview

The **Public** directory will contain all the processes or elements that the end users will use. This will replicate the earlier known **Portal**, which was responsible for accessing all the end-user-facing elements. The **Public** directory has two folders in it:

- [**Catalog**](/version-10/docs/catalog): The **Catalog** serves as the [Workflow Catalog](https://documentation.decisions.com/v8/docs/workflow-catalog-overview), similar to older versions. This folder provides a centralized location for end users to access and run the processes. Elements added to the Catalog are referred to as catalog items.
- [**Public Folders**](/version-10/docs/public-folders): This folder will include the public-facing interactive folders that the end-users will use.

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-3TUTU0AD.png)

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1YE69E8S.png)

---

## What changed from v8 to v9?

| Version 8 | Version 9 |
| --- | --- |
| The visibility of the normal folders was determined solely based on the permissions given to the end users. | The folder’s visibility is not only permission-based but also location-based. All the end-users facing folders must be inside the **Public → Public Folders**. |
| The **Workflow Catalog** was used to host all the catalog items so they were accessible to the end-users. | The **Catalog** now replaces the workflow catalog and will host all the catalog items to be accessible to the end-users. |
| The **Workflow Catalog** was system-specific. Users could add any items to it from the platform. | The **Catalog** is Project-specific, and only processes from the current Project can be added. |

---

## Steps to Perform after Upgrading to v9

### Moving the Workflow Catalog Items

After upgrading to version 9, the Workflow catalog items will still be accessible to the end-users. These catalog items are located at **System → Applications → Workflow Catalog**. However, admin users can no longer add any new catalog items to this System folder.

During [project conversion](https://documentation.decisions.com/version-10/docs/projects-conversion), the catalog items will not automatically be transferred to the new Catalog folder. Users must move all the catalog items to the **Public Folders** in order to maintain the Project's integrity. Please follow the steps below to move the catalog items to the Project.

#### Moving legacy catalog items to Project:

1. Navigate to **System → Applications → Workflow Catalog**.
2. Right-click on the **Catalog → Projects → Move to Project**. A dialog with all the projects will appear.
3. Select the appropriate **Project → Catalog**. Click on **Move**.
4. The Project's Catalog folder will open, confirming that the catalog item got moved to that specific Project.

### Moving the User-facing Folders

After [project conversion](/version-10/docs/projects-conversion), all the public-facing folders will be visible in the folder tree within the Project. These folders will not be visible to the end users if the folders are not moved to the new **Public → Public Folders**.

Similar to the catalog items, relocating all end-user-facing folders under the **Public** folder after the Project Conversion is compulsory. To do so, you must move the parent folder of all the end-user-facing folders to **Public → Public Folders**. By moving the parent folder, all the child folders will also be moved automatically. To move the folders, refer to the steps mentioned below.

#### Move user-facing folders to Public Folders:

1. Right-click on the Parent folder you want to move to the Public Folders.
2. Click on **Move → Public → Public Folders**. Click on **Move**.
3. The folder and subfolders will be moved to the Project and will be accessible to the end users.

---

> [!NOTE]
> See Next:
> 
> - [Catalog](/version-10/docs/catalog): Learn how to add catalog items so they are accessible to end users.
> - [Public Folders](/version-10/docs/public-folders): Learn how to create and make folders visible to the end users.