How to Use Org to control Custom Model?

[wbond]

Currently we are gating rollout of the custom model by having a custom org that we assign users to.

While working to try and perform some really basic evaluation before adding more users, one of our members tried to remove themselves from GitHub Copilot Access in the org settings.

As a result, their name was greyed out and the interface now says they'll be removed at the end of the billing period.

Do you have suggestions for how to move people in and out of access? Will we need to remove them from the org altogether to get the custom model to stop being used for their completions?

[thejoebourneidentity]

I believe you'll just need to remove their Copilot seat under the Copilot->Access settings. I don't think they need to be totally removed from the org. cc @ivanpk is this accurate?

[wbond]

The issue with removing their access is as shown in the screenshot above - the access stays until the end of the billing cycle.

[thejoebourneidentity]

Ah, I see. @justincampbell this seems to be a detail in how the licenses are managed once a seat is granted and later removed. Are you able to gleam from how the access works whether or not the user needs to be completely removed from the org?

[thejoebourneidentity]

Hey @wbond, @ivanpk just looked into this and found that if you need an immediate fix you should need to remove the user from the organization as well, otherwise they'll remain until the end of the billing cycle.