"Access User Profiles" permission label is misleading

Thanks to git log -S there is a pointer to the original issue, which is #658148: The "access user profiles" permission is poorly named → . Have the conditions that led to the current naming changed? It has been fifteen years.

Sandeep Sanwale → made their first commit to this issue’s fork.

changed the label of access user profiles from View user information to access user profiles in user.permissions.yml .

Has test failures.

The issue summary must be edited to include why this reversal of a prior decision is appropriate.

I have updated the Issue summary with a response to the related issue as well as an alternative proposed resolution of including a description for this permission.

I have added the description for the Access User Profiles permission . please review this .

Now the solution goes against the issue summary. Proposed solution should match

Binoli Lalani → made their first commit to this issue’s fork.

Hello,

I updated the permission description as per Proposed resolution and fixed unit testcase errors. Please review latest commit.

Thank you

Left a comment but if read out loud doesn't sound correct. "With this permission can do this. And without this permission you can't do this" is kinda how I'm reading this. Left a comment

Still appears to have test failures.

It would be better to call this "Access Any User Profile" instead of "Access User Profiles", so it is clear this does not mean that users can access their own profile.

Updated the title/name of the permission. Also updated the IS.

Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to our policies.