--- title: Copilot model access update for GitHub Team plans description: GitHub has changed how model access is determined for Copilot users holding seats in more than one organization. Previously, a user could access a model if any... canonical: https://daily.dev/posts/copilot-model-access-update-for-github-team-plans-sko2tev7d twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Copilot model access update for GitHub Team plans | daily.dev og:description: GitHub has changed how model access is determined for Copilot users holding seats in more than one organization. Previously, a user could access a model if any... og:url: https://daily.dev/posts/copilot-model-access-update-for-github-team-plans-sko2tev7d og:image: https://api.daily.dev/og/posts/sko2tEV7D.png og:image:alt: Copilot model access update for GitHub Team plans og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Copilot model access update for GitHub Team plans **[GitHub Changelog](https://daily.dev/sources/github_updates)** · 1 min read · 1 upvotes · 0 comments ## Summary GitHub has changed how model access is determined for Copilot users holding seats in more than one organization. Previously, a user could access a model if any of their organizations enabled it; now, model access is decided solely by the organization that pays for the user's usage, shown under 'Usage billed to' on the Copilot features page. Users whose Copilot access comes entirely through a single enterprise or its organizations are unaffected. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How does GitHub Copilot decide which AI models I can use if I have seats in multiple organizations? Model access is now determined only by the organization that pays for your usage, found under 'Usage billed to' on the Copilot features page. Previously, you could use a model if any of your organizations had enabled it, but that policy has changed so billing and governance stay in sync across multi-org Copilot users. _Track changes like this Copilot policy update to keep multi-org AI coding access configured correctly on daily.dev._ ### Will this GitHub Copilot billing organization change affect users who only belong to one enterprise? No, if Copilot access comes entirely through a single enterprise or its organizations, model access remains unaffected by this update. The change only applies to users holding Copilot seats across more than one organization, where the billing organization now solely governs which models are accessible. _Developers managing enterprise Copilot rollouts follow policy changes like this one on daily.dev._ ## Similar posts on daily.dev - [Target Copilot models to organizations with model rules](https://daily.dev/posts/target-copilot-models-to-organizations-with-model-rules-ztdipqtxt) · GitHub Changelog · 2 upvotes · 1 comments - [Track organization Copilot usage](https://daily.dev/posts/track-organization-copilot-usage-k9rvujspa) · GitHub Changelog · 0 upvotes · 0 comments - [Organization-level Copilot usage metrics dashboard available in public preview](https://daily.dev/posts/organization-level-copilot-usage-metrics-dashboard-available-in-public-preview-yu839xovo) · GitHub Changelog · 0 upvotes · 0 comments --- Tags: [#github](https://daily.dev/tags/github) [View this post on daily.dev](https://daily.dev/posts/copilot-model-access-update-for-github-team-plans-sko2tev7d) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Copilot model access update for GitHub Team plans","url":"https://daily.dev/posts/copilot-model-access-update-for-github-team-plans-sko2tev7d","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/copilot-model-access-update-for-github-team-plans-sko2tev7d"},"datePublished":"2026-09-01T14:31:27.386Z","dateModified":"2026-09-01T14:31:47.132Z","description":"GitHub has changed how model access is determined for Copilot users holding seats in more than one organization. Previously, a user could access a model if any...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/130b3bca59caa9a1837c28072eef0242?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/130b3bca59caa9a1837c28072eef0242?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"GitHub Changelog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"GitHub Changelog","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/15004b7835da4d89b02b115871f0f6dc","url":"https://daily.dev/sources/github_updates"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/copilot-model-access-update-for-github-team-plans-sko2tev7d","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"github","timeRequired":"PT1M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"GitHub Changelog","item":"https://daily.dev/sources/github_updates"},{"@type":"ListItem","position":3,"name":"Copilot model access update for GitHub Team plans"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/copilot-model-access-update-for-github-team-plans-sko2tev7d#faq","mainEntity":[{"@type":"Question","name":"How does GitHub Copilot decide which AI models I can use if I have seats in multiple organizations?","acceptedAnswer":{"@type":"Answer","text":"Model access is now determined only by the organization that pays for your usage, found under 'Usage billed to' on the Copilot features page. Previously, you could use a model if any of your organizations had enabled it, but that policy has changed so billing and governance stay in sync across multi-org Copilot users. Track changes like this Copilot policy update to keep multi-org AI coding access configured correctly on daily.dev."}},{"@type":"Question","name":"Will this GitHub Copilot billing organization change affect users who only belong to one enterprise?","acceptedAnswer":{"@type":"Answer","text":"No, if Copilot access comes entirely through a single enterprise or its organizations, model access remains unaffected by this update. The change only applies to users holding Copilot seats across more than one organization, where the billing organization now solely governs which models are accessible. Developers managing enterprise Copilot rollouts follow policy changes like this one on daily.dev."}}]} ```