Select to view content in your preferred language

Enable Credit Allocations by Default

336
4
05-13-2024 05:22 AM
Status: Open
PeterKnoop
MVP Regular Contributor

I would like to see credit allocations enabled by default for ArcGIS Organizations. I believe that is an important prerequisite to setting up organizations for success, and avoiding unexpected or unanticipated organization-wide issues stemming from accidental usage by a one or a few people at the wrong time.

Credit-based Software as a Service (SaaS) systems are a new concept for many organizations and users. Having credit allocations initially in place would help protect them while they are developing their understanding of how credits work, and how they pair with their organizations’s GIS workflows and needs.

I think it is also worth considering enabling credit allocations retroactively for existing organizations.

4 Comments
MichaelKohler

I'm not sure if this is what you're looking to do, but you can set credit allocations by default for new members.

Organization -> Settings -> New member defaults

MichaelKohler_0-1715711322431.png

 

PeterKnoop

@MichaelKohler that functionality is only available after you have enabled credit allocations for your ArcGIS Online organization (see Enable credit budgeting.) Currently credit allocation functionality is off by default for new ArcGIS Online organizations. This Idea is about having it on by by default.

JonathanMcD

I'm not sure about this one, should be just part of admin workflow / management.

 

It's a bit like asking for a TV or light to be set with default on.

PeterKnoop

@JonathanMcD it is perhaps like a TV or light. If we treat those items as consuming credits when they are on, then if a user forgets to turn them off, then they will run until they have exhausted all of your organization's credits. With Credit budgeting enabled, and credit allocations set, then the organization is protected from one or more users accidentally consuming all of the credits; the TV or light is automatically turned off once an allocated number of credits is consumed.

Perhaps another way to look at this is to ask for what organizational scenarios does it make sense to enable the organization to run out of credits? And, are such scenarios more common than those where you want to prevent an organization from running out of credits?