tions/security-guides/using-secrets-in-github-actions)
    * [ GitHub security features  ](/en/actions/security-guides/using-githubs-security-features-to-secure-your-use-of-github-actions)
    * [ Automatic token authentication  ](/en/actions/security-guides/automatic-token-authentication)

  * Creating actions 

    * [ About custom actions  ](/en/actions/creating-actions/about-custom-actions)
    * [ Create a Docker container action  ](/en/actions/creating-actions/creating-a-docker-container-action)
    * [ Create a JavaScript action  ](/en/actions/creating-actions/creating-a-javascript-action)
    * [ Create a composite action  ](/en/actions/creating-actions/creating-a-composite-action)
    * [ Metadata syntax  ](/en/actions/creating-actions/metadata-syntax-for-github-actions)
    * [ Dockerfile support  ](/en/actions/creating-actions/dockerfile-support-for-github-actions)
    * [ Set exit codes  ](/en/actions/creating-actions/setting-exit-codes-for-actions)
    * [ Publish in GitHub Marketplace  ](/en/actions/creating-actions/publishing-actions-in-github-marketplace)
    * [ Share from your private repository  ](/en/actions/creating-actions/sharing-actions-and-workflows-from-your-private-repository)
    * [ Share with your organization  ](/en/actions/creating-actions/sharing-actions-and-workflows-with-your-organization)
    * [ Release and maintain actions  ](/en/actions/creating-actions/releasing-and-maintaining-actions)
    * [ CLI setup action  ](/en/actions/creating-actions/developing-a-third-party-cli-action)

  * [ Guides for GitHub Actions  ](/en/actions/guides)

  * [ GitHub Actions ](/en/actions "GitHub Actions") / 
  * [ Using workflows ](/en/actions/using-workflows "Using workflows") / 
  * [ Share workflows with your organization ](/en/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization "Share workflows with your organization")

#  Sharing workflows, secrets, and runners with your organization

Learn how you can use organization features to collaborate with your team, by
sharing starter workflows, secrets, variables, and self-hosted runners.

##  In this article

  * Overview 
  * Sharing workflows 
  * Sharing secrets and variables within an organization 
  * Share self-hosted runners within an organization 
  * Next steps 

##  Overview

If you need to share workflows and other GitHub Actions features with your
team, then consider collaborating within a GitHub organization. An
organization allows you to centrally store and manage secrets, artifacts, and
self-hosted runners. You can also create starter workflows in the ` .github `
repository and share them with other users in your organization.

##  Sharing workflows

Your organization can share workflows by reusing the workflows exactly or by
creating starter workflows that provide templates for new workflows.

###  Reusing workflows

You can call one workflow from within another workflow. This allows you to
reuse workflows, avoiding duplication and making your workflows easier to
maintain. For more information, see " [ Reusing workflows ](/en/actions/using-
workflows/reusing-workflows) ."

###  Using starter workflows

Starter workflows allow everyone in your organization who has permission to
create workflows to do so more quickly and easily. When you create a new
workflow, you can choose a starter workflow and some or all of the work of
writing the workflow will be done for you. You can use starter workflows as a
starting place to build your custom workflow or use them as-is. This not only
saves time, it promotes consistency and best practice across your
organization. For more information, see " [ Creating starter workflows for
your organization ](/en/actions/using-workflows/creating-starter-workflows-
for-your-organization) ."

##  Sharing secrets and variables within an organization

You can centrally manage your secrets and variables within an organization,
and then make them available to selected repositories. This also