About Folder & Portal Permissions

Last Updated: 08/09/2018 Introduced in Version: 2.0

Portal folder security sets access to the contents of a folder, including the entities stored in the folder and the actions that can be performed on them. Depending on a report’s filters, folder security may also restrict how data displays on reports.

By default, a folder inherits permissions from its parent folder. That means that unless inheritance is disabled for a subfolder, it will get its permissions from its parent (this relationship cascades all levels).
In the folder structure below, all folders would have the exact same permissions unless inheritance was disabled for one. Jane would have administrator rights to all folders.
 
  • Folder 1 (jane@example.com has permission to Administrate this folder)
      Folder 1.1 (no specific permissions set)

      • Folder 1.1.2 (no specific permissions set)

 

In the folder structure below, john@example.com would only have permission on Folder 1 because Folder 1.1 has no permission set, and is NOT inheriting from parent. Folder 1.1.2 is inheriting from Folder 1.1, which has no permissions.

  • Folder 1 (John@example.com has permission to administrate this folder)
    • Folder 1.1 (no specific permissions set, permission inheritance disabled)
      • Folder 1.1.2 (no specific permissions set)
 
 

An administrator sets group and account access permissions for folders. A group or account may have permission to view a folder’s contents or may have full administrative rights.

To set folder security in the portal, click on the folder, and select Manage > Manage Permissions. In the Manage Folder Permissions pop-up, in the Accounts section, click the Add button. To select the account to grant permission, click the Account selector.

 

Select an account from the list and click OK.  This is where you could also edit permissions or delete accounts.
To edit permissions, select the account and then select the Edit Button, on the Edit object form you will see all the different permissions and can select/deselect as needed.
 

Specific Permission Types

  • Can use: allows the user to use items in this folder without having any other permissions to the folder. For example, for a user to be able to use  any of the designers, they need to at least have can use permission on /System/Shared Designer Elements/ 
  • Can Open: allows the user to open folder tree
  • Can View: allows the user to view this folder in the folder tree
  • Can Edit: allows the user to edit tags on the folder
  • Can Add: allows the user to add entities to a folder. For example, if the folder is a designer project, it allows the user to  add flows/rules/etc to that folder
  • Can Delete: allows the user to delete the folder
  • Can Administrate: gives the user all permissions to the folder. Allows things like managing permissions on folder, renaming folder
  • Can See Hidden: allows the user to view items marked as hidden inside this folder 
  • Can See Archived: allows the user to view the Archived folder
  • Can View Browse Page: allows the user to see Browse page link
To disable permission inheritance; select the folder, select Manage > Permissions: Disable Permissions Inheritance
 

Need more help with:

Folder & Portal Permissions?

 

Contact us at support@decisions.com

 

Additional Resources