Who would benefit? |
Anyone wanting to control field value or access with the user role |
What impact would it make? |
More flexible approach then restricted fields |
How should it work? |
=USERROLE("Role1", "Role2") would return true if the current user has at least one of the listed roles |
Why is it needed? |
To replace the static restricted fields approach |
Combine with my READONLY() function to control access
I don't understand this idea. What should be the outcome of the function
USERROLE
? And why do you need it? If you want to restrict users for expression engine fields, I think inriver needs to implement support for that in the core, not apply it as a function.