Power Platform Community Forum Thread Details

Hi,

I've set up Project for the Web accelerator.

I'd like to share it with the team.

I'm having trouble because the project's owner/project manager is unable to create tasks.

I tried giving permission using the roles Project User, Project Team Member, Project Common, Project System, and so on, but nothing worked.

It displays limited access in the task area. I want to limit all users' permissions so that they can only modify their own projects/tasks, while other projects should be displayed in read-only mode.

Thanks for reading!

Categories:

Microsoft Dataverse with Power Apps

Hi,

It sounds like the issue is related to the security model within Microsoft Dataverse, which governs Project for the Web’s access rights. By default, the ability to create tasks is tied to the user's security role and access level within the environment.

Steps to Resolve:

Verify Security Role Permissions
- Ensure that the project owner/project manager has a security role that includes the Create and Write privileges on the msdyn_projecttask table.
- The Project User or Project Team Member roles may not have sufficient privileges by default. Instead, consider customizing these roles or assigning a role with the necessary permissions.
Check Business Unit and Ownership Structure
- If your organization is using Business Units, confirm that the project owner is assigned to the correct unit with appropriate access levels.
- If the project is owned by a different business unit, you may need to adjust security role access at the Parent: Child Business Unit level.
Ensure Proper Table Access in Dataverse
- Navigate to Power Platform Admin Center → Security Roles.
- Locate the role assigned to the project manager and verify that the msdyn_projecttask table has at least User-level Create and Write access.
Apply Read-Only Permissions for Other Users
- To restrict users from modifying other projects while allowing them to edit their own:
  - Use a custom security role where Read access is set at the Business Unit or Organization level.
  - Ensure Write and Delete permissions are set at User level to restrict edits only to their own tasks.
  - Avoid assigning Append and Append To privileges broadly, as these control linking records across entities.
Test with a Sample User
- After applying changes, test with a sample user account to verify that project managers can create tasks and other users have read-only access to non-owned projects.