// AI Platform Drift

GitHub Copilot Automations now support shared team workflows

GitHub Copilot changelog · published 2026-10-28 18:23 UTC
WORTH KNOWING BUDGET PRICINGAPI
WHAT CHANGEDGitHub Copilot Automations can now be created as "Shared" type, visible to all repository readers and editable by writers. Shared automations bill AI credits to the repository owner (organization or user) instead of the individual creator, and actions are attributed to Copilot rather than individual users. Organization-owned repositories require administrators to enable the "Allow use of Copilot cloud agent billed to the organization" policy. Feature is rolling out to Copilot Pro, Pro+, Max, Business, and Enterprise plans starting 28 October 2026.
WHY IT MATTERSAI credit costs shift from individual users to the organization budget when teams use shared automations. Actions attributed to Copilot rather than individuals change audit trails and attribution for automated GitHub operations like issue comments, pull request updates, and repository modifications.
WHAT TO DOIf your organization uses Copilot Business or Enterprise, verify whether the "Allow use of Copilot cloud agent billed to the organization" policy is enabled in admin settings. Review current personal automations to determine which should remain individual (billed to user) versus shared (billed to organization), and update budget forecasts to account for organization-billed automation credits.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Build shared workflows for your team with Copilot Automations
+https://github.blog/changelog/2026-10-28-build-shared-workflows-for-your-team-with-copilot-automations
+Wed, 28 Oct 2026 15:35:00 +0000
+
+Shared Copilot Automations are rolling out, enabling teams to build and maintain AI-powered workflows together.
+With Copilot Automations, you can combine prompts, triggers, and tools to design workflows around the way your team works. Copilot runs autonomously in the cloud, using only the tools you’ve allowed. For example, you could create automations to:
+
+Reproduce bugs as soon as an issue is opened.
+Capture screenshots of the changes when a pull request is marked as ready.
+Automatically investigate production incidents as soon as they’re detected in your monitoring tool.
+
+Until now, automations have been personal, meaning only you could see and edit them, and they used your identity and AI credits. That works well for automating your own work, like drafting your standup updates, but not for workflows your whole team relies on. Shared automations let your team build and maintain those workflows together.
+How shared automations work
+
+Visible to your team: Everyone with read access to the repository can see a shared automation, and anyone with write access can edit it.
+Billed to the repository owner: AI credits are billed to the organization or user that owns the repository, rather than to the person who created the automation.
+Act as Copilot: Actions on GitHub are attributed to Copilot, rather than to any one user.
+Built to last: Shared automations belong to the repository, so they keep running if the person who created them leaves the team. Change history lets your team see how the tools, triggers, and prompt have evolved.
+
+For shared automations to run in an organization-owned repository, an administrator must enable the “Allow use of Copilot cloud agent billed to the organization” policy.
+Create a shared automation
+When you create an automation on github.com, the GitHub Copilot app , or Visual Studio Code, choose Shared under Type. You can’t change an automation’s type after you create it. To learn more, see personal and shared automations.
+Shared Copilot Automations are rolling out to users on Copilot Pro, Pro+, Max, Business, and Enterprise plans. Availability may vary as the rollout progresses. Once available, you can create automations in any repository where you have write access.
+Join the discussion within GitHub Community.
+
+The post Build shared workflows for your team with Copilot Automations appeared first on The GitHub Blog.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningNew shared automation feature with changed billing, permissions, and admin controls affects team deployment and cost allocation.
signalsnew feature rollout with future date (2026-10-28) · new billing model: credits billed to repository owner instead of individual user · new permission model: read access sees automations, write access can edit · new admin policy requirement: 'Allow use of Copilot cloud agent billed to the organization' · feature availability tied to plan tier (Pro, Pro+, Max, Business, Enterprise) · behavioral change: actions attributed to Copilot, not individual users
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)