What is the difference between Security Templates and User Groups??

[Alfredo Barrientos]

Hi,

In Project Server 2003, What is the difference between Security
Templates and User Groups??

Thanks,

Alfredo Barrientos

 

[Dale Howard [MVP]]

Alfredo --

Security Templates are a rapid way to set permissions in a new custom Group.
For example, I want to create a new custom Group that has similar
permissions to those who are members of the Portfolio Managers group. When
I create the new custom Group, I can set the permissions in the Global
Permissions grid using the Portfolio Managers template, and then I can edit
the permissions as needed. Hope this helps.

 

[Alfredo Barrientos]

Thank you very much Dale. I have another question.

We have implemented an EPM solution, just with one project, with a
defined RBS.

Now, my client wants to implement other project, but in the past
scenario person B reports to person A, now person A reports to person
B. How can i do this?? I mean, I can have just one RBS!

Thanks,

Alfredo Barrientos

 

[Dale Howard [MVP]]

Alfredo --

The RBS outline code field shows "who reports to whom" in the organization,
and is used to control security within Project Server. You cannot set this
on project by project basis. I believe both you and the client are
misunderstanding its purpose and are using it incorrectly. Hope this helps.

 

[Alfredo Barrientos]

Hi Dale, thanks,

Well, i am trying to set this configuration

RBS
Rol1
Rol2

Project A
Person2 reports to Person1
Person1 can see the Project A's details, in Projects menu in PWA

Project B
Person1 reports to Person2
Person2 needs to see Project B's details, in Projects menu in PWA.

How can i do this? using categories??

Thanks,

Alfredo Barrientos



Dale Howard [MVP] (dot at dot) ha escrito:

 

[Dale Howard [MVP]]

Alfredo --

RBS is a Resource outline code, and as I stated previously, it shows "who
reports to whom" in the organization. You cannot use it the way you wish
with projects. The best I can tell you is that Person 1 and Person 2 should
both be in the Executives group so that each of them can see the projects
they wish to see. Hope this helps.

 

[Alfredo Barrientos]

Hi Dale,

Thank you very much to answer me.

Then, i could affirm "Project Server 2003 does not allow any way to
support Projects from Matrix Organizations".

Alfredo Barrientos



Dale Howard [MVP] (dot at dot) ha escrito:

 

[John M.]

Alfredo,

You are bound to get a several responses to your statement as you seem to
have made quite a leap from your sample to that broad assumption.

EPM "out-of-the-box" has a pre-populated security model that supports matrix
organizations. The functional organization represented by the resource
manager role and RBS while the project organization represented by the
project manager and team members on the project. I don't quite understand
how you logically came to the conclusion given the sample that you included.
Having two people (person 1 and person 2) that report to each other is a new
type of organization design that I am unfamiliar with...in fact it would be a
great way to ensure mutual success through collusion, but I digress.

As for your previous example... if you have the "out-of-the-box" security
groups/categories/permissions then try assigning Person 1 and Person 2 to the
project manager group and have them as team members on each project. They
should both have the permissions to view the projects. The default for the
"My Projects" category is to include all projects that the resource is a team
member of (in addition to projects that they manage and projects that
resources that they manage are assigned to). The Project Manager group
should include the "see projects in project center," "see projects in project
views," "open project," and "save project" permissions on the My Projects
category. If this doesn't make sense, I would recommend studying the
security model a little more to understand the available flexibility. Then
you should be able to modify it to model your situation.

Good luck.

John M.

 

[Dale Howard [MVP]]

Alfredo --

I don't think that the static RBS outline code structure will work very well
in your environment, given the fluid nature of "who reports to whom" in your
organization. Hope this helps.

 

[Dale Howard [MVP]]

John M --

Thanks for jumping into this discussion with some additional ideas.