Limited Edit Access RRS feed

  • Question

  • Hi,

    Is it possible to provide limited access to Project Manager / Project Team Member with access to only:-

    1. Actual updation via MSP in connected mode (EPM)

    2. Updation of a particular baseline # while ensuring PM is unable to edit other baselines

    3. Restricting access to edit start / finish / duration & linkages (Predecessors / successors)

    Monday, May 20, 2019 6:05 PM

All replies

  • Scatterworlds --

    The answers to your questions are:

    1. The project manager views tasks updates from team members in his/her project on the Approval Center page in Project Web App.  On this page, he/she can either approve or reject the pending task updates.  When he/she approves the updates, the system pushes the data into the Microsoft Project schedule.
    2. Baseline control is not as fine as you hope.  You can use Group permissions in PWA to lock down the baselines named Baselines 0-5.  These are called Protected Baselines.  You can also lock down Baselines 6-10, which are called Unprotected Baselines.  You CANNOT lock down one particular Baseline, however.
    3. If a project manager is allowed to open and edit an enterprise project, he/she automatically has permission to edit the project as needed.  This means you cannot lock down Start dates, Finish dates, Durations, or task dependencies.

    Hope this helps.

    Dale A. Howard [MVP]

    Monday, May 20, 2019 7:21 PM
  • Thanks Dale for the update.


    Eg. there are approx. 20 set of actual progress updates done for the Project tasks / activities.

    Can it be identified from MSP Enterprise in connected mode or via Custom or Macro that

    1. What all changes passed through the approvals system via EPM while what all were directly done in the MSP connected mode bypassing the approvals cycle.

    2. What all changes were done at what date & time

    3. Who all did the changes

    The above said is needed wrt reporting & control as the Project has multiple Project Managers & Planners working upon the Project.

    Tuesday, May 21, 2019 1:56 AM
  • Scatterworlds --

    The answers to your latest questions are:

    1. No
    2. No
    3. No

    I think the source of your problem is allowing multiple PMs to manage a single project.  If it were me, I would break up the project into multiple projects, each of which is managed by a single PM.  Just a thought.  Hope this helps.

    Dale A. Howard [MVP]

    Tuesday, May 21, 2019 1:57 PM