How to Assign Users per Project
Hi,
We would like to assign Users to various Projects.
The only one way we could find was from the Project Administration -> Project Group. This implies that we have to define Project Groups in the "Gemini Administration" section and set security schemas for each of them. After that we can see the Project Group items in the "Project Administration" section.
Is this the right way? It must be another way of allocating Users per Project since that feature was present in the previous version.
Thanks
Octavian
· 1 |
|
Wednesday, November 19, 2008, 8:27:59 PM |
0
|
You can do this by adding the global / project group / user to the assignable to issues permission for the project's scheme. |
||||
|
0
|
I don't think this solves the problem. We have many projects and many programers, business analysts, etc. Some are working on a single project and some are working on several. I want to separate them and have them see only their projects and isssues. The Global Groups allows you to indicate which one plays which role/roles. For example User Pascal is a "Developer" for Project A and he is "Project Adminsitrator" for Project B, therefore I have to put him in both Groups. However I cannot specify for which one he is Developer and for which one he is Project Admin. The fact he is "assignable to issues" does not solve my problem, that relates to the Issue administration itself. Or maybe I am missing something here ... Maybe if you take me step by step it would become clearer for me. I also believe there are a couple of bugs in the Security/Roles/Schemes section. Accounts I did create and set groups/roles/rights for them show as haveing no project allocated, even if I can see them there.
|
||||
|
0
|
I think this is how it works, correct me if I am wrong it is a bit confusing: Admin Section Global Groups can be used to control people that are in many projects. For example you may have a test unit testing many projects at an organization so you might want to create a global group for that. Users can be added to these global groups. Project Groups can be defined in the administration section. This is so you can keep the project groups names the same accross all projects (developers, anaysits, business users, managers, etc....). You can only define a name and description here, you cannot add users. Security Schemes define the access that a global group, project group name or global user has. You pick the scheme roles you want and then select who it applies to. Setting it for a project group will mean that all the users defined in that project under the project administration for that group will have access. Project Admin Section in each project Security Scheme - here you can assign one security scheme. Project Groups - here you can put users 1 by 1 (no batch add as in other screens) into the group. --------------------------------------- In your example you would have the gemini administrator create 2 project groups on called "Developer" and one called "Project Administrator". They would then setup a scheme for what these two project roles can do. Then under each project under the project administration you would have to include the scheme and add Pascal to the appropreate group (Proj. A = Developer, Proj. B = Project Administrator").
|
||||
|
0
|
Thanks. |
||||
|
0
|
Coul dyou confirm that if I want to manage access by Project, on each project I have to replace my Global Security Scheme with a project-specific Security scheme? I'm referring to your comment above - that only one security scheme can be assigned. |
||||
|
0
|
This is how I did for mine:
|
||||
|