Restriction to view the project

[paola70]

Hi,
I have published some projects and I would want to prevent that the projects
are visible to all resources that of it make part. How I can make?
Moreover I would want to only obtain one view on the usage/cost of the
resources relative to the single project plan.
Thanks.

 

[Reid McTaggart]

Very unusual! You want to NOT permit resources to see certain projects that
they are assigned to?

To do this, you could create a new category, put those projects into it, and
Deny permissions to groups that contain the resources, such as Team Members
and Project Managers and Team Leads.

You would have to be careful to not associate with this category any groups
that you DO want to be able to see the projects. For example: Perhaps
Executives and Administrators groups would NOT be associated with this new
category.

Also, if you want to permit other Team Members or Project Managers or Team
Leads, who are NOT assigned to the projects, to see the projects, then you
have much more work to do. Such a requirement would be even more unusual,
and it would make me wonder if you are managing some sort of Machiavellian
reality television show!

--
Reid McTaggart
(e-mail address removed)
Alegient, Inc., Houston
Project Server Experts
Microsoft Certified Partner

 

[TGG]

Paola,

Without knowing more about your setup, you could run into some potential
issues. Bear in mind, I'm thinking about this as I'm typing so this might
not be the best answer I can come up with on this.

We have some confidential projects where this type of restriction was
necessary. TMs could see their tasks via the task sheet, but not the entire
plan via Project Center. These are typically projects where the words
merger, acquisition, spinoff, outsourcing and downsizing could be involved.

In those project need instances, the team members (TM) were not part of the
normal TM setup.

Consequently, we setup a special category where the TMs have access to the
project, but have no project center views assigned. This way, they can still
use their timesheet to see only their tasks. You still have some exposure
with the create new task function as they can see some of the summary tasks
through this feature. We wound up with another group as well just for these
TMs.

If you have team members who are part of the normal category setup and the
following configuration is true, you may have issues.

If your default category for team members is setup where
- the option for Only the projects indicated below: is checked
- the check box Allow users in this category to view all projects in which
they are a team member is checked

In this situation, they will most likely be able to see the project
regardless of how you set up another category. I think permissions in the
category side are additive. I believe most people who have RBS security
based configurations will have the above settings checked since it reduces
security maintenance for TMs tremendously.

One alternative may be to have separate categories for data access and views
configuration. If you do this, you could have one category for data access
setup as above, then have specific views configuration categories where
certain groups have access to specific views categories.

Because the categories are very flexible in certain respects and very
inflexible in other respects, this type of scenario is harder to set up than
it should be.

This is the best I can come up with while running on 3 hrs sleep and a lack
of caffeine. If I think of more, I'll post.

TGG
blog: http://spaces.msn.com/members/evildoctorporkchop