Forum Discussion
Solved
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 als...
psawyer At the Environment level we do not have a group assigned, but we do have lower-level groups within the environment. Sounds like it is as simple as assigning a group at the Environment level to and only users in the group will show up in the Assigned To field? Is this correct?
- Yes, that is what I believe you need to do here. I don't know if you will need to remove the users or not. But all users will show up in the admin center who have access.
psawyer - Thanks, that worked! I wonder why Microsoft said this wasn't possible. Did you have any success limiting what a resource can do within a project, regardless of license type?
RodFromm Microsoft support for Project is pathetic. I have been working on stuff with them for months. Seriously their support is so bad I don't have words for how bad but I will try. Microsoft outsourced their support to a team who doesn't understand the product, then they pass the ticket around to avoid having to work on it.
As far as your access question. Yes. You can restrict or add access for parts on the entire project environment, or individual projects. The security works identically to how Dynamics works so that documentation is valid. The only thing you cannot do is get the "Limited" access function which was introduced last month. But you can get everything else.