<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/build-shared-workflows-for-your-team-with-copilot-automations-12pycs10n" -->

---
title: Build shared workflows for your team with Copilot...
description: GitHub is rolling out shared Copilot Automations, letting teams build and maintain AI-powered workflows together instead of only personal ones. Shared...
canonical: https://daily.dev/posts/build-shared-workflows-for-your-team-with-copilot-automations-12pycs10n
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Build shared workflows for your team with Copilot Automations | daily.dev
og:description: GitHub is rolling out shared Copilot Automations, letting teams build and maintain AI-powered workflows together instead of only personal ones. Shared...
og:url: https://daily.dev/posts/build-shared-workflows-for-your-team-with-copilot-automations-12pycs10n
og:image: https://api.daily.dev/og/posts/12PYcs10N.png
og:image:alt: Build shared workflows for your team with Copilot Automations
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.

# Build shared workflows for your team with Copilot Automations

**[GitHub Changelog](https://daily.dev/sources/github_updates)** · 2 min read · 0 upvotes · 0 comments

## Summary

GitHub is rolling out shared Copilot Automations, letting teams build and maintain AI-powered workflows together instead of only personal ones. Shared automations are visible to anyone with read access and editable by anyone with write access to the repository. AI credits get billed to the organization or repository owner rather than the creator, and actions are attributed to Copilot instead of an individual. The automations persist even if their creator leaves the team, and change history tracks edits to tools, triggers, and prompts. They're rolling out to Copilot Pro, Pro+, Max, Business, and Enterprise plans, and organization admins must enable a billing policy for them to run in org-owned repos.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://github.blog/changelog/2026-10-28-build-shared-workflows-for-your-team-with-copilot-automations>

## Questions this post answers

### What is the difference between personal and shared Copilot Automations on GitHub?

Personal automations are visible only to their creator and use that person's identity and AI credits, while shared automations are visible to everyone with read access to the repository and editable by anyone with write access. Shared automations bill AI credits to the organization or repository owner, attribute actions to Copilot instead of an individual, and keep running if the creator leaves the team.

_Teams standardizing on Copilot workflows can track rollout details like this on daily.dev._

### Which GitHub Copilot plans support shared Copilot Automations?

Shared Copilot Automations are rolling out to users on Copilot Pro, Pro+, Max, Business, and Enterprise plans, though availability may vary as the rollout progresses. Once available, automations can be created in any repository where the user has write access, choosing 'Shared' under 'Type' when creating it, a setting that cannot be changed afterward.

_Developers deciding when to adopt new Copilot features can follow rollout coverage on daily.dev._

### How do organizations enable billing for shared Copilot cloud agent automations?

An administrator must enable the 'Allow use of Copilot cloud agent billed to the organization' policy for shared automations to run in an organization-owned repository. This ensures AI credits are billed to the organization or user that owns the repository rather than to the individual who created the automation.

_Admins configuring org-wide AI tooling policies can keep tabs on changes like this via daily.dev._

## Similar posts on daily.dev

- [Agentic workflows no longer need a personal access token](https://daily.dev/posts/agentic-workflows-no-longer-need-a-personal-access-token-yztqlwbhg) · GitHub Changelog · 1 upvotes · 0 comments
- [A GitHub agentic workflow](https://daily.dev/posts/a-github-agentic-workflow-xqc7skb2g) · A Java geek · 53 upvotes · 2 comments
- [GitHub Agentic Workflows](https://daily.dev/posts/github-agentic-workflows-6xigduvrg) · Hacker News · 1 upvotes · 0 comments

---

Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#github](https://daily.dev/tags/github), [#automation](https://daily.dev/tags/automation), [#vscode](https://daily.dev/tags/vscode)

[View this post on daily.dev](https://daily.dev/posts/build-shared-workflows-for-your-team-with-copilot-automations-12pycs10n)

```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":"Build shared workflows for your team with Copilot Automations","url":"https://daily.dev/posts/build-shared-workflows-for-your-team-with-copilot-automations-12pycs10n","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/build-shared-workflows-for-your-team-with-copilot-automations-12pycs10n"},"datePublished":"2026-10-28T16:16:53.917Z","dateModified":"2026-10-28T16:36:13.994Z","description":"GitHub is rolling out shared Copilot Automations, letting teams build and maintain AI-powered workflows together instead of only personal ones. Shared...","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/build-shared-workflows-for-your-team-with-copilot-automations-12pycs10n","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,github,automation,vscode","timeRequired":"PT2M"}
{"@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":"Build shared workflows for your team with Copilot Automations"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/build-shared-workflows-for-your-team-with-copilot-automations-12pycs10n#faq","mainEntity":[{"@type":"Question","name":"What is the difference between personal and shared Copilot Automations on GitHub?","acceptedAnswer":{"@type":"Answer","text":"Personal automations are visible only to their creator and use that person's identity and AI credits, while shared automations are visible to everyone with read access to the repository and editable by anyone with write access. Shared automations bill AI credits to the organization or repository owner, attribute actions to Copilot instead of an individual, and keep running if the creator leaves the team. Teams standardizing on Copilot workflows can track rollout details like this on daily.dev."}},{"@type":"Question","name":"Which GitHub Copilot plans support shared Copilot Automations?","acceptedAnswer":{"@type":"Answer","text":"Shared Copilot Automations are rolling out to users on Copilot Pro, Pro+, Max, Business, and Enterprise plans, though availability may vary as the rollout progresses. Once available, automations can be created in any repository where the user has write access, choosing 'Shared' under 'Type' when creating it, a setting that cannot be changed afterward. Developers deciding when to adopt new Copilot features can follow rollout coverage on daily.dev."}},{"@type":"Question","name":"How do organizations enable billing for shared Copilot cloud agent automations?","acceptedAnswer":{"@type":"Answer","text":"An administrator must enable the 'Allow use of Copilot cloud agent billed to the organization' policy for shared automations to run in an organization-owned repository. This ensures AI credits are billed to the organization or user that owns the repository rather than to the individual who created the automation. Admins configuring org-wide AI tooling policies can keep tabs on changes like this via daily.dev."}}]}
```

