Yes my intent was to not really change category permissions much with this upcoming change, so these (this and Category permissions and the new permission groups - #5 by martin ) are more unintended side effects. I don’t intend to remove everyone yet as an option from category permissions…but over time I think it’s probably a good idea to do a fast follow up on this.
The problem is that I was thinking it would be even less clear what I should migrate everyone category permissions to, but maybe it can follow logic like you are suggesting? E.g. if I remove everyone, a migration would add these category permissions for a site:
- Site requires login →
everyonebecomeslogged_in_users - Site is public/doesn’t require login →
everyonebecomeslogged_in_usersANDanonymous_users, two separate category permissions
I think this suggestion makes the most sense, and is the clearest, so I will make that change when I can.