Project Workspace: Permission Level erased from Customed group atworkspace creation

[Pelinski Guillaume]

Hello,

I have set 4 different custom groups on my workspace template:
- These groups are granted specific Permission Levels.
- The Permission Levels used for workspaces are listed in PWA.
- They are populated with Active Directory groups.

Yet, when a workspace is automatically created at project creation, the groups are created but they have no Permission Levels.

Checking off the option "Automatic Sync" in the Provisioning Settings appears not to be a solution because no one can access the workspace.

RESULT:
- The project owner (PM) can not manage Permission Levels, hence decide who can contribute/read the workspace.
- When a project is closed, he/she can't freeze the workspace by removing all contributor rights.

???????????????????????????????????????????????????
=> How can I prevent Project Server to erase the Permission Levels from the workspace custom groups?



----------------------------------------------------
DETAILS IN CASE YOU WANT TO UNDERSTAND MY SITUATION:

GROUP1: Wk-Admins
Perm. Level:
- Workspace-Administrators
Default Group members:
- Admin, ProjectServer
- ActiveDirectory\microsoft project administrators
- ActiveDirectory\microsoft project key users
At workspace creation:
The people who will manage the workspace are added:
- The PM
- His/Her boss

GROUP2: Wk-Users
Perm. Level:
- Workspace-Members
Default Group members:
- ActiveDirectory\microsoft project governance board
At workspace creation:
The people who will contribute on the workspace are added:
- All team members

GROUP3: Wk-Visitors
Perm. Level:
- Workspace-Visitors
Default Group members:
- NT AUTHORITY\authenticated users
At workspace creation:
The people not registered in Project Server who might need to access it are added.

GROUP4: 0-Group.To.Erase
Perm. Level:
- Workspace-Administrators
Default Group members:
- ActiveDirectory\microsoft project portfolio managers
- ActiveDirectory\microsoft project project managers
At workspace creation:
The group is emptied.This group grants by default the admin rights to all PM so that they can populate the different groups above with the relevant staff.
Once these groups are populated, there is no need to maintain 0-Group.To.Erase populated.


Submitted via EggHeadCafe - Software Developer Portal of Choice
Multi-Dimensional Arrays In ASP
http://www.eggheadcafe.com/tutorial...e59-3dae1c6edc36/multidimensional-arrays.aspx

 

[Jonathan Sofer [MVP]]

Hi Pelinski,

Gary and myself have already responded to your posts about this issue, I
don't think you are going to get any other responses on this other than what
you already have been given. Below is a summary:

- Permission levels are one of those items that do not come over with the
workspace template.
- The simplest solution is for you (as the administrator) to go in after the
workspace is created and to change the PM group permissions on the workspace
to allow the PM group to manage SharePoint permissions. This will have to
be part of your new project workspace setup process.

Otherwise, Gary suggested that you need to write your own permissions
synchronization routine rather than relying on the built-in routines. IOW,
you write a program to accomplish this. Your best bet for something custom
like this would be to post to the [microsoft.public.project.developer]
newsgroup.

Jonathan

in message

 

[. Guillaume]

Hi Gary,

I must admit that I understood it better this time.
Thanx for your patience and help.

Thanx for the hint on the developer newsgroup.

Guillaume



Jonathan Sofer [MVP] wrote:

Hi Pelinski,Gary and myself have already responded to your posts about this
11-Jan-10

Hi Pelinski,

Gary and myself have already responded to your posts about this issue, I
do not think you are going to get any other responses on this other than what
you already have been given. Below is a summary:

- Permission levels are one of those items that do not come over with the
workspace template.
- The simplest solution is for you (as the administrator) to go in after the
workspace is created and to change the PM group permissions on the workspace
to allow the PM group to manage SharePoint permissions. This will have to
be part of your new project workspace setup process.

Otherwise, Gary suggested that you need to write your own permissions
synchronization routine rather than relying on the built-in routines. IOW,
you write a program to accomplish this. Your best bet for something custom
like this would be to post to the [microsoft.public.project.developer]
newsgroup.

Jonathan

in message

Previous Posts In This Thread:


Submitted via EggHeadCafe - Software Developer Portal of Choice
VB.NET TCP Client - Server Socket Communications
http://www.eggheadcafe.com/tutorial...0cf-3619c1576dca/vbnet-tcp-client--serve.aspx