Allow an administrator to control each individual user’s access to functions that consume credits. There is a need to restrict users form consuming “Computation” credits. The current control by class of user: “User”, “Publisher” and “Administrator” is inadequate. In a matter of minutes a poorly trained publisher can burn through hundreds of dollars of credits through tile generation, geocoding or routing. This is diminishing the utility of AGOL because the easiest way to guard against excessive credit usage is to restrict the number of “Publishers”. We would like to have MORE publishers, but we can’t have them burning through all of our credits by using expensive computational services.