In an Environment with many users, you normally would want to give certain roles access to sections instead of indivitual users. With a lot of users it is quite a pain using the module since you have to assign every user to every section manually.

Individual users could still be assignable and might overrule their role settings if set to yes.

CommentFileSizeAuthor
#5 Picture 1.png40.87 KBagentrickard

Comments

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

I would welcome a patch for this. Domain Access does something similar, so you can look there for inspiration.

The module is designed for a specific use-case, and I do not intend to work on this feature.

eigentor’s picture

eigentor commented

Ah o.k. Well I am not a coder so there won't be much coming from me.
I am seeing this module as a solid start on this functionality http://groups.drupal.org/node/16134 which is a function principle many "classical" CMSes work (Typolight, Typo3). If more people want to make Drupal work that way somone might jump in and build upon this module.
Good to know that it is not designed as a cure-all but rather focused at solving a specific use case.

An alternative to Organic Groups if one wants to build sections for editing access as it is. Bending O.G. to do this feels a bit bending it too much. Still it also works.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

OG does work, but this module is designed to allow the menu system to be the primary organizational metaphor of your site.

I may have a chance to get to this feature, just not immediately. It isn't terribly hard.

That g.d.o. post inspired this module, actually (http://groups.drupal.org/node/16134#comment-55308). It is delberately not a node access module due to overhead concerns and the complexity of the menu system.

pdcarto’s picture

pdcarto commented

I don't see how this feature request makes sense. Roles are intended for site-wide permissions. To define one role for each section of the site would quickly produce a permissions UI nightmare. Also, some sufficiently privileged user would still have to assign the privileges to individual users one way or another - either by editing their roles, or editing their sections (both on the user/%/edit page).

The only use-case that makes any sense might be when you already have a large number of users in a particular role that you want to dump into a MNE section. In that case, I'd argue that a separate utility function to assign sections to users in a particular role would make more sense than forging a live connection between roles and sections (for reason #1).

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
StatusFileSize
new Picture 1.png40.87 KB

I think you misunderstand.

Here's the DA interface for this feature, which I don't think is unwieldy. You don't assign a role per section. You assign multiple sections to a role. These sections can be stored in the user table or loaded dynamically during hook_user('load').

We could also do this under user administration. Domain Access also does something similar by using hook_user_operations().

http://api.drupal.org/api/function/hook_user_operations/6

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Status: Active » Closed (won't fix)