7.0 People

updated 11 June 09
People

People Index Page
Larger image here

People Events

People/Events Index page
Larger image here

Description: Any large lists of people are managed in this section, including site administrators, site members (authenticated users), event attendees and group memembers.

Current thinking/roadmap:

  • Shows lists of people divided into tabs like Admin (site admins), Members (authenticated users), Events (event attendees), Groups (group members) etc.
  • Management tools for each type of ‘person’ is shown in their corresponding tab. For example ‘roles’ would be shown with Admins, ‘Broadcast’ tools would be shown with Event Attendees etc.
  • Uses same visual language as Find Content table

Note that roles, permissions and user settings will be migrated into the Modules & Configuration section of the site so that this section is focussed on ‘everyday’ usage and Modules & Configuration will hold the less frequently accessed functionality.

Aggregated Feed (Pipe) of Related Discussions

Please feel free to add your thoughts as comments below or if you’d rather publish them elsewhere you can have them the pipe by using this tag #d7ux_7_0

go back to Project Framework to view all project components

14 thoughts on “7.0 People”

  1. If nothing else, this video points out some issues with the current permissions setup and suggests some immediate solutions. Bigger and better options should be available, but perhaps its a place to start?

    http://gotdrupal.com/videos/manage-drupal-permissions-more-easily

    Organizing permissions by modules creates some problems. First, the site builder knows the modules and which do what but the content creator and others do not and so that breaks at least principle #3. Also, the modules have permissions that cross over sometimes. When you have multiple modules that restrict permissions to content, then you have multiple modules to go find content permissions under in order to properly set things up. Missing one is trivial and time consuming. (Plus it makes you look stupid to clients.) I’m not sure how to do better in this, but some change in organization seems like an obvious need. Finally, when you get 5 or more roles, the main permissions page becomes a true challenge. It’s like dealing with a big spreadsheet with little squares. Accidentally hitting the wrong permission and allowing something improperly is easy. The video I shared has show a few modules that already show a way of helping with this last one.

    The level of permissions is a clear strength technologically, but I’m looking forward to a better management interface.

  2. Agree with Josiah regarding how confusing things get when a couple of modules and a couple of roles have been added. A functional organization might work better than a module-based one, or perhaps there could be two ways to view the information (so when a new module is enabled that offers new functionality one could get right to it). I’m fond of the rights-granting process that goes like this:
    1) select which user/role you want to work with
    2) select from a list of functionality or content types to grant permissions, or add functions on left to bucket on right to grant permissions.

    which is usually combined with this:

    1) select which functionality/object you want to work with
    2) select users/groups w/o access to which you want to grant access.

    Using a tree control of grouped functionality and grouped users/groups with checkboxes next to them makes much more sense visually (one could have icons for different categories of functionality) and is familiar (eg granting users/groups rights to content in Windows). Either (tree controls or buckets) would work better than millions of tiny checkboxes in rows for these kinds of operations.

  3. Hearing Carolyn describe it, I realized it is similar to the problem that was “fixed” in D6 where going to /admin resulted in a list sorted by module. It can still be seen at /admin/by-module.

  4. The existing permissions interface isn’t overly pretty, but it’s also the one thing in core which hasn’t caused any issues in usability testing.

    When you add a lot of modules and roles then yes it does get complicated – but then you’re building/administering a complex site by that point anyway.

    Grouping permissions by task, being able to separate permissions by module, stuff like that are all potentially useful enhancements – but this isn’t a critical issue and there are already patches around for it. Similarly basic user management didn’t cause many issues for usability testees either.

    One thing with users vs. people – we currently don’t have a great way to deal with site visitors (i.e. users without an account) – in fact they’re called anonymous users. There’s some moves to get the concept of ‘visitors’ at a higher level (i.e. this comment and my previous one would both be associated to the ‘catch’ visitor, who might decide to register later and could have their previous comments associated with their new account, stuff like that) – so an overall ‘people’ then division between visitors and users might be useful for that. Replacing users altogether with people I’m less sure about – then what are visitors? un-people?

  5. People to my site, who are members, often ask via contact some common questions. Which has no answer it seems. Or very complex set up of modules or hacking of core.
    Many of these vistors have WP or google background, meaning they have accounts on those sites also.
    Example
    How do I hide my online status?
    How do I find the comments I made?
    How do I find comments I got?
    How do I have a calendar block display of my blog posts? ( Multiuser blogging is enabled)
    How do I turn off my RSS?
    How do I import my friends from my gmail here?

    The last one is so very common.

    1. hi Garfield, this is a very late response to your comment, sorry about that. These are some very interesting questions tho’.

      It’s not clear to me what ‘kind’ of people these are? Are they asking you questions about building a Drupal site? or are they users on your site wanting to access and/or switch off some functionality that may or may not exist?

      (if the latter, it strikes me that a lot of these things should perhaps exist on a Profile page, no?)

  6. In the People landing page, we’re looking at a list of people, but the tab says ‘Content’. Is this a typo, or is this a tab to see the people associated with content? If I don’t have any Events, will the tab still show?

Comments are closed.