![]() Clear the permissions in the Global permissions section of the page using the new security template.Remove any security Categories added to the user account.Therefore, to simplify the security environment, the Project Server administrator must do the following: ![]() Doing this creates a much more complex security environment to manage. When a Project Server administrator adds Categories for a user account and sets permissions in the Global Permissions section of the page, all of these actions constitute an override to the permissions granted by the security Groups for that user account. Because of this, using this new security template makes it much easier to clear the permissions for an individual user account. Notice from the preceding steps that the new security template has no permissions set whatsoever. ![]() Enter a brief description of the template in the Description field and then click the Save button. On the Add or Edit Template page in PWA, enter a name such as No Permissions in the Template Name field.Ħ. The software displays the Add or Edit Template page shown in the following figure.ĥ. On the Manage Templates page, click the NEW TEMPLATE button. The software displays the Manage Templates page shown in the following figure.Ĥ. In the Security section of the page, click the Manage Security Templates link. Navigate to the Server Settings page in Project Server 2010 or to the PWA Settings page in Project Server 2013.ģ. Log into Project Web App with Administrator permissions.Ģ. To do this, complete the following steps:ġ. Creating a Security Templateīefore you can clear user permissions using a security template, you must first create the custom security template. Clearing the permissions for each user account is time consuming, but there is a way to speed up the process by using a custom security template. To resolve this problem, the Project Server administrator will need to clear the permissions for each user account individually, and then add each user account to the appropriate security Groups. The Project Server administrator then followed up to my reply, stating that he just inherited a Project Server instance in which the previous administrator set individual permissions for EVERY user account! He also stated that his organization is having all kinds of permissions problems because of this. I stated that setting permissions for each individual user creates a security environment that is difficult to manage. ![]() I answered his question in the affirmative yes, the best way to control user permissions is to add the user to the security Groups that grant the permissions needed by that user. In a recent post in the Project Online General Questions and Answers user forum, a Project Server administrator asked us to confirm that the best practice for controlling permissions for a user is to add the user to one or more security Groups, as needed. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |