R
Roger C.
Can anyone tell me specifically which security/catetory setting allows a user
to change the owner? This appears to be an admin function, but I would like
to delegate this function to the project managers themselves.
Our administrators are not in the role of farming out projects. Because
projects come into existence long before most of them are actually begun, the
process we've created for our organization allows for project librarians
enter the shell of a project into the server - with no tasks - as soon as
it's approved, which is later picked up by an actual project manager.
Project managers use the PWA Project Details page to update our custom
enterprise project fields - the same place they'd change the Owner if they
had the rights to do it. I'd like to avoid having the project manager make a
call to the librarian or other administrator just to change the owner if I
can.
Because the out-of-the-box security settings and categories were not
appropriate for our organizational requirements, we've created and are using
our own - with the exception of the default Administrators group. In the
process, I've figured out that security in Project is multi-dimensional, and
getting the combination right is key. Unfortunately, it's not always
inherently obvious how to go about it. I'm hoping someone with more
experience here has the answer.
Thanks,
Roger C.
Cincinnati
to change the owner? This appears to be an admin function, but I would like
to delegate this function to the project managers themselves.
Our administrators are not in the role of farming out projects. Because
projects come into existence long before most of them are actually begun, the
process we've created for our organization allows for project librarians
enter the shell of a project into the server - with no tasks - as soon as
it's approved, which is later picked up by an actual project manager.
Project managers use the PWA Project Details page to update our custom
enterprise project fields - the same place they'd change the Owner if they
had the rights to do it. I'd like to avoid having the project manager make a
call to the librarian or other administrator just to change the owner if I
can.
Because the out-of-the-box security settings and categories were not
appropriate for our organizational requirements, we've created and are using
our own - with the exception of the default Administrators group. In the
process, I've figured out that security in Project is multi-dimensional, and
getting the combination right is key. Unfortunately, it's not always
inherently obvious how to go about it. I'm hoping someone with more
experience here has the answer.
Thanks,
Roger C.
Cincinnati