i agree, it is. there are a lot of options even when trying to keep it simple.
that would be an implementation of group based access control wouldn't it?
i am talking about an administration section i guess but its more like... access control. not really who can access the administration section of the site because it won't really be like a separate entity. but there will be editors who are allowed to edit important or major sections of the site. like artist/album/song descriptions, reviews, front page blogs. but then there will also moderators of the forums, people responsible for maintenance, users, dada dada.
right now im designing the data model for this website trying to figure out what the advantages and disadvantages of different systems would be. and trying to put names to concepts that i come up with
someone may be an editor but also may be the moderator of forums, now they could be members of both groups, or they could be granted permissions to perform the specified actions, or they could be granted permissions to perform the actions associated with speficic groups.
but then what if there is a special member who has permissions for some things or other things? then you'd need rbac. it's a complicated subject for sure. like maybe they can edit an article but not delete it then delete forum posts but not threads and no permissions for edits. whats an efficient but scalable way to implement these sorts of permissions?
we could store two lists? one based on actions and one based on groups?
and even when you decide on an system the data model could be speficied in many different ways.
i'll write more when i sober up but right now i dont think its a good idea. love to talk about it though
