Join John Riopel for an in-depth discussion in this video Managing permissions, part of Microsoft Project Server 2013 Administration.
- In Project Server 2013, it's important to plan the user access prior to doing your implementation. There's two modes that come with Project Server 2013. The traditional Project permission mode. This is the categories, groups, RBS-node. These are all the functions that previous versions of Project 2007, 2010 and now 2013 still have. However, out of the box, new to 2013 is a SharePoint permission mode.
This is a light-weight, easier to manage SharePoint permission model that's been role-based as well, however it starts at the SharePoint level and makes it easier to sync SharePoint groups with Project Server groups, so there are the same groups in SharePoint as were, and still apply, in Project Server 2013, however, these groups don't get to the same level of granularity, as the previous Project permission mode allowed.
All users, by default, will be added to your Project Server SharePoint model, that is the default permission mode. There is a PowerShell script that allows you to transition your server from a SharePoint model to a Project Server permission model, however you need to do that early on because any changes in moving from one mode to the other will lose the permission set for that particular model. So you'll want to make that decision early on. They are based again similar.
They have the same types of groups in both cases between SharePoint and Project Server so there's team members, there's project managers, there's resource managers, portfolio managers and all of the traditional Project Server groups. Again, however they don't get to the same permission level that you would if you go to the Project Server mode and features within the tool, as you can see by this grid, are also not apparent for you, so you lose the ability to create custom security categories.
You lose the ability to have the RBS in the SharePoint mode model, so you might want to consider that as you move forward. Also, the last piece of the permission set in Project Server 2013, you still have the ability to turn on off features using the allow and deny functions as well as the "not allowed" option. In SharePoint, that model of changing features within each of the categories is not available to you.
Early on, make a decision, figure out which mode might work for you, and check out these two options SharePoint permission mode as well as Project Server permission modes.
- Managing users, groups, permissions, and categories
- Working with enterprise custom fields and lookup tables
- Working with enterprise calendars
- Managing enterprise objects
- Managing views
- Adjusting time and task settings
- Changing and restarting workflows