Challenging part while using new version of any product is to find new location of features/options within new version, if they are no longer available on the same spot as of their former version.
This post will help you to find key feature of Project Server 2013, Security Settings in Project Server 2013, that used to be under server settings of Project Server 2010.
With the introduction to new security mode in Project Server 2013, i.e. :SharePoint Permission mode, your new PWA by default will provision with SharePoint permission mode and hence you will find Security section missing from PWA server settings page.
Advantages, and what is enabled and what is not, while staying with SharePoint security mode are detailed here: http://technet.microsoft.com/en-us/library/fp161361.aspx
Out of the above article, and with R&D i have done so far, the major features you were not be able to use in SharePoint security mode are as follows:
In order to switch the permission mode back to Project mode, use the following windows powershell cmdlet:
For detail of above cmdlet, see this technet article:: http://technet.microsoft.com/en-us/library/jj219486.aspx
Once the prompt will be back after execution, refresh the PWA server settings page to see the Security group available to be used.
Note that Switching security modes deletes all permissions configuration information for the specified Project Web App instance and reverts to the default settings for the specified mode. You need to be carefully planning this well in advance that which security mode you have to configure.
This post will help you to find key feature of Project Server 2013, Security Settings in Project Server 2013, that used to be under server settings of Project Server 2010.
With the introduction to new security mode in Project Server 2013, i.e. :SharePoint Permission mode, your new PWA by default will provision with SharePoint permission mode and hence you will find Security section missing from PWA server settings page.
Out of the above article, and with R&D i have done so far, the major features you were not be able to use in SharePoint security mode are as follows:
- Unable to edit default permission of groups
- RBS
- categories
- Delegation
As you are aware that permissions in PS 2010 and PS 2007 was the combination of security groups, categories and RBS. SharePoint security mode helps get rid of this complexity and provide single forum for system admins, i.e. SharePoint groups, to configure permission for PWA as well.
SharePoint Permission Mode creates SharePoint groups that directly correspond to the default security groups found in Project Permission Mode. These default security groups include the following:
- Administrator
- Portfolio Managers
- Portfolio Viewers
- Project Managers
- Resource Managers
- Team Leads
- Team Members
I have modified the quick launch in above screen shot to show you all the relevant groups, however you can click on Groups link on the top to access to full list of groups.
Using of SharePoint security could be beneficial for naive organizations or to those who are willing to run project management business without creating data access layers based on user role defined through RBS. There could be several more reasons of using PWA in SharePoint security mode as well.
The recommended way of adding user to group is still the Active Directory synchronization, available through server settings.
In order to switch the permission mode back to Project mode, use the following windows powershell cmdlet:
Set-SPProjectPermissionMode [-Url] <Uri> [-Mode] <SharePoint | ProjectServer | UninitializedSharePoint | UninitializedProjectServer> [[-AdministratorAccount] <String>] [-AssignmentCollection <SPAssignmentCollection>]
For detail of above cmdlet, see this technet article:: http://technet.microsoft.com/en-us/library/jj219486.aspx
Once the prompt will be back after execution, refresh the PWA server settings page to see the Security group available to be used.
Note that Switching security modes deletes all permissions configuration information for the specified Project Web App instance and reverts to the default settings for the specified mode. You need to be carefully planning this well in advance that which security mode you have to configure.
