Enterprise Project Templates

[RandyK]

Is there a way to lock down Enterprise Project templates so they cannot be
modified (only saved to .mpp files)?

 

[Dale Howard [MVP]]

Randy --

First of all, if you are using Project Server and your PM's are creating
projects from enterprise templates, they should NOT save their projects as
..mpp files. They need to save their projects in the Project Server
database, otherwise, they are defeating your company's use of Project
Server. Enough lecture.

Second, if you need to prevent your PM's from saving enterprise templates or
from editing existing templates, ask your Project Server administrator to do
the following:

1. Log into PWA with administrator permissions
2. Click Admin - Manage Users and Groups
3. Click the Groups link in the sidepane on the left
4. Select the Project Managers group and then click the Modify Group button
5. In the Global Permissions grid, set the "Save Project Template"
permission to "Not Allowed" (neither Allow or Deny is selected)
6. Click the Save Changes button

Hope this helps.

 

[RandyK]

Dale - helps a great deal! That is exactly what I was looing for. I will
make that change. As for the lecture, that was my bad - we are saving to
MSPS - not as .MPP files.... Thanks again!
RK

Randy --

First of all, if you are using Project Server and your PM's are creating
projects from enterprise templates, they should NOT save their projects as
..mpp files. They need to save their projects in the Project Server
database, otherwise, they are defeating your company's use of Project
Server. Enough lecture.

Second, if you need to prevent your PM's from saving enterprise templates or
from editing existing templates, ask your Project Server administrator to do
the following:

1. Log into PWA with administrator permissions
2. Click Admin - Manage Users and Groups
3. Click the Groups link in the sidepane on the left
4. Select the Project Managers group and then click the Modify Group button
5. In the Global Permissions grid, set the "Save Project Template"
permission to "Not Allowed" (neither Allow or Deny is selected)
6. Click the Save Changes button

Hope this helps.

 

[Dale Howard [MVP]]

Randy --

You are more than welcome, my friend!

Dale - helps a great deal! That is exactly what I was looing for. I will
make that change. As for the lecture, that was my bad - we are saving to
MSPS - not as .MPP files.... Thanks again!
RK

 

[Kevin W Flanagan]

What is the simple explanation for the differences between Not Allowed and Deny
--
Kevin W Flanagan, PMP
EPM Consultant

Randy --

First of all, if you are using Project Server and your PM's are creating
projects from enterprise templates, they should NOT save their projects as
..mpp files. They need to save their projects in the Project Server
database, otherwise, they are defeating your company's use of Project
Server. Enough lecture.

Second, if you need to prevent your PM's from saving enterprise templates or
from editing existing templates, ask your Project Server administrator to do
the following:

1. Log into PWA with administrator permissions
2. Click Admin - Manage Users and Groups
3. Click the Groups link in the sidepane on the left
4. Select the Project Managers group and then click the Modify Group button
5. In the Global Permissions grid, set the "Save Project Template"
permission to "Not Allowed" (neither Allow or Deny is selected)
6. Click the Save Changes button

Hope this helps.

 

[Dale Howard [MVP]]

Kevin --

First of all, there is no simple explanation for security permissions in
Project Server, especially if someone is a Project Server administrator who
comes from a non-technical background. It is easier to understand if you
come from a network administration background and are familiar with security
groups to control network permissions.

The quick and dirty explanation of permission settings is this: In Project
Server, permissions are cumulative across all security Groups to which you
belong (and the Categories to which those Groups have access). When a user
belongs to multiple security Groups, the order of precedence for calculating
the cumulative permission is as follows:

Denied trumps both Allowed and Not Allowed
Allowed trumps Not Allowed
Not Allowed trumps nothing

If you are a member of two Groups, and in one group a specific permission is
set to Denied and in the other Group the same permission is set to Allowed,
the cumulative permission is calculated as Denied (the Denied permission
trumps everything). This can cause problems for you if you are a Project
Server administrator and you are a member of any Groups other than the
Administrators group. If you are a member of two Groups, and in one Group
the permission is set to Allowed and in the other Group the same permission
is set to Not Allowed, then the cumulative permission is Allowed (Allowed
trumps Not Allowed). If you are a member of two Groups, and in both Groups
the permission is set to Not Allowed, then the cumulative permission is Not
Allowed, which means that you cannot do what that permission describes.

Because the Denied permission is so powerful, and can cause problems when
users are members of mutliple Groups (or the Groups have access to multiple
Categories), we recommend that you use the Denied permission rarely and use
it very carefully if you must use it. Generally speaking, the Not Allowed
permission will cover your security needs without needing to to use the
dangerous Denied permission. See, that wasn't simple, was it?

Thanks for asking. Hope this helps.

What is the simple explanation for the differences between Not Allowed and
Deny

 

[Kevin W Flanagan]

Yes it does, thank you very much.

 

[Dale Howard [MVP]]

Kevin --

You are more than welcome for the help, my friend! And thank YOU for
offering your assistance to others in this group!