The api documentation suggest the esri_access function of the user class is a means of enabling/disabling esri access. In v 1.4.1 this is not functioning, perhaps because user.esri_access is defined twice. The first sets an attribute of the user which returns user_type. This appears to take priority over the second which is a function to set the user_type, as noted in the documentation. In addition user.update includes user_type=None in the function but does not include that parameter in the arguments. Can you clarify the future functionality for user.esri_access? And with that, is there a reason the ability to set user_type is not included as a parameter in user.update? Thanks.