![]() |
| |||
| I apologize again for my newbie questions, but theres twos things I like clairification on. Firstly when you create project and want to add users / resources , heres what I do. Edit the project, then select build team, then I just add users I want as resources for the project. However, I also notice in the main Project Center (Proposal and Acitivities) there is a resource plan button. What is the difference from building a team and creating a resouce plan? My other question regards user/admin privileges. For example, I tried a few test cases myself and I'm a little confused. For example, if a certain user is set as a team member, but I create a new project and assign them the administrator of the project, they aren't able to publish the project or do anything (I suppose this is normal?) But if a user with project manager privileges is just a resource of a project, they seem to also be able to edit the project. I do not want this to happen, so is there anything I can do? Basically, if I have a team of people, is it possible to set the permissions so that they are all "members", but can have manager privileges (i.e. approviing changes) for only a specific project, while only member for other projects going on at once? I suspect all of this may have sometihng to do with setting permissions. When I edit a user's settings, is it sufficent to just set the security group they belong to, or should I only set their global permissons, or both? Any help is appreciated! |
| Sponsored links |
| |
| ||||
| Quote:
Quote:
Quote:
Quote:
__________________ Stephen Sanderlin Founder/Owner - EPMFAQ Principal Consultant - MSProjectExperts If you found this message useful, please click the Thanks button in the post! This electronic message, along with any information, advice, and opinions it contains, are mine alone and are not representative of my employer. All information is provided in "GOOD FAITH" and on an "AS IS" basis only. I provide no presentations or warranties, express or implied, including implied warranties of fitness for a particular purpose, merchantability, title, and noninfringement. I strongly advise you to extensively test any changes, workarounds, or techniques described herein on a development system prior to implementation in a production environment, and you are hereby notified that I bear no responsibility whatsoever for any loss, harm, or otherwise negative outcomes resulting from your actions, whether or not said actions were a result of this electronic message, directly or indirectly. |
| ||||
| You may also want to pick up copies of Implementing and Administering Microsoft Office Project Server 2007 (Epm Learning) and Managing Enterprise Projects Using Microsoft Office Project Server 2007 (Epm Learning), which go into a number of topics in detail including Resource Plans and Security.
__________________ Stephen Sanderlin Founder/Owner - EPMFAQ Principal Consultant - MSProjectExperts If you found this message useful, please click the Thanks button in the post! This electronic message, along with any information, advice, and opinions it contains, are mine alone and are not representative of my employer. All information is provided in "GOOD FAITH" and on an "AS IS" basis only. I provide no presentations or warranties, express or implied, including implied warranties of fitness for a particular purpose, merchantability, title, and noninfringement. I strongly advise you to extensively test any changes, workarounds, or techniques described herein on a development system prior to implementation in a production environment, and you are hereby notified that I bear no responsibility whatsoever for any loss, harm, or otherwise negative outcomes resulting from your actions, whether or not said actions were a result of this electronic message, directly or indirectly. |
| ||||
| You're welcome. Let us know if you need anything further!
__________________ Stephen Sanderlin Founder/Owner - EPMFAQ Principal Consultant - MSProjectExperts If you found this message useful, please click the Thanks button in the post! This electronic message, along with any information, advice, and opinions it contains, are mine alone and are not representative of my employer. All information is provided in "GOOD FAITH" and on an "AS IS" basis only. I provide no presentations or warranties, express or implied, including implied warranties of fitness for a particular purpose, merchantability, title, and noninfringement. I strongly advise you to extensively test any changes, workarounds, or techniques described herein on a development system prior to implementation in a production environment, and you are hereby notified that I bear no responsibility whatsoever for any loss, harm, or otherwise negative outcomes resulting from your actions, whether or not said actions were a result of this electronic message, directly or indirectly. |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|