In order to be able to clone a project, the user should have 3 privileges granted ; - View Project, View Financials and Add Project. If any of these have a specific 'Deny' at the Company Settings, the person will not be able to clone template projects. You can grant 'Add Project' to the roles you wish to allow to clone and create projects. But typically a company 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. To achieve a setting where the relevant people have the relevant permissions, leave the above privileges as 'Unspecified' for the Staff role at the company security settings. An 'Unspecified' at the Company level means that the object level security will be consulted. At the You can define a special role (eg. Clone Project) and assign those users to this role whom you wish to grant the ability to Clone 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 Project" role the ability to clone from your templates.
| Company Level | View Project | View Financials | Add Project |
|---|---|---|---|
| StaffClone Project | Unspecified | Unspecified | Grant |
| Template Level | Staff | ||
| Clone Project | 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. |