G
Graeme
Following advice posted to others in this forum I have
been able to make plans read-only to all PMs (via my org
category, open project rights) and read-write to only the
owning PMs (via my projects category, save project rights)
which is just what we want.
However, this works fine up to a point, as soon as a
resource with the Project Manager group becomes a team
member on a project (with a published assignment) they
also get rights to save that project as it is now in their
my projects category.
Couple this with the fact that across our large programme
we want to assign issues/risks across teams then PMs have
to have a published assignment on any project then need to
be assigned an issue/risk (without this the issues risks
don't appear on their PWA homepage) then very quickly we
end up back to the all PMs having read-write access to all
projects in the programme.
Does anyone have any solution to this?
been able to make plans read-only to all PMs (via my org
category, open project rights) and read-write to only the
owning PMs (via my projects category, save project rights)
which is just what we want.
However, this works fine up to a point, as soon as a
resource with the Project Manager group becomes a team
member on a project (with a published assignment) they
also get rights to save that project as it is now in their
my projects category.
Couple this with the fact that across our large programme
we want to assign issues/risks across teams then PMs have
to have a published assignment on any project then need to
be assigned an issue/risk (without this the issues risks
don't appear on their PWA homepage) then very quickly we
end up back to the all PMs having read-write access to all
projects in the programme.
Does anyone have any solution to this?