The things marked with ? are things i am not sure about

I just have to propose a new table for user managagment issues.

the new table should be like :
wikka_usergroups
id smallint not null auto_increment
groupname varchar(35) not null default ''
can_read_pages enum('Y', 'N') not null default 'Y';
can_edit_pages enum('Y', 'N') not null default 'Y';
can_create_pages enum('Y', 'N') not null default 'Y';
can_delete_pages enum('Y', 'N') not null default 'Y';

this desciption may need some more things to it thought ... it depends on the abilities of the core at that time.

- notes
in wikka_users:
we need another two fields :
usergroup varchar(35) not null default 'Registered'; -- for checking privileges.
lastvisit datetime not null default now(); -- for the possibility of a user cleaner

I am not sure if it is good to store the acls in the group table. This leeds to to places where you store the access to a page. 1)for single users direct to the page 2)for groups in the group table. It could be a solution if on the acl-page for a page the groups are shown, too?

Well I suppose the users could be assigned a default usergroup when registering...

Then the wikka_pages table may have another two fields :

edit_usergroup varchar(35) not null default 'Registered';
comment_usergroup varchar(35) not null default 'Registered';

if we have this example wikka_usergroups:

0, Admins, 'Y', 'Y', 'Y', 'Y';
1, Moderators, 'Y', 'Y', 'Y', 'N';
2, Registered, 'N', 'Y', 'Y','N';

Examle :
a Wiki page has its comment_usergroup set to 'Moderators' ( id=1 )...
the user currently viewing the page, belongs to the 'Registered' usergroup ( id=2 )

the user will not be able to put up a comment in the specific page because his 'id' is bigger than the allowed 'id' for the page ...

Basically this kind of managing user access is introducing a priority system...