Field Level Security

[Amy]

Can we have security defined to the field level? We only
want to give users access to modify certain fields in the
project. How can we do this?

 

[Dale Howard [MVP]]

Amy --

To what specific fields do you want to restrict access? What kind of users
are these people? Project managers? Team members? Where do you want to
restrict access? In Microsoft Project? In Project Web Access? Please give
us more information so that we can answer your question.

 

[Amy]

Thanks for your reply. We want to restrict access in
Microsoft Project to Project Managers. We have created
some custom fields and we don't want the Project Managers
to modify these fields.

 

[Dale Howard [MVP]]

Amy --

If the project managers can open the project Read/Write in Microsoft Project
Professional, then you cannot prevent them from changing values in these
enterprise fields. In your case, I would recommend that you make this a
training and performance issue for your project managers, and then hold them
accountable for their performance in this area. Hope this helps.

 

[Kurt Verhaegen]

Amy,
We are using the following method, if you modify it you
can reach the same goals:
- to each project an autorun macro is attached
- if the PM change the value of a certain field
- the macro will notice this, the original value is copied
to another field typically not visible
- after the modification is accepted (user press enter)
- this is detected again and the original value of the
temporary field is retrieved and stored in the field again

It's a complex workaround, which also uses CPU cycles for
each modification you do to the plan, but it allows you to
have fixed values in certain fields.

Another method could be: storing the values in field eg
Number11, and define Number 1 = Number 11 as a formula. In
the views for the PM you only show the column Number1 and
not Number11.
People who have the rights/roles in your organisation are
aware of Number11, the other not.

Grtz Kurt