Hi,
Why not create a way to set permissions for documents/projects based on groups? This is logical way to use groups.
Regards,
Evgueni
Hi,
What do you mean for groups ?
This notion does not exist in Project'Or RIA.
I mean Teams
Hi,
It is done this way, or almost :
- right access is based on profile (some kind of group)
- most rights are based on affectation to the project (access right = elements of own project)
- from team view, it is possible to affect all the team to a project.
So it is almost a management based on group.
What is missing :
- once affectation of team to a project is done, adding a member to the team does not affect him to the project
- same thing when removing resource from team, afectation to project is not removed
- resource can be linked to onlyone team... so only one group.
What will come in V2.9 :
- Each user should have a different role on each project.
Any suggestion of improvement on this bases is welcome
- Each user should have a different role on each project.= this should override the profile settings!!!
this should override the profile settings!!!
Not override, but complete.
The target is to be able to define a user as "team member" (defaut profile), so that he has restricted rights on the project he is affected to, but "Project Leader" on one project, where he will have advanced right (for instance possibility to run ppanning for the project)