Admins need a way to control or limit access to use of the organization's credits by custom apps configured to use App login, or by WAB apps configured with Subscriber content access.
Currently there appears to be a few situations where there is no way for an administrator to limit how many service credits an anonymous user may be given access to. Custom apps can be developed to use App Logins (where a member's credit allocation has no effect on the number of credits that can be used by the app). Web AppBuilder apps can be configured to provide Subscriber content access - where premium content will consume credits (again where a member's credit allocation has no effect on the number of credits that can be used by the app)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.