Forum Discussion

JanVanek's avatar
JanVanek
Copper Contributor
Jul 24, 2024

Project for the Web - how to prevent Assign Project Task to Contact or Account from Power App?

Hi, our customer has noticed that if he wants to assign a task to a colleague and he starts typing e.g. the first 3 letters of the name, the whisperer offers not only user names from Entra ID but also Contacts and Account names from the connected Power Application Project. How to prevent this? It is not desirable, project tasks are only assigned within the organization.

Thank you for help, Jan

  • JanVanek I'm not aware of a way to accomplish, but it would be nice.  Typically, in a PMO you want to control the resources in your environment/projects, but this is not how they designed Planner Premium.

  • RodFromm's avatar
    RodFromm
    Steel Contributor

    JanVanek I'm not aware of a way to accomplish, but it would be nice.  Typically, in a PMO you want to control the resources in your environment/projects, but this is not how they designed Planner Premium.

  • psawyer's avatar
    psawyer
    Iron Contributor
    If you are in a non-default environment then you can limit access to the application on the powerapps admin side. You can limit access to a specific group of users, those users would be the only users who would show up, except any manually created contacts.
    • RodFromm's avatar
      RodFromm
      Steel Contributor

      psawyer Can you elaborate on how to do this?  We have done extensive testing and could not limit who showed up in the Assigned To list and consulted with Microsoft who confirmed this is by design.

      • psawyer's avatar
        psawyer
        Iron Contributor
        Sure. Microsoft support for Project is an embarrassment.

        You need to be running in a non-default environment. Then you need a group for all the employees you want to assign tasks to. So if you have a group to separate out internal vs external users use that. Then from this page https://admin.powerplatform.microsoft.com/ you add in the security group for who can access the environment.

        I had the opposite problem. When I created the environment I put a security group in, and I couldn't assign tasks t anyone outside that group. So I removed the security group, and when that happened I could assign tasks to all users in my org. There is a microsoft article on it.

        You have to use a non-default environment which has a couple limitations, but the reporting and ability to customize the environment is worth it IMHO. If you need more info let me know.

Resources