Permission Management
Owner should be able to manage permissions to tasks, and by default a task should be only visible to "Assigned To" where he can only edit progress and comments, everything else should be editable by the Owner.

6 comments
-
Marie Altobelli commented
Permissions management requires some attention to be useful, our users aren't willing to make the sacrifices in security even though they like the interface better than Project Online.
Some Suggestions:
* Allow Project level security to individuals instead of groups. If I have 120 projects that have 1-2 people on each project, I don't want to have to create and manage a group for each project. Even allowing linking to a restricted teams channel would be better.
* Allow for re-assignment of project owners
* Consideration for confidential projects. very limited audience with no visibility to anyone except project members. Confidentiality must be assured.
* Provide a way to set read-only access to a project even if a user has Plan 3.
* Allow setting that gives no access to see a project (or even the existence of the plan). May need to work even if user is assigned to tasks
* RLS in Power BI -
Tijn commented
Desperately need this feature - need ability to have certain users only be able to complete a task and not change other fields on task. Also need ability to restrict users to only update their own tasks and not all tasks in the project.
-
Dagon commented
Please include an easier way to assign new owners. Currently, the only owner is the person that created the project plan. This means only that person can add new team members.
-
Peter Kestenholz commented
Currently any resource allocation to a task in P4W automatically provides the resource/user with full owner rights to the "Project" entity = allowing them to delete projects and do changes to the "Project" forms.
-
Anonymous commented
Definitely - currently any team member can change anyone's tasks, deliberately or by mistake and this is an issue especially for bigger teams
-
Steve commented
Project (for the Web) - Allow the Project Manager (Owner) to define a security matrix for different user roles on the project and what they are able to do. Things like: Who can delete a task, who can change or see key fields - for example costs;
This would be totally user defined.