User manual

Table Of Contents
Overview
Once an item's permission set is locked, only team members and groups
included in the permission list have access to the folder and the permission
set for that folder will not be affected by any changes made to project-wide
permission lists.
This is useful if, for example, you want to limit member access to a project's
financial folder. You know there are only certain members who should have
access to this financial folder regardless of any changes that may be made to
the site or project. Locking the permission set prevents giving new members
access to this folder. Or, if permissions should be changed site or project-wide,
the permissions for this folder will not be affected.
When you lock a permission set, you are locking the entries you see in the
permission list. The term "locked" in this case means that new, individual
project members cannot be given access to a locked folder or file (except when
members are added to groups that have already been assigned to a folder or
file with a locked permission set). An administrator cannot change the
permissions of existing project members within a locked list. Nor can
administrators add a new project member to a project that has a locked
permission set.
It is possible to unintentionally grant new project members access to a locked
folder or file. A permission list may include a combination of individual
members and groups; if you lock a permission set and then add a new member
to a group that is in the locked permission list, the new member will have
access to the folder or file.
NOTE To control the security of locked folders and files, do not add new members
to groups when a permission set is locked.
A project that has a locked permission set can be cloned and the permission
set will remain locked in the clone.
To lock and unlock a permission set (folder or file)
1 In the tree view select a project, folder, or file.
2 Right-click, and choose either Lock Permission or Unlock Permission
from the menu.
See also:
Cloning a Project (page 42)
Permissions (page 130)
Site and Project Administration | 139