Standard (Default) Permissions in Default Security Scheme
Ok. I completely wiped my install of Gemini because I have been fighting permission issues since the 3.X release. I did a clean install to 3.7 and try from scratch without dealing with upgrades etc.
It seems that everything is basically pre-configured for you except for the "Default Security Scheme" (Unless I missed a script or something).
So, if there was a script that created the Default Standard Permissions for each default global security group which is a part of the "Default Security Scheme" I think I may be able to use the system.
I just have no idea what permissions I should give to and Administrator versus a Developer. And quite frankly, why should I have to think about this. Maybe I would want to tweak it, but having the normal or standard permissions already there would give me a working system at the time of install instead of me beating my head against the wall to try to figure out what each permission does and whom I should grant each to. I realize that these permissions are pretty self explanitory... But again, why... Let me have a script that will set up a "Best Practices" install and at least get up and running. The I can tweak it if needed for my purposes, or for those that want completel flexability, don't run that script.
Just a suggestion that may help me and others. I just can't seem to get any Gemini going since the security changes in the 3.x product. I LOVED 2.X, it was simple. And I too wanted new features, so I understand that things had to change.
Right Now, I am a Global Admin of my Gemini install and I still cannot see the project I created.
There has to be someone that can explain this so I could get it. Or maybe I am really that stupid. If so, I need a new job ;)
Thanks for letting me vent. And as a caveat.. Saar is planning to do a remote help session and try to get me squared away. But I just thought this script idea may help others also.
tdemeza
· 1 |
|
Tuesday, June 8, 2010, 9:58:59 PM |