Page MenuHomePhabricator

Allow bureaucrats on test2wiki to add more groups
Closed, DeclinedPublic

Description

Feature summary (what you would like to be able to do and where):

  • Allow bureaucrats to add and remove all* (*except checkuser) groups including steward*. (*steward would split into 'local steward' which can modify all groups but checkuser and the original steward which can add and remove checkuser, but can not be assigned or remove by a bureaucrat.)

Use case(s) (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution):

  • Being able to test additional rights without having to ask global stewards.

Benefits (why should this be implemented?):

  • See above.

Event Timeline

CU is not the only group with access to private data. This should also mean that 2FA is compulsory for test2 crats. That's to begin with.

Local steward flag currently doesn't do much on wikis other than meta.

CU is not the only group with access to private data. This should also mean that 2FA is compulsory for test2 crats. That's to begin with.

Local steward flag currently doesn't do much on wikis other than meta.

@Base Which other groups? Do you mean oversighter? The reason I am singling out CU is because it is the only group with access to global private information.

Local steward flag currently doesn't do much on wikis other than meta.

I forgot to say that I would also like to add some of the meta steward right to the local steward group for testing purposes. (these would only apply locally)

Stang changed the subtype of this task from "Feature Request" to "Task".
Stang added a subscriber: Stang.

Allow non-stewards to manage CheckUser/Oversight permissions: Only stewards are allowed to manage those highly restricted groups; local wikis are not allowed to customize this.