XenForo treats logged out visitors ("Guests") and logged in but unconfirmed visitors ("Members") somewhat equal - they both get their permissions from usergroup Unregistered / Unconfirmed.
So when editing this usergroup there are many permissions like
While it may be "logical" that some permissions can't be applied to guests, in some cases this is not so obvious and may cause confusion.
My suggestion is to make it more obvious that some permissions can't be applied to guests.
This could be achived (relatively easily) by adding a new flag Can be applied to loggedin users only to permission definitions:
With such a flag in place the edit usergroup permission controls ffor usergroup Unregistered / Unconfirmed could be easily improved, making it very clear that some permissions can only be applied to loggedin members:
Ideally the entity should also have an appropriate check method so 3rd party developers can hook in via a code event listener.
This would allow 3rd party developers to "unflag" permissions as "Member only" in case their code changes behaviour.
So when editing this usergroup there are many permissions like
- Use push notifiations
- Upload an avatar
- Upload a profile banner
- ...
While it may be "logical" that some permissions can't be applied to guests, in some cases this is not so obvious and may cause confusion.
My suggestion is to make it more obvious that some permissions can't be applied to guests.
This could be achived (relatively easily) by adding a new flag Can be applied to loggedin users only to permission definitions:
With such a flag in place the edit usergroup permission controls ffor usergroup Unregistered / Unconfirmed could be easily improved, making it very clear that some permissions can only be applied to loggedin members:
Ideally the entity should also have an appropriate check method so 3rd party developers can hook in via a code event listener.
This would allow 3rd party developers to "unflag" permissions as "Member only" in case their code changes behaviour.
Upvote
5
