In order to be able to clone copy a project, the user should have 3 privileges granted - View Project, View Financials and Add Project. A company may not want to Grant the 'View Project' and 'View Financials' to all their Staff, as that would mean anyone who is a user of Celoxis can view all projects including its financial information. You can define a special role (eg. Clone Copy Project Role) and assign those users to this role whom you wish to grant the ability to Clone copy your templates to create new projects.
At the Company level, you keep "View" Project and "View Financials" as "Unspecified" for this role. However, at the template level (i.e on the specific projects that are defined as templates), set object level security and specifically set a Grant on the 2 privileges - 'View Project' and 'View Financials'. This will allow users playing the "Clone Copy Project Role" role the ability to clone copy from your templates.
| Company Level | View Project | View Financials | Add Project |
|---|
| Copy Project Role | Unspecified | Unspecified | Grant |
| Template Level |
| Copy Project Role | Grant | Grant | NA |
| Tip | ||
|---|---|---|
You can prefix the project name with 'Template' for e.g "Template - 4572 TEST Project" OR you can create a custom field say 'Is Template' (type Single-select drop-down with values Yes and No) and select Yes or No depending on whether this project is a template project. Creating a custom field can help you segregate templates from actual projects in reports. | ||
| Info | ||
| ||
Clone project will copy over the object level security. So all users playing Clone Project role will now have View Project and View Financials permissions to your cloned copy. If you do not want that, then set security for the cloned project and change that permission. |