as you know from my last Post, I created Departments, and I have assigned to the Project Manager Projman2 two departments (SIR and SIC), and no department to Project Manager named Projman1.
Now let’s suppose that Project Manager Projman1is logged on the Project Server 2010 and he wants to Create new Project with no Department field!
and I will get:
I am going to Save Publish that Project:
I am going to log in as a Project Manager 2and I will create new Project for SIR Sector like this:
I am going to save this Project too:
and I will publish it (I won’t show you that Picture Again, why should I? )
Now I am going to log in to PWA as Projman1, and I am going to Project Center:
As you can see, Projman1 can see both Projects!
Now I am going to log in to PWA as Projman2, and I am going to Project Center, too:
As you can see, Projman2 can only those Project that belongs to his Department!
If you have custom fields which are going to be used for some department, and you do not want that other departments use those specific custom field you, department fields are to filter which custom field can you access!
Suppose that I have Custom field for SPIG department like this one:
and one for SIR Department:
I will now open FIRST SPIG PROJECT in MS PROJECT PRO 2010 (logged as Projman1, and Projman1 has no Department), and I am going to the Project Information:
as you can notice, since this Project is for SPIG department I can see SPIG DEPARTMENT CUSTOM FIELD, but not the SIR DEPARTMENT CUSTOM FIELD! The same will be if I connect as a Projman2!
If I open FIRST SIR PROJECT, and if I look at Project Information I will see:
To conclude, Custom fields are not for security, but for filtering which custom and/or Projects can be seen by whom and where!
I will not be able to answer your questions, nor will I write an new post for next 10 days, because I’m going to attend MVP summit in Seattle for February 16 to February 24 2013.