This is a related to another request I have made: 1017432.
Right now, XOOPS has no way of assigning permissions to
users directly. You can "fake" it by making a group
with the permission you're concerned with and assigning
only one user to that group. Essentially, you're
creating a group that acts as a permission container.
But that's a lot of fiddling around in the system to
accomplish something. Instead of one step, assigning a
permission to a user, you have to go through three
steps: make the group, assign the perm to the group,
assign the user to the group. That's a real drag.
Also, if you are forced to use groups as permission
containers in this way, it can be a really confusing
thing for some sites. Here's why: Suppose you have a
lot of groups in your system already, but your existing
groups are being used as content containers -- they are
groups that are used to control what content users can
see, ie: what modules they can access, and what content
in those modules they can view.
If your site is full of content groups, then your
admins are used to working with a list of groups that
means something in terms of the org chart for your
company/club/department/whatever. That's what groups
in your site are, they represent something about how
the real-life people in your organization deal with
each other in the real world, and through the groups
system, you're mapping those relationships onto your site.
So if you then use the groups system to create
permission containers, things get very confusing, since
all of a sudden there are special groups in the system
which have nothing to do with how your other groups
(and your real people) are organized.
The same is true in reverse. If you've made a whole
bunch of groups in your system to control the
permissions people have to edit and administer things,
and then you go and create groups that control access
to content, you have the same confusion.
Essentially, I think the XOOPS group system is being
stretched in two directions: it's both a content
control system, and a permission control system, and
for some sites, depending on how things are organized,
this can be a problem and confusing. It would be best
in those cases to have the option of giving system
admin permissions, and ideally module admin permissions
too, directly to users.
I don't think the ability to give admin perms to groups
should be removed (I think handling content and
permission control both by groups can be very elegant
for some sites). But I would really like to see the
ability to give admin perms directly to users. It's a
missing feature for a lot of business uses to which
XOOPS could be put.
I don't see a big need for access permissions to be
given to users, though if it were possible, I'm sure a
use for that flexibility would be found by someone.