none
Edit Project Summary Fields Category Permission RRS feed

  • Question

  • Hi,

    I'm having a bit of an odd issue in that a PWA security group has Edit Project Summary Fields but not Save Project to Project Server. When members of this group try to save edits to custom fields on a PDP, they receive an error stating: You need to have permissions to create a new project.  Please ask the project Web App administrator for permissions.  What does happen is that the value is changed for draft version of the field, but not the published version (i.e. once the project is checked in, the edit "disappears" until checked out again).

    What is confusing is that with the same permission configuration in 2010, members of the group are able to edit the custom fields just fine. 

    I've tried various combinations of other permissions, but the Save to... is the magic one.  Of course, this creates the issue that people are able to edit project schedules when they should not have that ability.

    This is an on-premises installation of Project Server 2013 running the February 2015 CU.  I've also tested this on another system and get the same behaviour so I am led to believe it is by design.  Microsoft's documentation states:

    Allows a user to edit only the enterprise project fields shown in the new project fields Web Part. If you do not have this permission, but have "Save Project to Project Server" you can still edit project-level fields/custom fields in the project field Web Part.

    Am I missing something?

    Chris

    Friday, May 8, 2015 9:59 PM

All replies

  • I am seeting the same issue in Project online. We have SharePoint security set up and occuring for Portfolio Managers.

    Friday, June 19, 2015 2:47 PM
  • Hi Chris,

      Possibly not a direct answer, but in your situation what I would have done is devise a custom template inheriting the same permission as a PM does and then start removing the checks that are not needed. in PS 2013 rule of thumb seems to be you need to have PM permissions to do these changes. If you want users not to touch schedule then in your custom template you can uncheck the checkboxes for schedule. 

      Regards,

    Faizan.


    Regards, Syed Faizan ur Rehman, CBPM®,PRINCE2®, MCTS

    Sunday, June 21, 2015 6:01 AM
  • Hi Syed,

    The issue isn't one of general permissions, it's that the particular permission I describe is not consistent with the behaviour that was present in Project Server 2010.  It feels like an oversight, because according to the 2013 category permissions, it should be possible to allow someone to edit custom fields through PWA without giving them the ability to modify the schedule.  The problem is that empirical evidence doesn't support the configuration, and more powers than are necessary need to be granted.

    Friday, July 3, 2015 7:55 PM
  • Having the same issue. Do you found the resolution?
    Tuesday, September 22, 2015 3:55 PM