"Only View Own Issues" override
Gemini 3.5.4 (Build 2435):
Just trying to figure out if the requirement I've been presented with is feasible. We want a project where:
- Specific individuals are granted project group permissions and are able to see issues raised by everyone
- All other employees should have basic permissions (create issues and comments) but can only see issues they raised themselves
I guess the difficulty is that there isn't a group that this restriction should apply to across the board, but it needs to apply to those not specified elsewhere. Is there any way to implement this?
Thanks,
Nigel
nharris
· 1 |
|
Friday, November 20, 2009, 12:26:38 PM |
0
|
Not sure I understand, but why not create a global group for these users and give this group the view own permission only? |
||||
|
0
|
Sure, I could do that, but every time someone joined the company the administrators would have to remember to add them to that group. Since their permissions to the relevent projects are through default security schemes (everyone has access to a project for Gemini management requests/issues and to a project for general technical support), it would be greatly preferable if they could be restricted to only viewing their own issues if they aren't specifically granted greater privileges. |
||||
|
0
|
In that case a project group will work. Assign the "view own.." to that project group and add the users to it for the "view own" projects only. |
||||
|
0
|
Well, yes, it would solve the issue of users needing greater permissions for other projects but it will still require us to add maybe 400 users through a project group to each of these two projects - not a very maintainable solution. |
||||
|
0
|
This is not possible as there is no way to know to which project to apply it. |
||||
|
0
|
Maybe I'm not explaining myself very well, but as I said in my last posting, the "View own..." restriction would be applied to a global group that is used to provide the default permissions to a specific project. I don't understand your comment that there is no way to know to which project to apply it.
|
||||
|
0
|
See if this helps: |
||||
|
0
|
No, I've created a separate security scheme for the internal support project so that I can provide default permissions to that project to anyone with a Gemini user account. That can then be overridden by granting permissions to the same project through a project group. All well and good so far. |
||||
|
0
|
Can you please send an email to support at countersoft dot com? We will arrange a GoTo meeting session to see if we can sort this. |
||||
|