Clarity

  • 1.  Removing Project Resources - Security Question

    Posted Jul 02, 2009 10:59 AM
    Does anyone know what specific security right is required in order to perform the task outlined below?           Removing Participants from Projects  Collaboration managers can remove participants from projects.1Select the Team tab. The Project Team: Staff page appears by default.  2Select the Participants sub-tab on the team page toolbar. The Project Team: Participants page appears. 3Select each participant you want to remove from the project.4Click Remove . The Remove Participants Confirmation page appears. 5Confirm the removal prompt by clicking Yes . The selected participants are removed from the project.              Actually, our environment doesn't allow us to remove resources from the 'Participants' sub-tab but does under the default Team tab of 'Staff'.     Thanks


  • 2.  Re: Removing Project Resources - Security Question

    Posted Jul 02, 2009 01:22 PM
    Yeah, its good one this!  "Participants" are not controlled like any of the other security / access rights in Clarity, a completely different security model applies!  The answer actually is in the text you posted, but you don't realise it!  There is this "special" role associated with a project, known as the "Collaboration Manager".   When a project is CREATED, then the user who created the project becomes it's "Collaboration Manager".   The "Collaboration Manager" controls the "particpiant access" to the project and they can add resources as "participants" (as opposed to "Staff") on the project. They can also make other existing participants into "Collaboration Managers".  The only person who can REMOVE participants from the project is a (any) "Collaboration Manager".  If you look on the "Participants" tab you can see who the current "Collaboration Manager" is - they will have a funny icon next to their name.   If you have never changed this, then the ONLY "Collaboration Manager" will be the original project creator and ONLY they can remove the particpants.   (Not even system admins can do this otherwise!).  The workaround to adding participants if you are not a "Collaboration Manager" is to add them as a TEAM member and then remove them, this leaves Participant access - this feature is what you have stmbled upon!!    I said it was great didn't I?   ;-)  So you have to log on as the project creator user and remove the participants OR set up an admin user as another "Collaboration Manager" for the project so you don't have to this again!  David MortonCapgemini        


  • 3.  Re: Removing Project Resources - Security Question

    Posted Jul 03, 2009 02:49 AM
    Hi,    As dave rightly said either the project creator will be defaulted as CLB mgr and the partcipants who has been made as CLB mgr can remove the partcipants.Normally an PMO or an PM will  create an project  so they/he will be an CLB Mgr for that project.If an change in PM comes (when the PM resigns)  and    if  his replacement  is late,the new user will not be updated as CLB Mgr for that project and that user when joins as PM will not have  the CLB rights then what to  do?.Even the sys admin will not have the rights to update it.     By this way you can achieve it via DB.       Iam doing this for past 5 years with no issues,i will update the cmn_sec_user_groups table and will make either the new PM userid or the system admin user id,then it will be ok.     In this table CLB_PROJECT_GROUP_KEYS the PROJECT_MANAGERS_GROUP_ID column is the Collaboration Manager and  PROJECT_MEMBERS_GROUP_ID   is the Participants and projectid is the project internal id.      UPDATE CMN_SEC_USER_GROUPS G SET G.GROUP_ID=(SELECT PROJECT_MANAGERS_GROUP_ID FROM CLB_PROJECT_GROUP_KEYS k WHERE  K. PROJECT_MANAGERS_GROUP_ID =G.GROUP_ID) WHERE G. USER_ID = 5389100 AND G.GROUP_ID= 5017684      UPDATE CMN_SEC_USER_GROUPS G SET G.GROUP_ID=(SELECT PROJECT_MANAGERS_GROUP_ID FROM CLB_PROJECT_GROUP_KEYS k WHERE  K. PROJECT_MEMBERS_GROUP_ID =G.GROUP_ID) WHERE G. USER_ID = 5444537 AND G.GROUP_ID IN  (SELECT PROJECT_MEMBERS_GROUP_ID FROM CLB_PROJECT_GROUP_KEYS WHERE PROJECT_ID = 5000056)      Note:- An user must be an participant to become an CLB Mgr.     And one more very important thing is that removing an participant (if resources resigns or moved to another project or the project is In active) is an best practice and also it will help an lot regarding app performance.The participant will have default rights against all files / folders related to that project,so by removing it the records will deleted in the CMN_SEC_ASSGND_OBJ_PERM access rights table.The view is CMN_SEC_ASSGND_OBJ_PERM_V0 (Holding Millions of Records)is called every 15 seconds in the application,when the records are less naturally the operation will be fast.           Regards,  J.sundar


  • 4.  Re: Removing Project Resources - Security Question

    Posted Jul 06, 2009 06:34 AM
    Thank you both!   These replies are very helpful.