What are roles and core sets?

Once the permission categories are set, Administrators can match a category to a user set. A core set is one type of user set and is a group of users based on the users' role with respect to the Permission Target. This article describes the purpose of core sets.

1. Click Defaults

Click Defaults
  1. On the Icon Bar click the Admin button.
  2. Click Permissions to expand the menu, then click Defaults.

2. Core Sets for Project Tasks Permission Target

The core sets for the Project Tasks permission target dictate what permissions a user has on a project depending on what role they have been assigned to on the project.

By default, there are 9 core sets for the Project Tasks permission target:

  • Owner: The user assigned as the Owner of the project.
  • Financial Reps: The user assigned as the Financial Rep for the project.
  • Higher Financial Reps: Users assigned to the Financial Rep role on parent work items.
  • Champions: Users assigned to approve gates on the project.
  • Higher Champions: Users assigned to the Champion role on parent work items.
  • Contributors: Users that accept invitations to join the project.
  • Everybody: All other users.

Administrators can expand this list by creating additional custom roles. See the article How do I create a role? for more information.

3. Core Sets for Users Permissions Target

When you set default permissions for user accounts, you must choose one of the following policy options:

  • Users can edit their own Profile and Preferences, but they cannot edit their permissions: The user can make changes to information on their profile and in their preferences, but cannot view or edit their permissions.
  • Use the Self User core set to define permissions users have to themselves: The user will have the permissions that are defined by the Self User core set below.
  • Users have full permissions to themselves: The user will have full permissions to edit all things pertaining to their user account.

There are 2 core sets for the Users permission target:

  • Everybody: Refers to the permissions that everyone else in PowerSteering has for a user profile.
  • Self User: Refers to the permissions that a user has for their own user profile. It is likely that the Self User will be configured to have greater access than the Everybody core set.

4. Core Sets For Groups Permission Target

When you set default permissions for groups, you must choose one of the following policy options:

  • Owners can edit, delete, or delegate the Group, as well as add or remove members; all other users can only view the Profile and Load: The owner of the group can edit, delete, or delegate new ownership for the group and can also add and remove members. All other users will only be able to view the group profile and its members.
  • Users have permissions to the Group as defined in the permissions table below: Group members and all other users will have the permissions that are defined by the core sets below.

There are 2 core sets for the Users permission target:

  • Group Members: Refers to the permissions that group members have for a group.
  • Everybody: Refers to the permissions that all other users have for a group.

5. Core Sets for Metric Templates Permission Target

There are 2 core sets for the Metric Templates permission target:

  • Team Members: Refers to the permissions that group members have for a group.
  • Everybody: Refers to the permissions that all other users have for a group.

6. Core Sets For Contexts Permission Target

There is 1 core set for the Contexts permission target:

  • Everybody: Refers to the permissions that all other users have for context permissions.

7. Core Sets For Manage Time Permission Target

There is 1 core set for the Manage Time permission target:

  • Everybody: Refers to the permissions that all other users have for manage time permissions.

0 Comments

Add your comment

E-Mail me when someone replies to this comment