Permission and Category

[Andy]

Recently, we have deployed a Microsoft Project Server for testing. I have
read some books about category and group. There are default groups such as
Resource Managers, Executives, Team Leads.... We will have two depts using
the project server. The plan is the two dept can only see projects from
their own dept.

In this case, I need to create a Team Lead 1 group for dept 1 and another
Team Lead 2 group for dept 2.....etc for the rest of groups. Then, I need to
create a Category such as Dept 1 Reports and another one called Dept 2
Reports with similar permission as one of the default Category "My Direct
Reports". After that, scroll down to the "Select the projects that users in
this category can view". For Category Dept 1 Reports, add the projects for
Dept 1. Does it sound correct?

Is there any option I can copy groups?

Thanks,

Project 2003 Server beginner

 

[Dale Howard [MVP]]

Andy --

I think your decision to use a single Project Server 2003 instance for the
two departments is going to drive you crazy. You are correct that you will
need to create a totally new batch of Groups and Categories to control who
can see what projects and what resources in the single Project Server 2003
instance. Worse still, your solution would be terribly "labor intensive"
since every time a new project is saved for one of the two departments, you
will need to manually add that project to the correct department's Category.
If the two departments are not going to share resources across projects, I
would recommend instead that you create a second Project Server 2003
instance using the EditSite tool. Set up the first instance for the first
department and set up the second instance for the second department. This
way, you could keep all of the default Groups and Categories in each
instance, and do other more important things with your time!

Hope this helps.

 

[Stephen Sanderlin]

I obviously do not know all of your requirements, but in a situation
like this, I would build an RBS to filter the visible data rather than
creating a plethora of Groups and Categories -- that is, assuming that
your basic permissions are the same between the two organizations and
you're merely looking to control data visibility.

--
Stephen Sanderlin
Owner/Founder - EPMFAQ
http://www.epmfaq.com/
http://forums.epmfaq.com/

EPM Solutions Architect / Principal Consultant - BT Professional
Services
http://bt.ins.com/

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.

 

[Paul Conroy]

A single instance would also be a must if you want to report effectively
across the two departments.

There a certainly pro's and con's to each solution, and you should give
careful thought before comitting to either.

--
Did this post help you. Consider passing on the good will by making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com

 

[Andy]

Thanks for all your help. Eventually, we decide to use EditSite Tool.

 

[Dale Howard [MVP]]

Andy --

A wise decision, my friend. I think you will find this a much easier
solution.