Implied Permissions for Entity Owners
Some entity owner rights are built-in, or implied, for the resource that currently owns an entity. These permissions cannot be taken away (unless the resource is no longer the entity owner), but can be augmented with a permission profile. For example, a project owner always has the right to view and edit the Details section of projects they own.
- Implied permissions are a set of rights granted to the owner of an entity - these rights are not adjustable.
- Profile permissions are rights that are configured in a permissions profile by checking the appropriate entity/permissions in the permissions hierarchy.
While an entity owner's implied permissions cannot be reduced, they can be augmented using a profile configured with an Owner rule. For example, say you wanted to expand the implied rights for all project owners and add Delete permission. You can create/modify an Owner profile and configure the Project > Delete permission in the Permissions Hierarchy. Now project owners will have their implicit view/edit Details permission, along with permission to delete any project they own. If you wanted to augment the owner rights for one project in particular, you could add the owner to the project team along with a Team profile that grants additional permissions to the project. You can use this technique for any entity owner.
To summarize: owner profiles (profiles that use the Owner rule) are not required, but are available if you want to give entity owners additional permissions on every instance of an entity they create.
Note for project owners: When creating a project from a template, the current user will be defaulted in as the project Owner. However, while in the New Project Wizard, the current user can select a different resource to be the project owner. Once the project is created, only users with Project > Edit > Owner permission can change the project Owner.
Note for task owners: Some fields on the task Details tab directly affect other tasks or the parent project. Default task owner permissions will exclude edit permissions on the following fields. In order to edit these fields, users need Project > Edit > Tasks permission and possibly Project > Edit > Detail (if the parent project needs to be updated based on an edit to one of the fields below):
- Start Date
- Target Date
- Duration
- Manually Scheduled?
- Active?
- Constraint Type
- Predecessor
- Successor
- Scheduled Resources
- Is Capitalized?
- Work Effort
- Billing Type
Note for request owners (requesters): The requester (owner) field is not required for requests. The current user is defaulted in as the Requester. If the request is configured to show the Requester field on New, and/or editable on the resulting request, then the current user can assign a different resource as the Requester either while creating the new request or editing it at a later date.