Documentation Center

Folders and inheritance for customer requesters

Your administrators organize your resources into folders and subfolders in order to enforce inheritance. As a result, you can quickly access your resources by folder (also known as location).

Types of inheritance

Parent inheritance means that child folders inherit resources from their parent folder (or grandparent folder or higher above).

In brief, inheritance ensures that:
  • Users can see and use the resources stored in the folders above them (parent or grandparent folders).
  • Users cannot see and cannot use the resources stored in brother folders or uncle folders.
Therefore, when you select a location for your project during project creation, the project templates you can use to create this project are filtered as follows:
  • All project templates from your current folder (current location)
  • All project templates inherited from the folders above your current folder (parent or grandparent)

Inheritance differences: projects vs. project templates

There is an important difference between the way projects and project templates are accessed based on inheritance.

As customer requester, you can access the project templates from:
  • Your current folder (see and use)
  • Your parent folder and above (see and use)
As customer requester, you can access the projects from:
  • Your current folder (see and manage)
  • Your child folders (see and manage)

Therefore, you cannot access (see and manage) any of the projects created in a folder (location) above your current folder.

There is one more restriction which needs to be considered. There are two types of roles customer requesters can take: Customer Requester and Customer Requester Restricted. These 2 roles have the same set of permissions with one exception: visibility over peer projects. Users who have the Customer Requester role see their peers' projects, while users who have the Customer Requester Restricted role do not see their peers' projects.