Excluding Gantts from User Access

[Incanus]

Hello:

What would be the most efficient way of using Project Server's Groups
and Categories to prohibit write (edit) access for any an all users
(other than admins) to a specific Gantt or Gantts... without deleting
said Gantts from Project Server's?

Thanks in advance,

Sebastián Armas
Project Manager

 

[Dale Howard [MVP]]

Sebastian --

The only Gantt Chart view you can prevent everyone from editing is the
Enterprise Gantt Chart view, along with its corresponding Enterprise Entry
table. The Project Server administrator is the only one who can edit either
of these enterprise objects. Hope this helps.




Hello:

What would be the most efficient way of using Project Server's Groups
and Categories to prohibit write (edit) access for any an all users
(other than admins) to a specific Gantt or Gantts... without deleting
said Gantts from Project Server's?

Thanks in advance,

Sebastián Armas
Project Manager

 

[Gary Chefetz]

Sebastián:

When you say "Gantt" are you talking about a view or a project schedule? I
suspect we may have a terminology barrier here.

 

[Incanus]

I'm talking of an actual project schedule, one that you could open
with (say) Office Project Professional and update and then publish
back to Project Server (or save to a local .mpp file).

I'd like to have a Gantt to be "invisible" (not in Project Server
project schedules' available list when opening from Office Project
Professional), or, if visible, not available for reading/writing from
Office Project Professional.

How to do this, using Project Server's Groups and Categories, and
without actually checking out the project schedule(s)?

Thanks in advance,

Sebastián Armas
Project Manager

 

[Dale Howard [MVP]]

Sebastian --

As I already told you, the only View you can "lock" is the Enterprise Gantt
Chart view, and its accompanying Enterprise Entry table. A project manager
can edit any of the default Views, such as the Gantt Chart or Task Usage
views, and any of the default Tables, such as the Entry table or the
Tracking table for tasks.

And no, there is no way, via Group and Category permissions to have a View
be visible in Microsoft Project 2007 to some users and visible to others.
On the other hand, you CAN make PWA views visible to some users and not to
others. But this is NOT possible in Microsoft Project 2007. Hope this
helps.




I'm talking of an actual project schedule, one that you could open
with (say) Office Project Professional and update and then publish
back to Project Server (or save to a local .mpp file).

I'd like to have a Gantt to be "invisible" (not in Project Server
project schedules' available list when opening from Office Project
Professional), or, if visible, not available for reading/writing from
Office Project Professional.

How to do this, using Project Server's Groups and Categories, and
without actually checking out the project schedule(s)?

Thanks in advance,

Sebastián Armas
Project Manager

 

[Gary Chefetz]

Sebastián:

Ok, then, let's stop using the term "Gantt" as it is clearly confusing my
partner Dale. A Gantt Chart is simply a view that you can apply to a
schedule in project or Project Server. You certainly can use groups and
categories to protect schedules and prevent people from seeing them, or give
people rights to view them read-only, or allow them to read or write.
Understand that once you give someone the ability to open a schedule in the
Project client, you can't prevent them from applying any view available in
the Project client. So your choices are 1) the user can't open the schedule,
2) the user can open the schedule read-only, and 3) the user can open the
schedule read/write.

The standard permissions in Project Server do not allow Project Mangers to
open each other's plans in read/write mode. So, you need to be a bit more
specific about what exactly you want to accomplish. In the mean time, here
are some articles on manipulating the permissions in Project Server that
might help you get started:

http://www.projectserverexperts.com/zzfaqkb01/Read-OnlyAccessForPMTeamMembers.aspx
http://www.projectserverexperts.com/ProjectServerFAQKnowledgeBase/OpenOtherProjectsReadOnly.aspx

You might also consider our book Implementing and Administering Microsoft
Office Project Server 2007 for a thorough explanation of Project Server
security.

 

[Incanus]

Hello:

I'll reply bellow, If it's no bother.

Sebastián:

[...]
You certainly can use groups and
categories to protect schedules and prevent people from seeing them, or give
people rights to view them read-only, or allow them to read or write.
Understand that once you give someone the ability to open a schedule in the
Project client, you can't prevent them from applying any view available in
the Project client. So your choices are 1) the user can't open the schedule,
2) the user can open the schedule read-only, and 3) the user can open the
schedule read/write.

I'd rather implement 1) the user can't open the schedule or
if it's simpler, 2) the user can open the schedule read-only

The standard permissions in Project Server do not allow Project Mangers to
open each other's plans in read/write mode. So, you need to be a bit more
specific about what exactly you want to accomplish.  In the mean time, here
are some articles on manipulating the permissions in Project Server that
might help you get started:
http://www.projectserverexperts.com/zzfaqkb01/Read-OnlyAccessForPMTeamMembers.aspx
http://www.projectserverexperts.com/ProjectServerFAQKnowledgeBase/OpenOtherProjectsReadOnly.aspx

I'll be checking those: thankyou very much!

You might also consider our book Implementing and Administering Microsoft
Office Project Server 2007 for a thorough explanation of Project Server
security.

Again: thankyou very much!

Gratefully yours,

Sebastián Armas
Project Manager

 

[Gary Chefetz]

The articles should be enough to get you started down the right path.

Hello:

I'll reply bellow, If it's no bother.

Sebastián:

[...]
You certainly can use groups and
categories to protect schedules and prevent people from seeing them, or
give
people rights to view them read-only, or allow them to read or write.
Understand that once you give someone the ability to open a schedule in
the
Project client, you can't prevent them from applying any view available
in
the Project client. So your choices are 1) the user can't open the
schedule,
2) the user can open the schedule read-only, and 3) the user can open the
schedule read/write.

I'd rather implement 1) the user can't open the schedule or
if it's simpler, 2) the user can open the schedule read-only

The standard permissions in Project Server do not allow Project Mangers
to
open each other's plans in read/write mode. So, you need to be a bit more
specific about what exactly you want to accomplish. In the mean time,
here
are some articles on manipulating the permissions in Project Server that
might help you get started:
http://www.projectserverexperts.com/zzfaqkb01/Read-OnlyAccessForPMTeamMembers.aspx
http://www.projectserverexperts.com/ProjectServerFAQKnowledgeBase/OpenOtherProjectsReadOnly.aspx

I'll be checking those: thankyou very much!

You might also consider our book Implementing and Administering Microsoft
Office Project Server 2007 for a thorough explanation of Project Server
security.

Again: thankyou very much!

Gratefully yours,

Sebastián Armas
Project Manager