membermanagement.ini
The shipped settings of settings/membermanagement.ini: 4 blocks, 13 settings.
Member management: which user groups may manage the user accounts of which other groups, with which policies, and
which groups nobody manages through such a rule. Read by the setup wizard's role step and the kickstarter (a new
installation), by bin/php/addmembermanagement.php --apply (an installation that exists; without --apply it only
shows what it would change), and by the access check that keeps the protected groups' accounts out of reach
(doc/eng-us/bc/6.0/member-management.md).The defaults give the Editors group the role "Member management": create, edit (name, e-mail, password), enable and
disable, move and remove the accounts below Members. The accounts of Administrator users and Editors stay with the
administrators, and nobody gets roles, sections or setup from it.Groups are named in one of these forms, so the same file fits every installation:
remote:<remote id> the group object's or its main node's remote id (the stock groups keep theirs everywhere)
node:<node id> the group's node
name:<name> the top-level user group of that name below the user root
Add or change rules in settings/override/membermanagement.ini.append.php or in an extension's settings.
| Block | Settings |
|---|---|
| MemberManagementSettings | 3 |
| MemberGuardSettings | 4 |
| MemberRule_editors_manage_members | 5 |
| MemberPolicySet_member_management | 1 |
Generated by ./console exp:help:examples from settings/membermanagement.ini. Do not edit this page: change the source and generate again (how). Free documentation: GFDL 1.3 or later.