Deny viewing of certain projects

[H20Polo Pascal]

My current default settings allow all users to see all projects in our
server. I have a need to restrict access of certain projects to a small
group of individuals.

I know how to use MODIFY CATEGORY in PWA to show a list of projects a
category can see, but I don't want to be required to constantly update the
list as new projects are added. This is why the default is to see all
projects.

Is there a way to list projects that can't be seen rather than list projects
that can be seen? This would be much easier to manage. In fact, I would
like to use one of my project codes to define the list of projects that can't
be seen in PWA and try to automate the process.

Does anyone have a manual solution or a macro that accomplishes this?

Finally, can the same security be set up within the client, so that those
using this interface are also restricted from viewing certain projects?

Regards,

Pascal Cohen-Hadria

 

[Dale Howard [MVP]]

Pascal --

To automate the process, you would need to create a custom enterprise
Project flag field that specifies which projects should and should not be
seen by folks in the particular group. Then you would need to create a
custom Category into which those "don't see" project would be added
manually, and add that Category to a custom Group for those who should not
see the projects. Then refer to the following FAQ for a SQL script that
will automate the transfer of projects to the new Category:

http://www.projectserverexperts.com/Shared Documents/ChangeSecurityCategories.htm

Hope this helps.

 

[Tom M. Smith]

May I extend this question to ask. How does one deny viewing of "enterprise
custom fields" that are in the global template to only selected users that
connect to the server via PWA (and/or Project Pro 2003) to server based
projects that depend on that global template?
Thanks for the help.

 

[Dale Howard [MVP]]

Tom --

For those users, first create one or more custom PWA views that do not
contain any of the custom fields. Then create a custom Category that gives
access to only those specific projects that do not contain the custom
fields. Then create a custom Group, add those users to this Group only, add
the custom Category to the Group, and then set the Permissions and Global
Permissions as desired. Lastly, remove those users from any Groups other
than the one custom Group you created for them. This will restrict access
in PWA to allow those users only to see Views that do not include the custom
fields.

In Microsoft Project Professional, on the other hand, you cannot prevent
users from see any or all of the custom fields. If a user has permission to
open a project in Microsoft Project Professional, even Read/Only, he/she can
easily insert the custom fields in any View and see them. Hope this helps.

 

[Tom M. Smith]

Dale, your suggestion is most appreciated !
If you should have a moment please consider viewing my thread with Kevin
Flanagan titled "Monitoring user updates to Project Server".
Regards, TOM

 

[Dale Howard [MVP]]

Tom --

You are more than welcome, my friend! Since Kevin started answering that
thread with you, I will allow him to finish it with you. It is only common
courtesy, and I believe he will ultimately help you. But thanks for asking!