While it's listed in #207, I suppose it should have its own issue since it will be a substantial amount of code to be written.

A permissions system should be able to grants rights such as:

• who is able to take control of warp at will (warp rights group)
• who can dock onto a station (interaction rights group)
• who can launch from the VAB/SPH (mission rights group)
• who can chat and private message (chat rights group)
• who can perform specific commands or administrative functions (chat_admin rights group)

A stage 1 implementation will grant all rights to ops and a limited (hardcoded) list of rights for users. A stage 2 implementation will allow specific user groups to be defined that are granted a list of rights groups. A stage 3 implementation will support whitelisting and blacklisting for specific rights. A stage 4 implementation will support vessel-level permissions (visibility, docking, controls, collision, etc).

Not really sold on this one...

'warp' only makes sense for MCW_FORCE
'interaction'/'mission'/'chat' feel like a diversion away from what I think "stock multiplayer" should be :-/
'chat_admin' is already addressed in the admin thing on the server - and all it does is give you access to the server console.

I see DMP as more of a framework, in that features should be implemented to support plugins as well. warp rights also makes sense for MCW_VOTE (since, say, a spectator group should not be able to take part in voting for warp).