Currently the Sandbox is protected and thereby prevents users with less that 10 reputation from posting there. This is theoretically a problem because new users are the ones that need the Sandbox the most. Therefore I want to ask if someone could raise the threshold (answers from new users) so that the Sandbox won't automatically be protected.
The new Sandbox has been protected 3 times automatically since it was created. The first two times Monica unprotected it and after posting this Separatrix unprotected it the third time.
As was mentioned by Laurel in a comment to this Meta discussion about mentioning the Sandbox to first time question askers our sister site PPCG had a similar problem after lowering the limit for posting on Meta to 1 reputation.
In the linked post on PPCG the Community Manager Shog9 said that he "set the relevant thresholds (answers from new users) to 10,000".
Is there a way to do this with our Sandbox, too, so that it doesn't get protected all the time and has to be unprotected by someone manually?
It would be very frustrating to give new users with (currently) 5 reputation the hint that they can use the Sandbox only for them to discover that they are not allowed to post there. This might not be a problem for a lot of people, but in theory it's possible. And manually unprotecting the Sandbox is unnecessary work for the people that have this privilege.
Since the first discussion on this topic the Sandbox has automatically been protected 6 more times. One of these automatic protections was triggered 8 minutes after Monica Cellio unprotected the question, which lead to a second unprotection from Monica 3 more minutes later. A few days later the Sandbox has automatically been protected again and a new user replied to this post to ask if someone could unprotect it again, which HDE did.
Currently we have 9 auto-protections in roughly 1 1/2 month. In 7 of those cases a mod unprotected the question (Monica and HDE). 2 times a non-mod user with the corresponding privilege (Separatrix) unprotected the question.
Update two months later: The problem persists and we are currently at 18 auto-protections.