To create a new top level folder, click Create
from the Actions menu or page toolbar.
To create a subfolder, click Folder
Action > Create Folder from the
Actions menu on a Folders page.
Subfolders can only be created of the same type. For example, subfolders
created from a controlled folder will be of the controlled folder type.
Similarly, subfolders created from a simple folder will be of the same
type.
Enter these details for the folder:
Type. Click
and select the folder type. Values are
"Workspace Vault", its sub-types, or "Controller Folder".
Name. Enter a short name for
the folder.
Policy. Click
and select the policy for the selected
folder type.
Description. Enter a description
of the purpose of the folder.
Default User Access. Select
an option to control who should have read access to the folder:
- None. The only users who
have read access to the folder are those who are listed in the folder's
access list. Only project members can be added to a folder's access list.
- Read. Any user who has view
access to the project, either through direct membership or through company
visibility, will have read access to the folder. Read access to the folder
means being able to view and download the content of the folder. If you
choose Read as the default access and Inherited as the access type, all
project members are added to the folder's access list and are given Read
access.
- Read Write. Allows
project members Read and Write access. Read access
to the folder means being able to view and download the content of the
folder. Write access to the folder means being able to change the content
of the folder.
- Add. Allows project members to add content
to a folder.
- Remove. Allows project members to remove content
from a folder.
- Add Remove. Allows project members Add and
Remove access. Add access to the folder means being
able to add content to the folder. Remove access to the folder means
being able to remove the content from the folder.
Inherit Access. Choose an option
from the drop-down list:
- Yes. For subfolders, the
subfolder's access list will inherit the parent folder's access list.
Whenever the parent's access list is changed, the same change is made
to the subfolder's access list. The subfolders's access list can be changed
directly without affecting the parent's list.
For top level folders, Inherited only applies when the
Default Access is Read. In this case, all project members are added to
the folder's access list and are given Read access.
- No. The folder/subfolder's
access list is not inherited from the parent. Changes to the parent or
subfolder's access list are independent and have no affect on the other
folder.