**Needed Research / Open questions (and what we found out so far):**
- We need examples with explanations: When did somebody change the page protection of a page in which way why?
- How does the current interface look like?
- What are the existing user roles and their page protection rights? Is the protection scale sorted hierarchically?
- //It seems that the code base does not require a hierarchical sorting. The policy is: Everything is allowed to everyone, but you can take away rights from groups, e.g. doing certain things on a web page//
- //Which user roles and page protection types exist differs from community to community. There is the default of semi-protection/ full-protection throughout the wiki, but e.g. de-wiki has another right for "sighters" in between the two. It looks like usually the number of protection rights (including unprotected) is between 3 and 6//
- Do we undermine the wiki style of working, if we allow preemptive page protection?
- //From discussion with one editor: Page protection should never become a default. The wiki way of working is allowing everyone to edit, and react if vandalism occurs. If the page protection prevents one good edit, it has already been a bad idea//
- Also: {T142369}
- //From discussion with editor: You may want to go back to the previous state of protection, if it had been set on "indefinitely"//
**Solution ideas:**
//Allow multiple protections at once//
{F4345151}
//Allow mulitple protections after each other//
Similar to the first one, but there may always be just one protection level for a page at a time. This would have the advantage that the change in the code base would probably not be as massive as for the first idea.
//Go back to the indefinite state that was in place before//
**Possible tasks:**
- Find best possible solution, based on research results
- Ask the community if the suggested solution is better than a revision history which saves the state before and then sets it back
- Do an RFC on how this should look like and, if applicable, how the database should be changed
**Background**:
Wish #7 of the 2015 German-speaking community survey was {T142209}