Feature Request: Organization Default Model & Per-User Model Controls for GitHub Copilot

[nstrating]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Other

Body

Problem

Before requesting this feature, I want to confirm if the following is possible on organization level with Github Copilot:

• Is it possible to set an organization-wide default model (e.g., Auto)?
• Is there a way to reset the model to a default on each new session?
• Can models be enabled/disabled per user or group, instead of globally?

If these capabilities already exist, pointers to documentation would be appreciated.
Currently, users can select a model and it persists across sessions, causing many users to stick to a specific model (e.g., Opus).

Feature Request

Add administrative controls to:

• Set an organization-level default model (e.g., Auto)
• Enforce an optional policy to reset the model to default on new sessions
• Allow per-user or per-group model enable/disable, instead of only global control

Use Case

• Encourage use of Auto model selection
• Prevent long-term use of expensive models (e.g., Opus)
• Apply different model access policies per team or role
• Maintain consistent starting configuration across all users

Proposed Behavior

1. Admin sets default model → Auto
2. User opens Copilot → Auto is selected
3. User switches model during session
4. On restart/new session → model resets to Auto

Additionally:
Admin can restrict certain models for specific users/groups

[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. ⭐

[pvojar]

I do agree with this feature request.

As of today enterprises may create AI model policy that can be only scoped to the organization level. Anyhow would be nice to see a feature that may allow Enterprise Admins to assign a models to the specific user, enterprise teams and organization teams as well.

This will streamline the enterprises to decide which models the group of users may use. For example group of senior developers may receive more robust models such as Opus 4.7, on the other side new comers or junior developers should star with less complex models to avoid the Enterprise AI credits exhaustion, to gain the time to get familiar with the AI in general.