have it an an extension. not in core. that way, admins with the know how can turn it on and use the permissions. there will always be documentation, but if I installed it for a client, they 'played' around with it, I would have a phone call withing two days, requesting I unlock it for them.
just a suggestion.
not quite sure how you would pull this off with at least a few hooks to the core, juggling permissions like that would seem a bit insane plus it would no doubt require some role settings. Unless of course mark goes through with creating that table solely intended for extension settings and such.
Comments
i think i got lost in my own thread.
did you see denieds torrent of posts... that fool could use some punctuation