With current HEAD, I find the configuration pages around the "People" area to be very confusing.

There's a top-level "People" page admin/people, which has a tab for "Permissions". Problems:
- It is not obvious to a new user (or a previous D6 user, or to me in particular), that you would want to click on People in the toolbar to get to the Permissions page. This is new -- it was changed in #699842: Move permissions to a tab at admin/people/permissions.
- The tooltip when you hover over People in the top nav is just "Manage user accounts" (I think this comes from the main People menu item that generates the admin/people path). It should say "and permissions" at least.

Then there's also a People section in config admin/config/people. This contains Account settings (admin/config/people/accounts), and IP address blocking (admin/config/people/ip-blocking). Problems:
- These should be grouped with the other people stuff, in my opinion. At a minimum, admin/config/people/account is MUCH more related to admin/people than is admin/people/permissions. IMO.
- I also think it's extremely confusing that there are two people sections. All the people stuff should be together, or the Config people section should be renamed to something else.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

jhodgdon’s picture

Issue tags: +#d7ux, +D7UX usability

tagging (hope I have the right tags)

Bojhan’s picture

Well there was bound to be a new issue, when we did this move so late in the cycle.

- We are guessing here, you are saying its not obvious to a new user, you or a D6 user that permissions is under people - we think it it will be more obvious then under configuration.
- We can rename the description.

- Actually this is all about use, the conceptual map you make, is very much object related. In terms of use, you rarely optimize account settings or IP blocking, for them to be in People - would make them far more important than they actually are.
- Yes and No, it is somewhat confusing to have two people sections. But its just as confusing two use two diffrent names for the same category.

catch’s picture

Yeah I find this really confusing as well, and regularly navigate to the wrong section. For renaming, we could do admin/config/users ;)

jhodgdon’s picture

Well, I would defer to any usability testing...

- The description change on the top-level People (admin/people) definitely needs to be done to include permissions (if that stays there), and that's a one-line patch.
- I see your point about having both sections being called People, and that Config/People is for configuration settings related to People.
- But if the criterion for what is in People and what is in Config/People is how often you would use them, then Permissions should definitely be in Config/People too. How often are you really going to need to configure permissions? Hopefully not often, and to me they're definitely a configuration item. So would setting up roles be (it's a local task under permissions, anyway, which actually makes sense).

Bojhan’s picture

Well, you might not use it much - but I am pretty sure a lot of users see it as a common place to be. What we saw in testing, is that many issues where refered to as permission problems (these where beginning Drupal 6 users) and when setting up a site its still a pretty common place to be.

If you want to make a patch for the description that is great.

jhodgdon’s picture

It looks like a couple of descriptions need to change, because the Configuration/People section still says "Configure user accounts, roles and permissions.".

We should probably just open up that other issue again where the permissions page was moved into Admin/People as a tab and make the fix there, and close this issue as a "wont' fix".

I'll do that.

jhodgdon’s picture

Status: Active » Closed (works as designed)
Noyz’s picture

Status: Closed (works as designed) » Active

Reopening this issue for two reasons...

1. There's seems to be significant confusion around finding permissions. I do think so long as there's a 'people' primary toolbar menu, grouping 'permissions' with 'people' is a sound idea. The problem is many people, both new and existing, can't find 'permissions.' I think in their mind, 'permissions' is a preference-like setting, and therefor try 'configure' first. As such, we should cross-link from config.

2. For those that have TAC installed, it's awfully strange that /config/people provides a link to granular-level access control, yet not site-wide permissions.

YesCT’s picture

Version: 7.x-dev » 8.x-dev
Issue tags: +Usability

This sounded link the same issue identified in Budapest Usability Testing Results, under Task 2
http://groups.drupal.org/node/271918

I’d love a cross-link from people to account settings, I only this because I’ve been working with Drupal for years"; "It is disturbing that 'people' settings are called 'account' settings and accounts are 'users'

If it's not the same, a search for a different already existing issue should be done, or a new issue should be opened.

YesCT’s picture

Issue tags: +budapest2012

tagging

YesCT’s picture

klonos’s picture

...we now have a dedicated section for related issues as metadata ;)

malcomio’s picture

Status: Active » Needs review
FileSize
1.5 KB

Given that the only child of 'Configuration/People' that is provided by core is 'Account Settings', how about we just remove it, and promote 'Account Settings' up a level?

Here's a patch that does that.

The tricky bit is what to do about any contrib modules that might use the 'user.admin_index' route to hang their menu links off...

malcomio’s picture

Version: 8.0.x-dev » 8.1.x-dev

Status: Needs review » Needs work

The last submitted patch, 13: people_section_s_are-715972-13.patch, failed testing.

malcomio’s picture

As well as the failed tests, looks like the ban module also uses a path starting with admin/config/people

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

pameeela’s picture

Status: Needs work » Postponed (maintainer needs more info)
Issue tags: +Bug Smash Initiative

This is a tough one! I do agree it's confusing to have both People links, but it's been this way for so long now, that it might be more confusing to change it?

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

quietone’s picture

Status: Postponed (maintainer needs more info) » Closed (duplicate)
Related issues: +#2695771: Re-organise user/account items under admin/

Now I find a later issue that has a comment suggesting this is a duplicate of that one, #2695771-11: Re-organise user/account items under admin/. And I agree that later issue has more discussion of possible solutions.

Therefor closing this as a duplicate and moving credit.

Also, I changed #1409940: Why does 'People' appear twice in the management menu? to be a duplicate of #2695771: Re-organise user/account items under admin/ instead of this issue.