none
Using protected baseline doesn't prevent unauthorised user to modify Baseline Start or Baseline Finish RRS feed

  • Question

  • Using protected baseline doesn't prevent unauthorised user to modify Baseline Start or Baseline Finish and publish the project. Any advice to help control or to prevent this behaviour?

    We use :  Project server 2010


    Wednesday, July 17, 2013 2:36 PM

Answers

  • Claude --

    The Save Protected Baseline permission, when set to Deny, only prevents a PM from updating the Baseline using the Set Baseline dialog (Project > Set Baseline > Set Baseline).  It does NOT prevent a PM from displaying the Baseline field and then manually editing Baseline Start date or Baseline Finish dates in that table.

    Is it possible your PMs are manually editing dates in the Baseline table?  If so, there is no built-in permission in Project Server to prevent this from happening.  Instead, you would need to make this a training and performance issue; train your PMs NOT to manually edit Baseline information in the Baseline table, and then hold them accountable for their performance.  Hope this helps.


    <p>Dale A. Howard [MVP<span>]</span><br/> </p>

    Friday, July 19, 2013 1:05 PM
    Moderator

All replies

  • Claude --

    The Save Protected Baseline permission, when set to Deny, only prevents a PM from updating the Baseline using the Set Baseline dialog (Project > Set Baseline > Set Baseline).  It does NOT prevent a PM from displaying the Baseline field and then manually editing Baseline Start date or Baseline Finish dates in that table.

    Is it possible your PMs are manually editing dates in the Baseline table?  If so, there is no built-in permission in Project Server to prevent this from happening.  Instead, you would need to make this a training and performance issue; train your PMs NOT to manually edit Baseline information in the Baseline table, and then hold them accountable for their performance.  Hope this helps.


    <p>Dale A. Howard [MVP<span>]</span><br/> </p>

    Friday, July 19, 2013 1:05 PM
    Moderator
  • Sorry for the delay.  I appreciate that you took time to answer.
    Monday, July 29, 2013 7:16 PM
  • Hi Dale

    We have untrustworthy PMs lol and whilst the Save Protected Baselines deny function gets us halfway there as a PMO lead, I wonder if we could use a Task Change event through VBA to check the user group and deny the commit across any of the baseline fields for the PM group?

    Thanks in advance

    Sean

    Tuesday, July 30, 2013 11:46 PM
  • I should be able to use

    expression .ProjectBeforeTaskChange2(tsk, Field, NewVal, Info)

    http://msdn.microsoft.com/en-us/library/office.vbapj.chm131165.aspx

    as it applies to changes applied before committal to the baseline fields, check the users group and then bypass the update and throw out a message.

    Will give it a go and let you know.

    Sean

    Tuesday, July 30, 2013 11:55 PM