none
Project Manager Permission for Restricting Baselining RRS feed

  • Question

  • Hi,

    I created a custom group for project managers and deny the permission for baselining (save Unprotected Baseline and save protected Baseline) the project in the security template as well as in the group. I applied this to a project manager and when he tried to baseline from project professional he can do the same and he can publish the project with this changes.

    Any idea. 


    Thanks & Regards, Benno
    Thursday, March 24, 2011 6:42 AM

Answers

  • Hi Benno,

    Unfortunately, this is by design.

    All security rules and settings apply to Enterprise Projects. If a user creates a new project, the type of the project is not (yet) 'Enterprise' but 'New'. As a result, not all restrictions apply to this new project.

    You can either introduce a Project creation/request procedure in which the Project manager is not allowed to create new projects from within Project Pro or not at all.
    or you would have to write a macro that stops a new project from being saved if a baseline has been saved.

    I hope this helps,
    Hans


    My EPM blog: Projectopolis
    Thursday, March 24, 2011 2:29 PM
    Moderator

All replies

  • Hi Benno,

    What version of project server are you using?

    Just to be sure: so you have set 'deny' to on for permissions save Unprotected Baseline and save protected Baseline for this group and the project manager is a member of this group? For which category in this group have you denied the 'save protected baseline'? For 'My Organization'?

    Did the PM close Microsoft Project and re-open it after you have made your changes?

    Off topic: denying permissions in Project Server is not always the best practice. You should consider leaving the permission blank (no allow, no deny) if you want to deny a permission for a group.

    Regards,
    Hans


    My EPM blog: Projectopolis
    • Marked as answer by Benno EPM Thursday, March 24, 2011 12:04 PM
    • Unmarked as answer by Benno EPM Thursday, March 24, 2011 12:04 PM
    • Marked as answer by Benno EPM Thursday, March 24, 2011 12:05 PM
    • Unmarked as answer by Benno EPM Thursday, March 24, 2011 12:05 PM
    Thursday, March 24, 2011 9:46 AM
    Moderator
  • Hi Hans,

    I am using Project Server 2010 and Project Professional 2010.

    The Project manager cannot do baseline or clear baseline once the project is saved and published. But if they are creating a new project from project professional and before saving if they are baselining it is getting saved and publishing. But they will not be able to edit it next time.

     

     


    Thanks & Regards, Benno
    Thursday, March 24, 2011 12:13 PM
  • Hi Benno,

    Unfortunately, this is by design.

    All security rules and settings apply to Enterprise Projects. If a user creates a new project, the type of the project is not (yet) 'Enterprise' but 'New'. As a result, not all restrictions apply to this new project.

    You can either introduce a Project creation/request procedure in which the Project manager is not allowed to create new projects from within Project Pro or not at all.
    or you would have to write a macro that stops a new project from being saved if a baseline has been saved.

    I hope this helps,
    Hans


    My EPM blog: Projectopolis
    Thursday, March 24, 2011 2:29 PM
    Moderator
  • Thank you Hans for the explanation and help.

     


    Thanks & Regards, Benno
    Sunday, March 27, 2011 4:47 AM
  • Hi Hans

    I disagree that this is by design. It is a real new bug in 2010 introduced in the end of November/start of December.

    In Project Professional 2007 if you got a mpp file or if you had just created a new project in Project Professional and define a baseline before it becomes an "Enterprise" project, you can set the baseline as you can do in 2010. But when you save it (in mpp form or new project form) in Project Server 2007, it clears the baseline before save whem the PM does not heve right tho save the protected baseline (it is not necessary to choose Deny, just leave unchecked). So the first question is why downgrade a design of 2010 that is working fine in 2007?

    Well in Project Pro 2010 curiously it worked fine as Project 2007 until last November.

    In December this feature stopped to work. I know this, because I received a support request in mid November, that PMs were claiming that they could not save the baseline because this feature was working (only the PMO could save the baseline by setting definition).

    In mid December the PMO of the same customer called me again complaining that the PMs were saving the baseline bypassing the setting. That's when I discovered that the feature was not working anymore. This behaviour was double checked at the both events in our lab server to confirm the issue.

    What did happen between November and December? They and I only applied Windows Update in between. Not any hot fix or CUs were applied in the servers or in the desktops, so I suspect that this change of behavior came in one of the Windows/Office Updates.

    I hope this can help to add some light on the subject.


    Best regards, Ricardo Segawa Segawas Projetos Microsoft Partner
    Monday, March 28, 2011 11:25 PM