Confusing Enterprise Billing Policies

[JonathanCSmith]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot in GitHub

Body

We have enacted a universal user budget. This is working. Ish. In the short term we will make do. However, I also have independent credit funding for certain groups of users that I need to allocate. Previously, I'd put this into a cost centre and assigned those users that had access to additional funding. Now, the universal user budget blocks said users from accessing their additional funding. I can't remove them from the universal budget for obvious reasons. Which means they cannot have access to their funding that they have secured for more copilot spend. You're literally shooting yourself in the foot here.

Also, tiered user group budgets as a whole is so necessary. Come on. Please. This is a nightmare for administration right now. I have to manually assign each user who needs to go above the universal budget.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[alive-xd]

We're seeing the same thing.

The universal budget effectively becomes a hard cap, which makes separate funding allocations pointless. We have users who have additional approved spend available through their own cost centres, but once they hit the universal limit they're blocked anyway.

That leaves us with a choice between removing the universal protection entirely or manually managing exceptions user by user. Neither is practical.

The current model seems to assume every user draws from a single budget pool. That's not how a lot of enterprises operate. Different teams, projects and departments often have their own funding and approval processes.

At the very least, budgets need some form of hierarchy or precedence so that additional approved funding can actually be used instead of being blocked by the global limit.