Users - Groups - Privileges Implementation

[Gpower2]

We must decide upon a database schema for managing users/groups/privileges.

The controller objects must implement methods for managing this data.

[LelouchVII]

We should keep simple privilaged groups this time. From what I hear when you removed Left from the team you had so many privilaged groups to remove him from it made a mess. My proposition:

Free User--> Can only download and view
Registered User-->Can post
Member Under Training-->Can view encyclopedia
Member--> Can view secret section
Admin--> Can view dev section, has access to ftp/server
Super Admin-->Has root access. Controls everything

[Gpower2]

This is another matter all together.
You are talking more about user classes or rather user roles.
I am talking about groups like project groups etc., and I am really emphasizing on the back end design and implementation rather than the data itself.

[LelouchVII]

Ah ok then. Ill think of something and update later