External dependencies and permissions

[Chris]

Hello,

two PMs wanted to use external dependencies to connect their schedules but
they didn't have permission to do it (each PM was only allowed to modify his
own schedule).

I temporarily gave one of the PMs additional permissions and he was able to
create the external dependency. I then switched back to the initial settings.

Now the PM who created the external dependency is still able to modify both
schedules, while the other PM can only edit his own schedule. Is this normal?
How can I get back to my original configuration: each PM can only modify his
own schedule?

Thanks,

Chris

 

[Garon]

I am not sure if this is normal as I have never tried the scenario myself.
However, a suggestion that may work to get you back to the original situation
is remove all of the cross project dependencies and check the user
permissions again to ensure that the managers only have access to the
appropriate projects.

Check the RBS based authorities. I make sure the resources are not assigned
to tasks in projects you do not want them to have access to. You could also
try checking that the resources are removed from the Resource lists of
Projects you do not want them to edit.

Regards
Garon Line

 

[Chris]

Hello,

let me precise my question: I want to get back to the original permissions
(each PM can only modify his own project), but I need to keep the cross
project dependencies.

Thanks,

Christophe