--- title: "Setting Permissions" slug: "setting-folder-permissions" description: "This document explains the ins and outs, of Folder & Portal permissions. Changing the permissions on a folder or portal will change how and what data is displayed to a user. " tags: ["User Portal", "Portal", "Decisions Studio", "Permissions", "portal settings", "Folder"] updated: 2025-09-04T15:52:45Z published: 2025-09-04T15:52:45Z --- > ## 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. # Setting Permissions ## Overview **Permissions**are settings that grant [Account(s)](https://documentation.decisions.com/v9/docs/adding-a-user-account) or [Group(s)](/v9/docs/creating-groups) access to a specific******Project**or**Folder** as well as its contained Designer Elements. Additionally, depending on the [Filters****](https://documentation.decisions.com/v9/docs/using-inline-filters)used in some **Reports**, Permissions may also be used to restrict how data appears on a Report, such as toggling visibility of hidden or deleted items. Administrator accounts can configure permissions on any Project. On the other hand, accounts with Project-creating access i.e. Designers or higher, can only edit permissions on their own Projects. The following article reviews how to change a Project's permissions, list each permission level, and then define permission inheritance. --- ## Changing Folder Permissions Within a Project Users with at least Designer permissions can edit a Folder's permissions to restrict how certain accounts and/or groups interact with it. 1. Navigate to a Project in the Folder Tree, and right-click on a Folder or a Designer Folder. 2. In the Manage Section, navigate to **Permissions****> Manage Permissions.** 3. Click ADD under either **Accounts Information** or **Groups Information** to select an Account or Group. 4. Under Account (Or Group), click **PICK** in the resulting window. In the resulting **Pick Entity** panel, select the desired Entity, and then click the **PICK**button once again. 5. Next, enable the desired PERMISSIONS**.**For example, enable the CanUse, CanOpen, and CanView settings to allow users to search for and view the Folder's contents. 6. Select OK after the Permissions have been selected to return to the **Manage Folder Permissions**panel.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-10_16h35_17.png)![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-15_16h36_11(1).png) 7. If required for the use case, repeat this process for each Account or Group that requires additional permissions for the Designer Folder. 8. After adding the desired Accounts or Groups, click **SAVE PERMISSIONS.**The selected users with those Permissions can now access the Designer Folder in the Portal. 9. Navigate to the Portal of the Account or Group that has been granted visibility and notice the Designer Folder is displayed. ### Legacy Projects Permissions for Legacy Projects work the same as for Projects discussed above. Permissions can be set for both Folders and Designer Folders. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/Setting%20Folder%20Permissions%202024-07-16%20144151%20(1).png) --- ## Folder Permissions Levels The following chart defines each level of available permission****found within the **PERMISSIONS** category of the **Manage****Folder****Permissions**window: | Permission | Function | | --- | --- | | Can Use | Gives permission to utilize Designer Elements within the Folder. | | Can Open | Gives permission to open Subfolders or Process Folders contained within the Folder. Enabling this permission also enables Can Use. | | Can View | Gives permission to view a Folder and its contents in the Folder tree. This does not allow the user to edit or manage the data. Users also do not have debug access to Designer Elements. | | Can Edit | Gives permission to edit tags on the Folder and its contents by allowing the ability to add or delete tags. Enabling this permission also enables all preceding permissions. | | Can Add | Gives permission to add Entities to a Folder such as Designer Elements, documents, comments, etc. Enabling this permission automatically enables the Can Use, Can Open, and Can View permissions. | | Can Delete | Gives permission to delete the Folder. Enabling this permission also allows the user to delete any Subfolders within the parent Folder. This feature enables Can Use, Can Open, and Can View permissions. | | Can Administrate | Gives all permissions to the Folder. The user can manage the folder's permissions, rename the folder, and grant other permission types. Can Administrate is required to use the Import action within a Project. | | Can See Hidden | Gives permission to view items marked as hidden inside this Folder. The Report filter will still need to be changed to Hidden in order to see the content. | | Can See Archived | Gives permission to view the contents of the Archived Folder. | | Can View Browse Page | Gives permission to see the Browse page link. | --- ## Permission Inheritance By default, Projects****are given**permission inh****eritance**which****grants****any nested Subfolders the same permissions as their containing parent Folder. Permission inheritance can be toggled via **Manage > Permissions: Disable/Enable Permissions Inheritance** in the Folder's Action Menu. Toggle permission inheritance off to allow more flexible control of what can and cannot be accessed within the Project and by whom. The group members cannot view nor interact with other Subfolders within the parent Folder, not the parent Folder itself since the permission was not applied to the parent.