User manual

■ The same folders, logs, and sub-projects as in the original project, with the
same permissions, as the original project.
■ The same roles and workflow types associated with the original project,
with the same project members associated with each. Forms are not cloned.
Note that even though roles are cloned, specific member assignment to
those roles are not. For example, if Sue is assigned the role of Lead-Engineer
in the source project, the destination project will not receive Sue. The role,
Lead-Engineer will be cloned, but it will not contain any members.
If the Include Files option is selected, a project is created with all of the above
attributes, as well as all of the files of the original project, with the following
attributes:
■ Files have the same permissions associated with them as the original files
and forms.
■ Files only contain their most recent version.
■ Files maintain their discussions.
■ Drawings maintain their markups.
Cloning and permissions
When a project is cloned to a subfolder, all users belonging to the cloned
project are granted list permissions to the top level (or parent) folder, and all
subfolders down to the cloned project. This is because the destination folder
may be a location that users do not have permission to view. By granting users
list permissions to the parent folder, users can access the cloned project. For
example:
In the following picture Construction Drawings has been cloned to a subfolder
of Proj3. Before Construction Drawings is cloned, you have edit permissions
to Construction Drawings, but not to Proj1, Proj2, and Proj3. After the clone,
you still have edit permissions to Construction Drawings, as well as list
permissions to Proj1, Proj2, and Proj3.
A project that has a locked permission set can be cloned and the permission
set will remain locked in the clone.
44 | Chapter 6 Site and Project Administration