Quote:
Originally Posted by 47shadesofgay
[You must be logged in to view images. Log in or Register.]
I agree with seperation of powers with regards to who has DB access/code access whatever, but when it comes to log access, unless they can be abused in some tangible way I think individuals who handle CSR should be able to be trusted with any and all logs.. otherwise why are they handling CSR in the first place? =p
That was the crux of my original question, because if there were logs in the database itself I could then understand wanting to restrict access to them, because you probably don't want GMs poking around too much in the db.
Anyhoo, sounds much better than it was a year ago. [You must be logged in to view images. Log in or Register.] |
Yeah, well don't let my response confuse you too much. I'm not suggesting that there are members of staff that need to be watched (certainly not, in fact). But when you take a role on staff here you should expect to be watched and scrutinized by the maintainers, regardless of your access level or role. It's the way it should be, and is best for the community.