Configuration page: People & permissions

People stuff

• Roles
• Permissions
• Account setup
• …

(Account setup is my rename of the rather empty 'user settings', but don't let that distract you)

It's such a small list, you can't help but think it could be put on the People page itself…
We need to connect the People page with this group of settings on the Config page somehow (this is also slightly off topic)

The topic is:

- label for this People Management (ugh) category
- items that will certainly live there

Don't forget about profile fields to user profiles. I don't think that belongs coupled with people management. OTOH, configuring permissions is something you do on a minutely basis when setting up the site, and it might make sense for roles/permissions to be a lot closer to the people management screen.

That category should be created, and i think it should be something like this:

People Management
* People Listing
* Account Settings
* Profile Fields
* Roles
* Permissions

(note: bikeshedding over names etc. can be done later on.)

also: a category is very important, as in the current situation, the people link only shows in the management menu at the bottom of the page when Seven is set ad admin menu, and the expert profile has been used.

Ok, summary of IRC chat with Bojhan:

For the category label:

- Let's avoid 'People management', it's corporate speak at it's worst and will make catch quit Drupal. Can't have that.
- 'Management' is rather meaningless anyway. We're in the context of the admin of a content management system, it's all about managing stuff so duh.

People & permissions is what we came up with, for the following reasons:

- 'Permissions' is a key word. In this category, it'll probably be the page used most often.
- Bojhan mentioned that during the Baltimore usability tests, 'Permissions' was a care word indeed. "people think everything (that goes wrong) is about permissions."
- Bojhan checked what Basecamp does and lo! they're using 'People & Permissions'…
- 'People and permissions' implies a pretty broad scope on what could be underneath it (more so than say, 'People & roles', yet is still quite distinctive from the other categories.

I support the direction in #6. Since we call the top-level link "People" it's natural people will be looking for that keyword in the settings page as well, and I can also confirm that "permissions" is a critical keyword, based both on formal usability testing and also my general observations in teaching workshops, etc. There's a good reason we renamed "Access control" to "Permissions" in D6. :)

I like 'People and permissions' - it opens this section up to more properly deal with non-user-account-holding visitors, permissions incorporates roles (at least in Drupal), doesn't make me want to cry or punch walls like 'People management' does.

People & permissions
that is one Great Find, and in addition, it makes the other one (config & modules) look less weird.

Moved all mentioned user settings and profiles to "People and permissions". This is how it looks:

I've put this up as the first item on the right to list. Probably these left/right placements and weights will be debated after code freeze, but we need the paths to settle, so let's not argue over that. Also, I've put the order of items to be "Account settings", "Roles", "Permissions" first in a logical order that my mind maps. That is rather easy to fix afterwards.

IP adress blocking seems to fit in here as well but isn't part of it yet.

I went to commit this, but it looks like Dries already did. :)

Oops. But yes, let's move IP blocking here.

Hahhaa

Patch to move IP blocking.

Editing profile fields broken, e.g., admin/config/people/profile/edit/1
patch attached

Looks good. Unfortunate that we don't have tests for this :( We should come back to the ip blocking move after this fix is committed.

Committed both patches. Thanks!

Committed both patches. Thanks!

#19 didn't actually passed so rolled that back.

fixed ip-blocking patch

Changing arg numbers is something we happen to forget. Thanks for fixing that up. Looks good, passed UX already above, passed tests -> RTBC.

Committed. Thanks!