Merge branch 'main' into automatic-toc
This commit is contained in:
Sarita Iyer
@@ -26,7 +26,7 @@ Alternatively, you can enable {% data variables.product.prodname_actions %} in y
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** You might not be able to manage these settings if your organization has an overriding policy or is managed by an enterprise that has overriding policy. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %}
|
||||
**Note:** You might not be able to manage these settings if your organization has an overriding policy or is managed by an enterprise that has overriding policy. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21"%}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -48,7 +48,7 @@ You can disable all workflows for a repository or set a policy that configures w
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** You might not be able to manage these settings if your organization has an overriding policy or is managed by an enterprise that has overriding policy. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."
|
||||
**Note:** You might not be able to manage these settings if your organization has an overriding policy or is managed by an enterprise that has overriding policy. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif currentVersion ver_gt "enterprise-server@2.21" %}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -52,6 +52,10 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
|
||||
|
||||
8. To notify users that the release is not ready for production and may be unstable, select **This is a pre-release**.
|
||||
|
||||
{%- if currentVersion == "free-pro-team@latest" %}
|
||||
1. Optionally, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion.
|
||||
|
||||
{%- endif %}
|
||||
9. If you're ready to publicize your release, click **Publish release**. To work on the release later, click **Save draft**.
|
||||
|
||||
|
||||
|
||||
@@ -103,4 +103,4 @@ Organization owners and repository administrators can only grant access to view
|
||||
### Further reading
|
||||
|
||||
- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"
|
||||
- "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)"
|
||||
- "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)"
|
||||
|
||||
@@ -16,7 +16,7 @@ For each repository that you administer on {% data variables.product.prodname_do
|
||||
|
||||
This overview can help you audit access to your repository, onboard or off-board contractors or employees, and effectively respond to security incidents.
|
||||
|
||||
For more information about repository permission levels, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)."
|
||||
For more information about repository permission levels, see "[Permission levels for a user account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)."
|
||||
|
||||
|
||||
|
||||
@@ -52,10 +52,10 @@ For more information about repository permission levels, see "[Permission levels
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.navigate-to-manage-access %}
|
||||
4. Under "Manage access", find the team or person whose access you'd like to remove, then click {% octicon "trashcan" aria-label="The trashcan icon" %}.
|
||||
|
||||
4. Under "Manage access", find the team or person whose access you'd like to remove, then click {% octicon "trash" aria-label="The trash icon" %}.
|
||||
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)"
|
||||
- "[Setting base permissions for an organization](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)"
|
||||
- "[Setting base permissions for an organization](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization)"
|
||||
|
||||
@@ -13,7 +13,7 @@ topics:
|
||||
- repositories
|
||||
---
|
||||
|
||||
An organization owner must allow forks of private{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and internal{% endif %} repositories on the organization level before you can allow or disallow forks for a specific repository. For more information, see "[Managing the forking policy for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)."
|
||||
An organization owner must allow forks of private{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and internal{% endif %} repositories on the organization level before you can allow or disallow forks for a specific repository. For more information, see "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)."
|
||||
|
||||
{% data reusables.organizations.internal-repos-enterprise %}
|
||||
|
||||
|
||||
@@ -16,7 +16,7 @@ topics:
|
||||
|
||||
### About repository visibility changes
|
||||
|
||||
Organization owners can restrict the ability to change repository visibility to organization owners only. For more information, see "[Restricting repository visibility changes in your organization](/github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization)."
|
||||
Organization owners can restrict the ability to change repository visibility to organization owners only. For more information, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)."
|
||||
|
||||
We recommend reviewing the following caveats before you change the visibility of a repository.
|
||||
|
||||
|
||||
@@ -51,5 +51,5 @@ After an enterprise or organization owner enables or enforces SAML SSO for an or
|
||||
|
||||
### Further reading
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}- "[About identity and access management with SAML single sign-on](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %}
|
||||
{% if currentVersion == "free-pro-team@latest" %}- "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %}
|
||||
{% if currentVersion == "github-ae@latest" %}- "[About identity and access management for your enterprise](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %}
|
||||
|
||||
@@ -17,13 +17,13 @@ topics:
|
||||
|
||||
Personal access tokens (PATs) are an alternative to using passwords for authentication to {% data variables.product.product_name %} when using the [GitHub API](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) or the [command line](#using-a-token-on-the-command-line).
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}If you want to use a PAT to access resources owned by an organization that uses SAML SSO, you must authorize the PAT. For more information, see "[About authentication with SAML single sign-on](/articles/about-authentication-with-saml-single-sign-on)" and "[Authorizing a personal access token for use with SAML single sign-on](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)."{% endif %}
|
||||
{% if currentVersion == "free-pro-team@latest" %}If you want to use a PAT to access resources owned by an organization that uses SAML SSO, you must authorize the PAT. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" and "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)."{% endif %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %}
|
||||
|
||||
### Creating a token
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}1. [Verify your email address](/articles/verifying-your-email-address), if it hasn't been verified yet.{% endif %}
|
||||
{% if currentVersion == "free-pro-team@latest" %}1. [Verify your email address](/github/getting-started-with-github/verifying-your-email-address), if it hasn't been verified yet.{% endif %}
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.developer_settings %}
|
||||
{% data reusables.user_settings.personal_access_tokens %}
|
||||
@@ -47,13 +47,13 @@ Personal access tokens (PATs) are an alternative to using passwords for authenti
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning:** Treat your tokens like passwords and keep them secret. When working with the API, use tokens as environment variables instead of hardcoding them into your programs.
|
||||
|
||||
{% endwarning %}
|
||||
{% if currentVersion == "free-pro-team@latest" %}9. To use your token to authenticate to an organization that uses SAML SSO, [authorize the token for use with a SAML single-sign-on organization](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).{% endif %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}9. To use your token to authenticate to an organization that uses SAML SSO, [authorize the token for use with a SAML single-sign-on organization](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).{% endif %}
|
||||
|
||||
### Using a token on the command line
|
||||
|
||||
@@ -61,7 +61,7 @@ Personal access tokens (PATs) are an alternative to using passwords for authenti
|
||||
|
||||
Personal access tokens can only be used for HTTPS Git operations. If your repository uses an SSH remote URL, you will need to [switch the remote from SSH to HTTPS](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-ssh-to-https).
|
||||
|
||||
If you are not prompted for your username and password, your credentials may be cached on your computer. You can [update your credentials in the Keychain](/articles/updating-credentials-from-the-osx-keychain) to replace your old password with the token.
|
||||
If you are not prompted for your username and password, your credentials may be cached on your computer. You can [update your credentials in the Keychain](/github/getting-started-with-github/updating-credentials-from-the-macos-keychain) to replace your old password with the token.
|
||||
|
||||
### Further reading
|
||||
|
||||
|
||||
@@ -20,7 +20,7 @@ To keep your account secure, we recommend you follow these best practices:
|
||||
- Use a password manager, such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/), to generate a password of at least 15 characters.
|
||||
- Generate a unique password for {% data variables.product.product_name %}. If you use your {% data variables.product.product_name %} password elsewhere and that service is compromised, then attackers or other malicious actors could use that information to access your {% data variables.product.product_name %} account.
|
||||
- Configure two-factor authentication for your personal account. For more information, see "[About two-factor authentication](/articles/about-two-factor-authentication)."
|
||||
- Never share your password, even with a potential collaborator. Each person should use their own personal account on {% data variables.product.product_name %}. For more information on ways to collaborate, see: "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)," "[About collaborative development models](/articles/about-collaborative-development-models/)," or "[Collaborating with groups in organizations](/articles/collaborating-with-groups-in-organizations/)."
|
||||
- Never share your password, even with a potential collaborator. Each person should use their own personal account on {% data variables.product.product_name %}. For more information on ways to collaborate, see: "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)," "[About collaborative development models](/articles/about-collaborative-development-models/)," or "[Collaborating with groups in organizations](/organizations/collaborating-with-groups-in-organizations/)."
|
||||
|
||||
{% data reusables.repositories.blocked-passwords %}
|
||||
|
||||
|
||||
@@ -186,7 +186,6 @@ An overview of some of the most common actions that are recorded as events in th
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `repo_funding_link_button_toggle` | Triggered when you enable or disable a sponsor button in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)")
|
||||
| `repo_funding_links_file_action` | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)")
|
||||
| `sponsor_sponsorship_cancel` | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")
|
||||
| `sponsor_sponsorship_create` | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor)")
|
||||
@@ -194,9 +193,11 @@ An overview of some of the most common actions that are recorded as events in th
|
||||
| `sponsor_sponsorship_tier_change` | Triggered when you upgrade or downgrade your sponsorship (see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")
|
||||
| `sponsored_developer_approve` | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)")
|
||||
| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)")
|
||||
| `sponsored_developer_disable` | Triggered when your {% data variables.product.prodname_sponsors %} account is disabled
|
||||
| `sponsored_developer_redraft` | Triggered when your {% data variables.product.prodname_sponsors %} account is returned to draft state from approved state
|
||||
| `sponsored_developer_profile_update` | Triggered when you edit your sponsored developer profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors)")
|
||||
| `sponsored_developer_request_approval` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)")
|
||||
| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Changing your sponsorship tiers](/articles/changing-your-sponsorship-tiers)")
|
||||
| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")
|
||||
| `sponsored_developer_update_newsletter_send` | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/articles/contacting-your-sponsors)")
|
||||
| `waitlist_invite_sponsored_developer` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)")
|
||||
| `waitlist_join` | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your user account](/github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account)")
|
||||
|
||||
@@ -18,7 +18,7 @@ You can create and participate in issues, pull requests, and team discussions, d
|
||||
|
||||
Issues are useful for discussing specific details of a project such as bug reports and planned improvements. For more information, see "[About issues](/articles/about-issues)." Pull requests allow you to comment directly on proposed changes. For more information, see "[About pull requests](/articles/about-pull-requests)" and "[Commenting on a pull request](/articles/commenting-on-a-pull-request)."
|
||||
|
||||
{% data reusables.organizations.team-discussions-purpose %} For more information, see "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)."
|
||||
{% data reusables.organizations.team-discussions-purpose %} For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)."
|
||||
|
||||
### Reacting to ideas in comments
|
||||
|
||||
|
||||
@@ -15,7 +15,7 @@ topics:
|
||||
|
||||
After a pull request is opened, anyone with *read* access can review and comment on the changes it proposes. You can also suggest specific changes to lines of code, which the author can apply directly from the pull request. For more information, see "[Reviewing proposed changes in a pull request](/articles/reviewing-proposed-changes-in-a-pull-request)."
|
||||
|
||||
Repository owners and collaborators can request a pull request review from a specific person. Organization members can also request a pull request review from a team with read access to the repository. For more information, see "[Requesting a pull request review](/articles/requesting-a-pull-request-review)." {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}You can specify a subset of team members to be automatically assigned in the place of the whole team. For more information, see "[Managing code review assignment for your team](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)."{% endif %}
|
||||
Repository owners and collaborators can request a pull request review from a specific person. Organization members can also request a pull request review from a team with read access to the repository. For more information, see "[Requesting a pull request review](/articles/requesting-a-pull-request-review)." {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}You can specify a subset of team members to be automatically assigned in the place of the whole team. For more information, see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)."{% endif %}
|
||||
|
||||
Reviews allow for discussion of proposed changes and help ensure that the changes meet the repository's contributing guidelines and other quality standards. You can define which individuals or teams own certain types or areas of code in a CODEOWNERS file. When a pull request modifies code that has a defined owner, that individual or team will automatically be requested as a reviewer. For more information, see "[About code owners](/articles/about-code-owners/)."
|
||||
|
||||
|
||||
@@ -37,7 +37,7 @@ If the branch you want to delete is associated with an open pull request, you mu
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.navigate-to-branches %}
|
||||
1. Scroll to the branch that you want to delete, then click {% octicon "trashcan" aria-label="The trashcan icon to delete the branch" %}.
|
||||
1. Scroll to the branch that you want to delete, then click {% octicon "trash" aria-label="The trash icon to delete the branch" %}.
|
||||
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
|
||||
|
||||
@@ -13,7 +13,7 @@ topics:
|
||||
|
||||
Owners and collaborators on a repository owned by a user account can assign pull request reviews. Organization members with triage permissions to a repository can assign a pull request review.
|
||||
|
||||
Owners or collaborators can assign a pull request review to any person that has been explicitly granted [read access](/articles/access-permissions-on-github) to a user-owned repository. Organization members can assign a pull request review to any person or team with read access to a repository. The requested reviewer or team will receive a notification that you asked them to review the pull request. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}If you request a review from a team and code review assignment is enabled, specific members will be requested and the team will be removed as a reviewer. For more information, see "[Managing code review assignment for your team](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)."{% endif %}
|
||||
Owners or collaborators can assign a pull request review to any person that has been explicitly granted [read access](/articles/access-permissions-on-github) to a user-owned repository. Organization members can assign a pull request review to any person or team with read access to a repository. The requested reviewer or team will receive a notification that you asked them to review the pull request. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}If you request a review from a team and code review assignment is enabled, specific members will be requested and the team will be removed as a reviewer. For more information, see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)."{% endif %}
|
||||
|
||||
{% note %}
|
||||
|
||||
|
||||
@@ -79,5 +79,5 @@ If you change the visibility of an internal repository and then delete the repos
|
||||
- "[Setting repository visibility](/articles/setting-repository-visibility)"
|
||||
- "[About forks](/articles/about-forks)"
|
||||
- "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)"
|
||||
- "[Managing the forking policy for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization)"
|
||||
- "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)"
|
||||
- "{% if currentVersion == "free-pro-team@latest" %}[Enforcing repository management policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account#enforcing-a-policy-on-forking-private-or-internal-repositories){% else %}[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-forking-private-or-internal-repositories){% endif %}"
|
||||
|
||||
@@ -23,7 +23,7 @@ Code owners are automatically requested for review when someone opens a pull req
|
||||
|
||||
When someone with admin or owner permissions has enabled required reviews, they also can optionally require approval from a code owner before the author can merge a pull request in the repository. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)."
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}If a team has enabled code review assignments, the individual approvals won't satisfy the requirement for code owner approval in a protected branch. For more information, see "[Managing code review assignment for your team](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)."{% endif %}
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}If a team has enabled code review assignments, the individual approvals won't satisfy the requirement for code owner approval in a protected branch. For more information, see "[Managing code review assignment for your team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)."{% endif %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
If a file has a code owner, you can see who the code owner is before you open a pull request. In the repository, you can browse to the file and hover over {% octicon "shield-lock" aria-label="The edit icon" %}.
|
||||
|
||||
@@ -21,7 +21,7 @@ Private repositories are only accessible to you, people you explicitly share acc
|
||||
Public repositories are accessible to everyone on the internet. Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members. Internal repositories are accessible to enterprise members. For more information, see "[About internal repositories](#about-internal-repositories)."
|
||||
{% endif %}
|
||||
|
||||
Organization owners always have access to every repository created in an organization. For more information, see "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization)."
|
||||
Organization owners always have access to every repository created in an organization. For more information, see "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)."
|
||||
|
||||
People with admin permissions for a repository can change an existing repository's visibility. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)."
|
||||
|
||||
|
||||
@@ -42,7 +42,7 @@ $ ssh -T git@{% data variables.command_line.codeblock %}
|
||||
> provide shell access.
|
||||
```
|
||||
|
||||
If the repository belongs to an organization and you're using an SSH key generated by an OAuth App, OAuth App access may have been restricted by an organization owner. For more information, see "<a href="/github/setting-up-and-managing-organizations-and-teams/about-oauth-app-access-restrictions" class="dotcom-only">About OAuth App access restrictions</a>."
|
||||
If the repository belongs to an organization and you're using an SSH key generated by an OAuth App, OAuth App access may have been restricted by an organization owner. For more information, see "<a href="/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions" class="dotcom-only">About OAuth App access restrictions</a>."
|
||||
|
||||
For more information, see [Adding a new SSH key to your GitHub account](/articles/adding-a-new-ssh-key-to-your-github-account).
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ You decide how to generate {% data variables.product.prodname_code_scanning %} a
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-security %}
|
||||
3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %}
|
||||
3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %}
|
||||
|
||||
4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow.
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.{% endif %}
|
||||
|
||||
@@ -37,7 +37,7 @@ For information about {% data variables.product.prodname_advanced_security %} fe
|
||||
The site administrator must enable {% data variables.product.prodname_advanced_security %} for {% data variables.product.product_location %} before you can use these features. For more information, see "[Configuring Advanced Security features](/admin/configuration/configuring-advanced-security-features)."
|
||||
{% endif %}
|
||||
|
||||
Once your system is set up, you can enable and disable these features at the organization or repository level. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."
|
||||
Once your system is set up, you can enable and disable these features at the organization or repository level. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -46,7 +46,7 @@ Once your system is set up, you can enable and disable these features at the org
|
||||
|
||||
For public repositories on {% data variables.product.prodname_dotcom_the_website %}, these features are permanently on and can only be disabled if you change the visibility of the project so that the code is no longer public.
|
||||
|
||||
For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %}
|
||||
For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -68,8 +68,8 @@ You're now connected to the {% data variables.product.product_name %} community.
|
||||
|
||||
|
||||
|
||||
- [Set up Git](/articles/set-up-git)
|
||||
- [Create a repository](/articles/create-a-repo)
|
||||
- [Fork a repository](/articles/fork-a-repo)
|
||||
- "[Set up Git](/articles/set-up-git)"
|
||||
- "[Create a repository](/articles/create-a-repo)"
|
||||
- "[Fork a repository](/articles/fork-a-repo)"
|
||||
- **Be social**
|
||||
- {% data reusables.support.connect-in-the-forum-bootcamp %}
|
||||
|
||||
@@ -151,5 +151,6 @@ You have now forked a repository, practiced cloning your fork, and configured an
|
||||
|
||||
- "[Set up Git](/articles/set-up-git)"
|
||||
- "[Create a repository](/articles/create-a-repo)"
|
||||
- **Fork a repository**
|
||||
- "[Be social](/articles/be-social)"
|
||||
- {% data reusables.support.connect-in-the-forum-bootcamp %}
|
||||
|
||||
@@ -98,15 +98,4 @@ In addition to the features available with {% data variables.product.prodname_te
|
||||
|
||||
You can set up a trial to evaluate {% data variables.product.prodname_ghe_cloud %}. For more information, see "<a href="/articles/setting-up-a-trial-of-github-enterprise-cloud" class="dotcom-only">Setting up a trial of {% data variables.product.prodname_ghe_cloud %}</a>."
|
||||
|
||||
For more information about hosting your own instance of [{% data variables.product.prodname_ghe_server %}](https://enterprise.github.com), contact {% data variables.contact.contact_enterprise_sales %}. {% data reusables.enterprise_installation.request-a-trial %}
|
||||
|
||||
### {% data variables.product.prodname_ghe_one %}
|
||||
|
||||
{% data variables.product.prodname_ghe_one %} includes [{% data variables.product.prodname_enterprise %}](#github-enterprise), plus:
|
||||
|
||||
- {% data variables.contact.github_support %} {% data variables.product.premium_plus_support_plan %}
|
||||
- {% data variables.product.prodname_insights %}
|
||||
- {% data variables.product.prodname_GH_advanced_security %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."{% endif %}{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.22" %}. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."{% endif %}
|
||||
- [{% data variables.product.prodname_learning %} for organizations](https://lab.github.com/organizations)
|
||||
|
||||
For more information about signing up for {% data variables.product.prodname_ghe_one %}, contact {% data variables.contact.contact_enterprise_sales %}.
|
||||
For more information about hosting your own instance of [{% data variables.product.prodname_ghe_server %}](https://enterprise.github.com), contact {% data variables.contact.contact_enterprise_sales %}. {% data reusables.enterprise_installation.request-a-trial %}
|
||||
@@ -42,6 +42,9 @@ Below is a list of some of the available keyboard shortcuts.
|
||||
|
||||
| Keyboard shortcut | Description
|
||||
|-----------|------------
|
||||
| <kbd>control b</kbd> or <kbd>command b</kbd> | Inserts Markdown formatting for bolding text
|
||||
| <kbd>control i</kbd> or <kbd>command i</kbd> | Inserts Markdown formatting for italicizing text
|
||||
| <kbd>control k</kbd> or <kbd>command k</kbd> | Inserts Markdown formatting for creating a link
|
||||
|<kbd>e</kbd> | Open source code file in the **Edit file** tab
|
||||
|<kbd>control f</kbd> or <kbd>command f</kbd> | Start searching in file editor
|
||||
|<kbd>control g</kbd> or <kbd>command g</kbd> | Find next
|
||||
@@ -52,6 +55,7 @@ Below is a list of some of the available keyboard shortcuts.
|
||||
|<kbd>control z</kbd> or <kbd>command z</kbd> | Undo
|
||||
|<kbd>control y</kbd> or <kbd>command y</kbd> | Redo
|
||||
|<kbd>cmd + shift + p</kbd> | Toggles between the **Edit file** and **Preview changes** tabs
|
||||
|<kbd>control s</kbd> or <kbd>command s</kbd> | Write a commit message
|
||||
|
||||
For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirror.net/doc/manual.html#commands).
|
||||
|
||||
|
||||
@@ -23,7 +23,7 @@ versions:
|
||||
{% link_in_list /managing-subscriptions-and-notifications-on-github %}
|
||||
|
||||
<!-- Notifications v1 -->
|
||||
{% link_in_list /setting-up-and-managing-organizations-and-teams %}
|
||||
|
||||
{% link_in_list /setting-up-and-managing-your-enterprise %}
|
||||
{% link_in_list /setting-up-and-managing-billing-and-payments-on-github %}
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ If the file{% if currentVersion == "free-pro-team@latest" or currentVersion ver_
|
||||
### Deleting a file
|
||||
|
||||
1. Browse to the file in your repository that you want to delete.
|
||||
2. At the top of the file, click {% octicon "trashcan" aria-label="The trashcan icon" %}.
|
||||
2. At the top of the file, click {% octicon "trash" aria-label="The trash icon" %}.
|
||||
{% data reusables.files.write_commit_message %}
|
||||
{% data reusables.files.choose-commit-email %}
|
||||
{% data reusables.files.choose_commit_branch %}
|
||||
|
||||
@@ -19,7 +19,7 @@ When your code depends on a package that has a security vulnerability, this vuln
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)."{% else %}
|
||||
- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. For more information about advisory data, see "<a href="/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database" class="dotcom-only">Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}</a>."{% endif %}
|
||||
- New advisory data is synchronized to {% data variables.product.prodname_ghe_server %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %}
|
||||
- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% if currentVersion == "free-pro-team@latest" %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
|
||||
|
||||
{% data reusables.repositories.dependency-review %}
|
||||
@@ -42,9 +42,9 @@ For a list of the ecosystems that {% data variables.product.product_name %} can
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies in _public_ repositories and generates {% data variables.product.prodname_dependabot_alerts %} by default. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories.
|
||||
|
||||
You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)."
|
||||
You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization)."
|
||||
|
||||
For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)."
|
||||
For information about permission requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository permission levels for an organization](/organizations/collaborating-with-groups-in-organizations/repository-permission-levels-for-an-organization#permission-requirements-for-security-features)."
|
||||
|
||||
{% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)."
|
||||
{% endif %}
|
||||
|
||||
@@ -13,7 +13,7 @@ topics:
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% else %}When {% data variables.product.product_name %} detects vulnerable dependencies in your repositories, it sends security alerts.{% endif %}{% if currentVersion == "free-pro-team@latest" %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability.
|
||||
{% endif %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created repositories. For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)."
|
||||
{% if currentVersion == "free-pro-team@latest" %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/collaborating-with-groups-in-organizations/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)."
|
||||
{% endif %}
|
||||
|
||||
{% if enterpriseServerVersions contains currentVersion and currentVersion == "enterprise-server@2.21" %}
|
||||
|
||||
@@ -65,7 +65,7 @@ Email notifications also allow flexibility with the types of notifications you r
|
||||
|
||||
### About participating and watching notifications
|
||||
|
||||
When you watch a repository, you're subscribing to updates for activity in that repository. Similarly, when you watch a specific team's discussions, you're subscribing to all conversation updates on that team's page. For more information, see "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)."
|
||||
When you watch a repository, you're subscribing to updates for activity in that repository. Similarly, when you watch a specific team's discussions, you're subscribing to all conversation updates on that team's page. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)."
|
||||
|
||||
To see repositories that you're watching, go to your [watching page](https://github.com/watching). For more information, see "[Managing subscriptions and notifications on GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)."
|
||||
{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}
|
||||
@@ -76,7 +76,7 @@ You can configure notifications for a repository on the repository page, or on y
|
||||
#### About custom notifications
|
||||
{% data reusables.notifications-v2.custom-notifications-beta %}
|
||||
You can customize notifications for a repository, for example, you can choose to only be notified when updates to one or more types of events (issues, pull request, releases, discussions) happen within a repository, or ignore all notifications for a repository.
|
||||
{% endif %} For more information, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#configuring-your-watch-settings-for-an-individual-repository)."
|
||||
{% endif %} For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below.
|
||||
|
||||
#### Participating in conversations
|
||||
Anytime you comment in a conversation or when someone @mentions your username, you are _participating_ in a conversation. By default, you are automatically subscribed to a conversation when you participate in it. You can unsubscribe from a conversation you've participated in manually by clicking **Unsubscribe** on the issue or pull request or through the **Unsubscribe** option in the notifications inbox.
|
||||
|
||||
@@ -38,7 +38,7 @@ To see an overview of your repository subscriptions, see "[Reviewing repositorie
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
{% tip %}
|
||||
|
||||
**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below.
|
||||
**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
|
||||
|
||||
{% endtip %}
|
||||
{% endif %}
|
||||
|
||||
@@ -20,7 +20,7 @@ topics:
|
||||
|
||||
- To edit a milestone, next to the milestone you want to edit, click **Edit**.
|
||||
|
||||
5. Type the milestone's title, description, or other changes, and click **Create milestone** or **Save changes**.
|
||||
5. Type the milestone's title, description, or other changes, and click **Create milestone** or **Save changes**. Milestones will render Markdown syntax. For more information about Markdown syntax, see "[Basic writing and formatting syntax](/github/writing-on-github/basic-writing-and-formatting-syntax)."
|
||||
|
||||
### Deleting milestones
|
||||
|
||||
|
||||
@@ -19,15 +19,15 @@ When you downgrade or cancel a sponsorship, the change will become effective on
|
||||
|
||||
{% data reusables.sponsors.navigate-to-sponsored-account %}
|
||||
{% data reusables.sponsors.sponsorship-dashboard %}
|
||||
{% data reusables.sponsors.review-tiers-to-select %}
|
||||
{% data reusables.sponsors.select-a-tier %}
|
||||
{% data reusables.sponsors.update-sponsorship %}
|
||||
|
||||
### Canceling a sponsorship
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.billing %}
|
||||
{% data reusables.user_settings.billing_plans %}
|
||||
{% data reusables.sponsors.billing-switcher %}
|
||||
{% data reusables.user_settings.subscriptions-tab %}
|
||||
3. Under "{% data variables.product.prodname_sponsors %}", to the right of the sponsored open source contributor, click {% octicon "triangle-down" aria-label="The down triangle octicon" %} next to your sponsored amount, then click **Cancel sponsorship**.
|
||||
|
||||
4. Review the information about canceling your sponsorship, then click **OK**.
|
||||
|
||||
@@ -19,5 +19,6 @@ When you upgrade your sponsorship tier, the change will become effective immedia
|
||||
|
||||
{% data reusables.sponsors.navigate-to-sponsored-account %}
|
||||
{% data reusables.sponsors.sponsorship-dashboard %}
|
||||
{% data reusables.sponsors.review-tiers-to-select %}
|
||||
{% data reusables.sponsors.select-a-tier %}
|
||||
{% data reusables.sponsors.update-sponsorship %}
|
||||
|
||||
@@ -58,7 +58,7 @@ You can upgrade your organization from {% data variables.product.prodname_free_t
|
||||
|
||||
#### Next steps for organizations using {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
If you upgraded your organization to {% data variables.product.prodname_ghe_cloud %}, you can set up identity and access management for your organization. For more information, see "[Managing SAML single sign-on for your organization](/articles/managing-saml-single-sign-on-for-your-organization)."
|
||||
If you upgraded your organization to {% data variables.product.prodname_ghe_cloud %}, you can set up identity and access management for your organization. For more information, see "[Managing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization)."
|
||||
|
||||
If you'd like to use an enterprise account with {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. For more information, see "[About enterprise accounts](/articles/about-enterprise-accounts)."
|
||||
|
||||
|
||||
@@ -29,5 +29,5 @@ You can check how many seats your license includes and how many of them are curr
|
||||
|
||||
6. On the "Security & analysis" settings page, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section to see a detailed breakdown of usage by repository for this organization.
|
||||
|
||||
For more information, see "[Managing security and analysis settings for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization)."
|
||||
For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
|
||||
|
||||
|
||||
@@ -1,61 +0,0 @@
|
||||
---
|
||||
title: About identity and access management with SAML single sign-on
|
||||
intro: 'If you centrally manage your users'' identities and applications with an identity provider (IdP), you can configure Security Assertion Markup Language (SAML) single sign-on (SSO) to protect your organization''s resources on {% data variables.product.prodname_dotcom %}.'
|
||||
product: '{% data reusables.gated-features.saml-sso %}'
|
||||
redirect_from:
|
||||
- /articles/about-identity-and-access-management-with-saml-single-sign-on
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
### About SAML SSO
|
||||
|
||||
{% data reusables.saml.dotcom-saml-explanation %}
|
||||
|
||||
After you configure SAML SSO, members of your {% data variables.product.prodname_dotcom %} organization will continue to log into their user accounts on {% data variables.product.prodname_dotcom %}. When a member accesses resources within your organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} redirects the member to your IdP to authenticate. After successful authentication, your IdP redirects the member back to {% data variables.product.prodname_dotcom %}, where the member can access your organization's resources.
|
||||
|
||||
Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. For more information, see "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)."
|
||||
|
||||
{% data reusables.saml.outside-collaborators-exemption %}
|
||||
|
||||
Before enabling SAML SSO for your organization, you'll need to connect your IdP to your organization. For more information, see "[Connecting your identity provider to your organization](/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization)."
|
||||
|
||||
For an organization, SAML SSO can be disabled, enabled but not enforced, or enabled and enforced. After you enable SAML SSO for your organization and your organization's members successfully authenticate with your IdP, you can enforce the SAML SSO configuration. For more information about enforcing SAML SSO for your {% data variables.product.prodname_dotcom %} organization, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
|
||||
|
||||
Members must periodically authenticate with your IdP to authenticate and gain access to your organization's resources. The duration of this login period is specified by your IdP and is generally 24 hours. This periodic login requirement limits the length of access and requires users to re-identify themselves to continue.
|
||||
|
||||
To access the organization's protected resources using the API and Git on the command line, members must authorize and authenticate with a personal access token or SSH key. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."
|
||||
|
||||
The first time a member uses SAML SSO to access your organization, {% data variables.product.prodname_dotcom %} automatically creates a record that links your organization, the member's {% data variables.product.prodname_dotcom %} account, and the member's account on your IdP. You can view and revoke the linked SAML identity, active sessions, and authorized credentials for members of your organization or enterprise account. For more information, see "[Viewing and managing a member's SAML access to your organization](/github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization)" and "[Viewing and managing a user's SAML access to your enterprise account](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)."
|
||||
|
||||
If members are signed in with a SAML SSO session when they create a new repository, the default visibility of that repository is private. Otherwise, the default visibility is public. For more information on repository visibility, see "[About repository visibility](/github/creating-cloning-and-archiving-repositories/about-repository-visibility)."
|
||||
|
||||
Organization members must also have an active SAML session to authorize an {% data variables.product.prodname_oauth_app %}. You can opt out of this requirement by contacting {% data variables.contact.contact_support %}. {% data variables.product.product_name %} does not recommend opting out of this requirement, which will expose your organization to a higher risk of account takeovers and potential data loss.
|
||||
|
||||
{% data reusables.saml.saml-single-logout-not-supported %}
|
||||
|
||||
### Supported SAML services
|
||||
|
||||
{% data reusables.saml.saml-supported-idps %}
|
||||
|
||||
Some IdPs support provisioning access to a {% data variables.product.prodname_dotcom %} organization via SCIM. For more information, see "[About SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)."
|
||||
|
||||
### Adding members to an organization using SAML SSO
|
||||
|
||||
After you enable SAML SSO, there are multiple ways you can add new members to your organization. Organization owners can invite new members manually on {% data variables.product.product_name %} or using the API. For more information, see "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)" and "[Members](/rest/reference/orgs#add-or-update-organization-membership)."
|
||||
|
||||
To provision new users without an invitation from an organization owner, you can use the URL `https://github.com/orgs/ORGANIZATION/sso/sign_up`, replacing _ORGANIZATION_ with the name of your organization. For example, you can configure your IdP so that anyone with access to the IdP can click a link on the IdP's dashboard to join your {% data variables.product.prodname_dotcom %} organization.
|
||||
|
||||
If your IdP supports SCIM, {% data variables.product.prodname_dotcom %} can automatically invite members to join your organization when you grant access on your IdP. If you remove a member's access to your {% data variables.product.prodname_dotcom %} organization on your SAML IdP, the member will be automatically removed from the {% data variables.product.prodname_dotcom %} organization. For more information, see "[About SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)."
|
||||
|
||||
{% data reusables.organizations.team-synchronization %}
|
||||
|
||||
{% data reusables.saml.saml-single-logout-not-supported %}
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[About two-factor authentication and SAML single sign-on ](/articles/about-two-factor-authentication-and-saml-single-sign-on)"
|
||||
- "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)"
|
||||
@@ -1,59 +0,0 @@
|
||||
---
|
||||
title: About OAuth App access restrictions
|
||||
intro: 'Organizations can choose which {% data variables.product.prodname_oauth_app %}s have access to their repositories and other resources by enabling {% data variables.product.prodname_oauth_app %} access restrictions.'
|
||||
redirect_from:
|
||||
- /articles/about-third-party-application-restrictions/
|
||||
- /articles/about-oauth-app-access-restrictions
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
When {% data variables.product.prodname_oauth_app %} access restrictions are enabled, organization members cannot authorize {% data variables.product.prodname_oauth_app %} access to organization resources. Organization members can request owner approval for {% data variables.product.prodname_oauth_app %}s they'd like to use, and organization owners receive a notification of pending requests.
|
||||
|
||||
{% data reusables.organizations.oauth_app_restrictions_default %}
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip**: When an organization has not set up {% data variables.product.prodname_oauth_app %} access restrictions, any {% data variables.product.prodname_oauth_app %} authorized by an organization member can also access the organization's private resources.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
### Setting up {% data variables.product.prodname_oauth_app %} access restrictions
|
||||
|
||||
When an organization owner sets up {% data variables.product.prodname_oauth_app %} access restrictions for the first time:
|
||||
|
||||
- **Applications that are owned by the organization** are automatically given access to the organization's resources.
|
||||
- **{% data variables.product.prodname_oauth_app %}s** immediately lose access to the organization's resources.
|
||||
- **SSH keys created before February 2014** immediately lose access to the organization's resources (this includes user and deploy keys).
|
||||
- **SSH keys created by {% data variables.product.prodname_oauth_app %}s during or after February 2014** immediately lose access to the organization's resources.
|
||||
- **Hook deliveries from private organization repositories** will no longer be sent to unapproved {% data variables.product.prodname_oauth_app %}s.
|
||||
- **API access** to private organization resources is not available for unapproved {% data variables.product.prodname_oauth_app %}s. In addition, there are no privileged create, update, or delete actions on public organization resources.
|
||||
- **Hooks created by users and hooks created before May 2014** will not be affected.
|
||||
- **Private forks of organization-owned repositories** are subject to the organization's access restrictions.
|
||||
|
||||
### Resolving SSH access failures
|
||||
|
||||
When an SSH key created before February 2014 loses access to an organization with {% data variables.product.prodname_oauth_app %} access restrictions enabled, subsequent SSH access attempts will fail. Users will encounter an error message directing them to a URL where they can approve the key or upload a trusted key in its place.
|
||||
|
||||
### Webhooks
|
||||
|
||||
When an {% data variables.product.prodname_oauth_app %} is granted access to the organization after restrictions are enabled, any pre-existing webhooks created by that {% data variables.product.prodname_oauth_app %} will resume dispatching.
|
||||
|
||||
When an organization removes access from a previously-approved {% data variables.product.prodname_oauth_app %}, any pre-existing webhooks created by that application will no longer be dispatched (these hooks will be disabled, but not deleted).
|
||||
|
||||
### Re-enabling access restrictions
|
||||
|
||||
If an organization disables {% data variables.product.prodname_oauth_app %} access application restrictions, and later re-enables them, previously approved {% data variables.product.prodname_oauth_app %} are automatically granted access to the organization's resources.
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[Enabling {% data variables.product.prodname_oauth_app %} access restrictions for your organization](/articles/enabling-oauth-app-access-restrictions-for-your-organization)"
|
||||
- "[Approving {% data variables.product.prodname_oauth_app %}s for your organization](/articles/approving-oauth-apps-for-your-organization)"
|
||||
- "[Reviewing your organization's installed integrations](/articles/reviewing-your-organization-s-installed-integrations)"
|
||||
- "[Denying access to a previously approved {% data variables.product.prodname_oauth_app %} for your organization](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization)"
|
||||
- "[Disabling {% data variables.product.prodname_oauth_app %} access restrictions for your organization](/articles/disabling-oauth-app-access-restrictions-for-your-organization)"
|
||||
- "[Requesting organization approval for {% data variables.product.prodname_oauth_app %}s](/articles/requesting-organization-approval-for-oauth-apps)"
|
||||
- "[Authorizing {% data variables.product.prodname_oauth_app %}s](/articles/authorizing-oauth-apps)"
|
||||
@@ -1,32 +0,0 @@
|
||||
---
|
||||
title: About organizations
|
||||
intro: Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once. Owners and administrators can manage member access to the organization's data and projects with sophisticated security and administrative features.
|
||||
redirect_from:
|
||||
- /articles/about-organizations
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
{% data reusables.organizations.organizations_include %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
### Organizations and enterprise accounts
|
||||
|
||||
Enterprise accounts allow owners to centrally manage policy and billing for multiple {% data variables.product.prodname_dotcom_the_website %} organizations.
|
||||
|
||||
For organizations that belong to an enterprise account, billing is managed at the enterprise account level, and billing settings are not available at the organization level. Enterprise owners can set policy for all organizations in the enterprise account or allow organization owners to set the policy at the organization level. Organization owners cannot change settings enforced for your organization at the enterprise account level. If you have questions about a policy or setting for your organization, contact the owner of your enterprise account.
|
||||
|
||||
{% data reusables.gated-features.enterprise-accounts %}
|
||||
|
||||
{% data reusables.organizations.org-ownership-recommendation %} For more information, see "[Maintaining ownership continuity for your organization](/github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization)."
|
||||
|
||||
### Terms of service and data protection for organizations
|
||||
|
||||
An entity, such as a company, non-profit, or group, can agree to the Standard Terms of Service or the Corporate Terms of Service for their organization. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."
|
||||
|
||||
{% endif %}
|
||||
@@ -1,30 +0,0 @@
|
||||
---
|
||||
title: About SCIM
|
||||
intro: 'With System for Cross-domain Identity Management (SCIM), administrators can automate the exchange of user identity information between systems.'
|
||||
product: '{% data reusables.gated-features.saml-sso %}'
|
||||
redirect_from:
|
||||
- /articles/about-scim
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
If you use [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) in your organization, you can implement SCIM to add, manage, and remove organization members' access to {% data variables.product.product_name %}. For example, an administrator can deprovision an organization member using SCIM and automatically remove the member from the organization.
|
||||
|
||||
If you use SAML SSO without implementing SCIM, you won't have automatic deprovisioning. When organization members' sessions expire after their access is removed from the IdP, they aren't automatically removed from the organization. Authorized tokens grant access to the organization even after their sessions expire. To remove access, organization administrators can either manually remove the authorized token from the organization or automate its removal with SCIM.
|
||||
|
||||
These identity providers are compatible with the {% data variables.product.product_name %} SCIM API for organizations. For more information, see [SCIM](/rest/reference/scim) in the {% data variables.product.product_name %} API documentation.
|
||||
- Azure AD
|
||||
- Okta
|
||||
- OneLogin
|
||||
|
||||
{% data reusables.scim.enterprise-account-scim %} For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)."
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
|
||||
- "[Connecting your identity provider to your organization](/articles/connecting-your-identity-provider-to-your-organization)"
|
||||
- "[Enabling and testing SAML single sign-on for your organization](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)"
|
||||
- "[Viewing and managing a member's SAML access to your organization](/github/setting-up-and-managing-organizations-and-teams//viewing-and-managing-a-members-saml-access-to-your-organization)"
|
||||
@@ -1,46 +0,0 @@
|
||||
---
|
||||
title: About SSH certificate authorities
|
||||
intro: 'With an SSH certificate authority, your organization or enterprise account can provide SSH certificates that members can use to access your resources with Git.'
|
||||
product: '{% data reusables.gated-features.ssh-certificate-authorities %}'
|
||||
redirect_from:
|
||||
- /articles/about-ssh-certificate-authorities
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
An SSH certificate is a mechanism for one SSH key to sign another SSH key. If you use an SSH certificate authority (CA) to provide your organization members with signed SSH certificates, you can add the CA to your enterprise account or organization to allow organization members to use their certificates to access organization resources. For more information, see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)."
|
||||
|
||||
After you add an SSH CA to your organization or enterprise account, you can use the CA to sign client SSH certificates for organization members. Organization members can use the signed certificates to access your organization's repositories (and only your organization's repositories) with Git. You can require that members use SSH certificates to access organization resources.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Enforcing security settings in your enterprise account](/articles/enforcing-security-settings-in-your-enterprise-account#managing-your-enterprise-accounts-ssh-certificate-authorities)."{% endif %}
|
||||
|
||||
For example, you can build an internal system that issues a new certificate to your developers every morning. Each developer can use their daily certificate to work on your organization's repositories on {% data variables.product.product_name %}. At the end of the day, the certificate can automatically expire, protecting your repositories if the certificate is later compromised.
|
||||
|
||||
When you issue each certificate, you must include an extension that specifies which {% data variables.product.product_name %} user the certificate is for. For example, you can use OpenSSH's `ssh-keygen` command, replacing _KEY-IDENTITY_ with your key identity and _USERNAME_ with a {% data variables.product.product_name %} username.
|
||||
|
||||
```shell
|
||||
$ ssh-keygen -s ./ca-key -I <em>KEY-IDENTITY</em> -O extension:login@{% data variables.product.product_url %}=<em>USERNAME</em> ./user-key.pub
|
||||
```
|
||||
|
||||
To issue a certificate for someone who uses SSH to access multiple {% data variables.product.company_short %} products, you can include two login extensions to specify the username for each product. For example, the following command would issue a certificate for _USERNAME-1_ for the user's account for {% data variables.product.prodname_ghe_cloud %}, and _USERNAME-2_ for the user's account on {% data variables.product.prodname_ghe_managed %} or {% data variables.product.prodname_ghe_server %} at _HOSTNAME_.
|
||||
|
||||
```shell
|
||||
$ ssh-keygen -s ./ca-key -I <em>KEY-IDENTITY</em> -O extension:login@github.com=<em>USERNAME-1</em> extension:login@<em>HOSTNAME</em>=<em>USERNAME-2</em> ./user-key.pub
|
||||
```
|
||||
|
||||
You can restrict the IP addresses from which an organization member can access your organization's resources by using a `source-address` extension. The extension accepts a specific IP address or a range of IP addresses using CIDR notation. You can specify multiple addresses or ranges by separating the values with commas. For more information, see "[Classless Inter-Domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)" on Wikipedia.
|
||||
|
||||
```shell
|
||||
$ ssh-keygen -s ./ca-key -I <em>KEY-IDENTITY</em> -O extension:login@{% data variables.product.product_url %}=<em>USERNAME</em> -O source-address=<em>COMMA-SEPARATED-LIST-OF-IP-ADDRESSES-OR-RANGES</em> ./user-key.pub
|
||||
```
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
|
||||
Organization members can use their signed certificates for authentication even if you've enforced SAML single sign-on. Unless you make SSH certificates a requirement, organization members can continue to use other means of authentication to access your organization's resources with Git, including their username and password, personal access tokens, and their own SSH keys.
|
||||
|
||||
{% endif %}
|
||||
|
||||
To prevent authentication errors, organization members should use a special URL that includes the organization ID to clone repositories using signed certificates. Anyone with read access to the repository can find this URL on the repository page. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
|
||||
@@ -1,48 +0,0 @@
|
||||
---
|
||||
title: About team discussions
|
||||
intro: 'Your team can plan together, update one another, or talk about any topic you''d like in discussion posts on your team''s page in an organization.'
|
||||
redirect_from:
|
||||
- /articles/about-team-discussions
|
||||
- /github/building-a-strong-community/about-team-discussions
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- community
|
||||
---
|
||||
|
||||
{% data reusables.organizations.team-discussions-purpose %}
|
||||
|
||||
Any organization member can post on your team's page or participate in a public discussion. {% data reusables.organizations.team-discussions-permissions %}
|
||||
|
||||
|
||||
|
||||
You can link to any team discussion to reference it elsewhere. You can pin important posts to your team's page for quick reference later. For more information, see "[Pinning a team discussion](/github/setting-up-and-managing-organizations-and-teams/pinning-a-team-discussion)."
|
||||
|
||||
|
||||
|
||||
{% data reusables.organizations.team-discussions-default %} Owners can disable team discussions for the entire organization. For more information, see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)."
|
||||
|
||||
### Notifications for team discussions
|
||||
|
||||
When someone posts or replies to a public discussion on a team's page, members of the team and members of any child teams receive email or web notifications. When someone posts or replies to a private discussion on a team's page, only members of the team receive notifications.
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** Depending on your notification settings, you'll receive updates by email, the web notifications page on {% data variables.product.product_name %}, or both. For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications)" and "[About web notifications](/github/receiving-notifications-about-activity-on-github/about-web-notifications){% endif %}."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
By default, if your username is mentioned in a team discussion, you'll receive notifications for the post mentioning your username and any replies to that post. Also, by default, if you reply to a post, you will receive notifications for other replies to the post.
|
||||
|
||||
To turn off notifications for team discussions, you can unsubscribe to a specific discussion post or change your notification settings to unwatch or completely ignore a specific team's discussions. You can subscribe to notifications for a specific discussion post even if you're unwatching that team's discussions.
|
||||
|
||||
For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Subscribing to and unsubscribing from notifications](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}" and "[Nested teams](/articles/about-teams/#nested-teams)."
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[About conversations on {% data variables.product.prodname_dotcom %}](/articles/about-conversations-on-github)"
|
||||
- "[About teams](/articles/about-teams)"
|
||||
- "[Creating a team discussion](/github/setting-up-and-managing-organizations-and-teams/creating-a-team-discussion)"
|
||||
- "[Editing or deleting a team discussion](/github/setting-up-and-managing-organizations-and-teams/editing-or-deleting-a-team-discussion)"
|
||||
@@ -1,78 +0,0 @@
|
||||
---
|
||||
title: About teams
|
||||
intro: Teams are groups of organization members that reflect your company or group's structure with cascading access permissions and mentions.
|
||||
redirect_from:
|
||||
- /articles/about-teams
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
|
||||
|
||||
Organization owners and team maintainers can give teams admin, read, or write access to organization repositories. Organization members can send a notification to an entire team by mentioning the team's name. Organization members can also send a notification to an entire team by requesting a review from that team. Organization members can request reviews from specific teams with read access to the repository where the pull request is opened. Teams can be designated as owners of certain types or areas of code in a CODEOWNERS file.
|
||||
|
||||
For more information, see:
|
||||
- "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)"
|
||||
- "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)"
|
||||
- "[About code owners](/articles/about-code-owners/)"
|
||||
|
||||
|
||||
|
||||
{% if enterpriseServerVersions contains currentVersion %}
|
||||
|
||||
You can also use LDAP Sync to synchronize {% data variables.product.product_location %} team members and team roles against your established LDAP groups. This lets you establish role-based access control for users from your LDAP server instead of manually within {% data variables.product.product_location %}. For more information, see "[Enabling LDAP Sync](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.organizations.team-synchronization %}
|
||||
|
||||
### Team visibility
|
||||
|
||||
{% data reusables.organizations.types-of-team-visibility %}
|
||||
|
||||
### Team pages
|
||||
|
||||
Each team has its own page within an organization. On a team's page, you can view team members, child teams, and the team's repositories. Organization owners and team maintainers can access team settings and update the team's description and profile picture from the team's page.
|
||||
|
||||
Organization members can create and participate in discussions with the team. For more information, see "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)."
|
||||
|
||||
|
||||
|
||||
### Nested teams
|
||||
|
||||
You can reflect your group or company's hierarchy within your {% data variables.product.product_name %} organization with multiple levels of nested teams. A parent team can have multiple child teams, while each child team only has one parent team. You cannot nest secret teams.
|
||||
|
||||
Child teams inherit the parent's access permissions, simplifying permissions management for large groups. Members of child teams also receive notifications when the parent team is @mentioned, simplifying communication with multiple groups of people.
|
||||
|
||||
For example, if your team structure is Employees > Engineering > Application Engineering > Identity, granting Engineering write access to a repository means Application Engineering and Identity also get that access. If you @mention the Identity Team or any team at the bottom of the organization hierarchy, they're the only ones who will receive a notification.
|
||||
|
||||
|
||||
|
||||
To easily understand who shares a parent team's permissions and mentions, you can see all of the members of a parent team's child teams on the Members tab of the parent team's page. Members of a child team are not direct members of the parent team.
|
||||
|
||||
|
||||
|
||||
You can choose a parent when you create the team, or you can move a team in your organization's hierarchy later. For more information see, "[Moving a team in your organization’s hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy)."
|
||||
|
||||
{% data reusables.enterprise_user_management.ldap-sync-nested-teams %}
|
||||
|
||||
### Preparing to nest teams in your organization
|
||||
|
||||
If your organization already has existing teams, you should audit each team's repository access permissions before you nest teams above or below it. You should also consider the new structure you'd like to implement for your organization.
|
||||
|
||||
At the top of the team hierarchy, you should give parent teams repository access permissions that are safe for every member of the parent team and its child teams. As you move toward the bottom of the hierarchy, you can grant child teams additional, more granular access to more sensitive repositories.
|
||||
|
||||
1. Remove all members from existing teams
|
||||
2. Audit and adjust each team's repository access permissions and give each team a parent
|
||||
3. Create any new teams you'd like to, choose a parent for each new team, and give them repository access
|
||||
4. Add people directly to teams
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[Creating a team](/articles/creating-a-team)"
|
||||
- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)"
|
||||
@@ -1,25 +0,0 @@
|
||||
---
|
||||
title: About two-factor authentication and SAML single sign-on
|
||||
intro: Organizations administrators can enable both SAML single sign-on and two-factor authentication to add additional authentication measures for their organization members.
|
||||
product: '{% data reusables.gated-features.saml-sso %}'
|
||||
redirect_from:
|
||||
- /articles/about-two-factor-authentication-and-saml-single-sign-on
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
Two-factor authentication (2FA) provides basic authentication for organization members. By enabling 2FA, organization administrators limit the likelihood that a member's {% data variables.product.product_name %} account could be compromised. For more information on 2FA, see "[About two-factor authentication](/articles/about-two-factor-authentication)."
|
||||
|
||||
To add additional authentication measures, organization administrators can also [enable SAML single sign-on (SSO)](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) so that organization members must use single sign-on to access an organization. For more information on SAML SSO, see "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)."
|
||||
|
||||
If both 2FA and SAML SSO are enabled, organization members must do the following:
|
||||
- Use 2FA to log in to their {% data variables.product.product_name %} account
|
||||
- Use single sign-on to access the organization
|
||||
- Use an authorized token for API or Git access and use single sign-on to authorize the token
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)"
|
||||
@@ -1,48 +0,0 @@
|
||||
---
|
||||
title: About your organization dashboard
|
||||
intro: 'As an organization member, you can visit your organization''s dashboard throughout the day to stay updated on recent activity and keep track of issues and pull requests you''re working on or following in the organization.'
|
||||
redirect_from:
|
||||
- /articles/about-your-organization-dashboard
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
### Accessing your organization dashboard
|
||||
|
||||
{% data reusables.dashboard.access-org-dashboard %}
|
||||
|
||||
### Finding your recent activity
|
||||
|
||||
In the "Recent activity" section of your news feed, you can quickly find and follow up with recently updated issues and pull requests in your organization.
|
||||
|
||||
{% data reusables.dashboard.recent-activity-qualifying-events %}
|
||||
|
||||
### Finding repositories in your organization
|
||||
|
||||
In the left sidebar of your dashboard, you can access your organization's top repositories you're active in.
|
||||
|
||||
|
||||
|
||||
### Staying updated with activity from the organization
|
||||
|
||||
In the "All activity" section of your news feed, you can view updates from other teams and repositories in your organization.
|
||||
|
||||
The "All activity" section shows all recent activity in the organization, including activity in repositories you're not subscribed to and of people you're not following. For more information, see {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Watching and unwatching repositories](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}" and "[Following people](/articles/following-people)."
|
||||
|
||||
For instance, the organization news feed shows updates when someone in the organization:
|
||||
- Creates a new branch.
|
||||
- Comments on an issue or pull request.
|
||||
- Submits a pull request review comment.
|
||||
- Forks a repository.
|
||||
- Creates a wiki page.
|
||||
- Pushes commits.{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
|
||||
- Creates a public repository.{% endif %}
|
||||
|
||||
### Further information
|
||||
|
||||
- "[About your personal dashboard](/articles/about-your-personal-dashboard)"
|
||||
@@ -1,27 +0,0 @@
|
||||
---
|
||||
title: About your organization’s news feed
|
||||
intro: You can use your organization's news feed to keep up with recent activity on repositories owned by that organization.
|
||||
redirect_from:
|
||||
- /articles/news-feed/
|
||||
- /articles/about-your-organization-s-news-feed
|
||||
- /articles/about-your-organizations-news-feed
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
An organization's news feed shows other people's activity on repositories owned by that organization. You can use your organization's news feed to see when someone opens, closes, or merges an issue or pull request, creates or deletes a branch, creates a tag or release, comments on an issue, pull request, or commit, or pushes new commits to {% data variables.product.product_name %}.
|
||||
|
||||
### Accessing your organization's news feed
|
||||
|
||||
1. {% data variables.product.signin_link %} to your {% data variables.product.product_name %} account.
|
||||
2. Open your {% data reusables.user_settings.personal_dashboard %}.
|
||||
3. Click the account context switcher in the upper-left corner of the page.
|
||||
|
||||
4. Select an organization from the drop-down menu.{% if currentVersion == "free-pro-team@latest" %}
|
||||
{% else %}
|
||||
{% endif %}
|
||||
@@ -1,33 +0,0 @@
|
||||
---
|
||||
title: Accessing your organization if your identity provider is unavailable
|
||||
intro: 'Organization administrators can sign into {% data variables.product.product_name %} even if their identity provider is unavailable by bypassing single sign-on and using their recovery codes.'
|
||||
product: '{% data reusables.gated-features.saml-sso %}'
|
||||
redirect_from:
|
||||
- /articles/accessing-your-organization-if-your-identity-provider-is-unavailable
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
Organization administrators can use [one of their downloaded or saved recovery codes](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes) to bypass single sign-on. You may have saved these to a password manager, such as [LastPass](https://lastpass.com/), [1Password](https://1password.com/), or [Keeper](https://keepersecurity.com/).
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** You can only use recovery codes once and you must use them in consecutive order. Recovery codes grant access for 24 hours.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. At the bottom of the single sign-on dialog, click **Use a recovery code** to bypass single sign-on.
|
||||
|
||||
2. In the "Recovery Code" field, type your recovery code.
|
||||
|
||||
3. Click **Verify**.
|
||||
|
||||
|
||||
After you've used a recovery code, make sure to note that it's no longer valid. You will not be able to reuse the recovery code.
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[About identity and access management with SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
|
||||
@@ -1,32 +0,0 @@
|
||||
---
|
||||
title: Accessing your organization's settings
|
||||
redirect_from:
|
||||
- /articles/who-can-access-organization-billing-information-and-account-settings/
|
||||
- /articles/managing-the-organization-s-settings/
|
||||
- /articles/who-can-see-billing-information-account-settings/
|
||||
- /articles/who-can-see-billing-information-and-access-account-settings/
|
||||
- /articles/managing-an-organization-s-settings/
|
||||
- /articles/accessing-your-organization-s-settings
|
||||
- /articles/accessing-your-organizations-settings
|
||||
intro: 'The organization account settings page provides several ways to manage the account, such as billing, team membership, and repository settings.'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** Only organization owners and billing managers can see and change the billing information and account settings for an organization. {% data reusables.organizations.new-org-permissions-more-info %}
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
@@ -1,58 +0,0 @@
|
||||
---
|
||||
title: Adding a billing manager to your organization
|
||||
intro: 'A *billing manager* is a user who manages the billing settings for your organization, such as updating payment information. This is a great option if regular members of your organization don''t typically have access to billing resources.'
|
||||
redirect_from:
|
||||
- /articles/adding-a-billing-manager-to-your-organization
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
- billing
|
||||
---
|
||||
|
||||
Members of your organization's Owners team can give *billing manager* permissions to people. Once a person accepts their invitation to become a billing manager for your organization, they can invite additional people to be billing managers.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Billing managers do not use paid licenses in your organization's subscription.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Permissions for billing managers
|
||||
|
||||
Billing managers can:
|
||||
|
||||
- Upgrade or downgrade the account
|
||||
- Add, update, or remove payment methods
|
||||
- View payment history
|
||||
- Download receipts
|
||||
- View, invite, and remove billing managers
|
||||
|
||||
In addition, all billing managers will receive billing receipts by email on the organization's billing date.
|
||||
|
||||
Billing managers **are not** able to:
|
||||
|
||||
- Create or access repositories in your organizations
|
||||
- See private members of your organization
|
||||
- Be seen in the list of organization members
|
||||
- Purchase, edit, or cancel subscriptions for {% data variables.product.prodname_marketplace %} apps
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** If your organization [requires members, billing managers, and outside collaborators to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization), the user must enable two-factor authentication before they can accept your invitation to become a billing manager for the organization.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
### Inviting a billing manager
|
||||
|
||||
The invited person will receive an invitation email asking them to become a billing manager for your organization. Once the invited person clicks the accept link in their invitation email, they will automatically be added to the organization as a billing manager. If they don't already have a GitHub account, they will be directed to sign up for one, and they will be automatically added to the organization as a billing manager after they create an account.
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.billing %}
|
||||
5. Next to Billing managers, click **Add a billing manager**.
|
||||
|
||||
6. Type the username or email address of the person you want to add and click **Send invitation**.
|
||||
|
||||
@@ -1,27 +0,0 @@
|
||||
---
|
||||
title: Adding an outside collaborator to a project board in your organization
|
||||
intro: 'As an organization owner or project board admin, you can add an outside collaborator and customize their permissions to a project board.'
|
||||
redirect_from:
|
||||
- /articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
An outside collaborator is a person who isn't explicitly a member of your organization, but who has permissions to a project board in your organization.
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.organization-wide-project %}
|
||||
{% data reusables.project-management.select-project %}
|
||||
{% data reusables.project-management.click-menu %}
|
||||
{% data reusables.project-management.access-collaboration-settings %}
|
||||
{% data reusables.project-management.collaborator-option %}
|
||||
9. Under "Search by username, full name or email address", type the outside collaborator's name, username, or {% data variables.product.prodname_dotcom %} email.
|
||||
|
||||
{% data reusables.project-management.add-collaborator %}
|
||||
{% data reusables.project-management.collaborator-permissions %}
|
||||
@@ -1,42 +0,0 @@
|
||||
---
|
||||
title: Adding GitHub App managers in your organization
|
||||
intro: 'Organization owners can grant users the ability to manage some or all {% data variables.product.prodname_github_app %}s owned by the organization.'
|
||||
redirect_from:
|
||||
- /articles/adding-github-app-managers-in-your-organization
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
For more information about {% data variables.product.prodname_github_app %} manager permissions, see "[Permission levels for an organization](/articles/permission-levels-for-an-organization#github-app-managers)."
|
||||
|
||||
### Giving someone the ability to manage all {% data variables.product.prodname_github_app %}s owned by the organization
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.github-apps-settings-sidebar %}
|
||||
1. Under "Management", type the username of the person you want to designate as a {% data variables.product.prodname_github_app %} manager in the organization, and click **Grant**.
|
||||
|
||||
|
||||
### Giving someone the ability to manage an individual {% data variables.product.prodname_github_app %}
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.github-apps-settings-sidebar %}
|
||||
1. Under "{% data variables.product.prodname_github_app %}s", click on the avatar of the app you'd like to add a {% data variables.product.prodname_github_app %} manager for.
|
||||
|
||||
{% data reusables.organizations.app-managers-settings-sidebar %}
|
||||
1. Under "App managers", type the username of the person you want to designate as a GitHub App manager for the app, and click **Grant**.
|
||||
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
### Further reading
|
||||
|
||||
- "[About {% data variables.product.prodname_dotcom %} Marketplace](/articles/about-github-marketplace/)"
|
||||
{% endif %}
|
||||
@@ -1,32 +0,0 @@
|
||||
---
|
||||
title: Adding organization members to a team
|
||||
intro: 'People with owner or team maintainer permissions can add organization members to teams. People with owner permissions can also {% if currentVersion == "free-pro-team@latest" %}invite non-members to join{% else %}add non-members to{% endif %} a team and the organization.'
|
||||
redirect_from:
|
||||
- /articles/adding-organization-members-to-a-team-early-access-program/
|
||||
- /articles/adding-organization-members-to-a-team
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
{% data reusables.organizations.team-synchronization %}
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.specific_team %}
|
||||
{% data reusables.organizations.team_members_tab %}
|
||||
6. Above the list of team members, click **Add a member**.
|
||||
|
||||
{% data reusables.organizations.invite_to_team %}
|
||||
{% data reusables.organizations.review-team-repository-access %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}{% data reusables.organizations.cancel_org_invite %}{% endif %}
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[About teams](/articles/about-teams)"
|
||||
- "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)"
|
||||
@@ -1,46 +0,0 @@
|
||||
---
|
||||
title: Adding outside collaborators to repositories in your organization
|
||||
intro: 'An *outside collaborator* is a person who isn''t explicitly a member of your organization, but who has Read, Write, or Admin permissions to one or more repositories in your organization.'
|
||||
redirect_from:
|
||||
- /articles/adding-outside-collaborators-to-repositories-in-your-organization
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
{% data reusables.organizations.owners-and-admins-can %} add outside collaborators to a repository, unless an organization owner has restricted the ability to invite collaborators. For more information, see "[Setting permissions for adding outside collaborators](/articles/setting-permissions-for-adding-outside-collaborators)."
|
||||
|
||||
{% data reusables.organizations.outside-collaborators-use-seats %}
|
||||
|
||||
{% if currentVersion != "github-ae@latest" %}
|
||||
If your organization [requires members and outside collaborators to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization), they must enable two-factor authentication before they can accept your invitation to collaborate on an organization repository.
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.organizations.outside_collaborator_forks %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
{% data reusables.repositories.navigate-to-manage-access %}
|
||||
{% data reusables.organizations.invite-teams-or-people %}
|
||||
5. In the search field, start typing the name of person you want to invite, then click a name in the list of matches.
|
||||
|
||||
6. Under "Choose a role", select the permissions to grant to the person, then click **Add NAME to REPOSITORY**.
|
||||
|
||||
{% else %}
|
||||
5. In the left sidebar, click **Collaborators & teams**.
|
||||
|
||||
6. Under "Collaborators", type the name of the person you'd like to give access to the repository, then click **Add collaborator**.
|
||||
|
||||
7. Next to the new collaborator's name, choose the appropriate permission level: *Write*, *Read*, or *Admin*.
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)"
|
||||
- "[Removing an outside collaborator from an organization repository](/articles/removing-an-outside-collaborator-from-an-organization-repository)"
|
||||
@@ -1,28 +0,0 @@
|
||||
---
|
||||
title: Adding people to your organization
|
||||
intro: 'You can make anyone a member of your organization using their {% data variables.product.product_name %} username or email address.'
|
||||
redirect_from:
|
||||
- /articles/adding-people-to-your-organization
|
||||
versions:
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
permissions: 'Organization owners can add people to an organization.'
|
||||
---
|
||||
|
||||
{% if currentVersion != "github-ae@latest" %}
|
||||
If your organization [requires members to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization), users must [enable two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) before you can add them to the organization.
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.people %}
|
||||
{% data reusables.organizations.invite_member_from_people_tab %}
|
||||
{% data reusables.organizations.invite_to_org %}
|
||||
{% data reusables.organizations.choose-to-restore-privileges %}
|
||||
{% data reusables.organizations.choose-user-role %}
|
||||
{% data reusables.organizations.choose-user-license %}
|
||||
{% data reusables.organizations.add-user-to-teams %}
|
||||
{% data reusables.organizations.send-invitation %}
|
||||
|
||||
### Further reading
|
||||
- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)"
|
||||
@@ -1,25 +0,0 @@
|
||||
---
|
||||
title: Allowing people to delete issues in your organization
|
||||
intro: Organization owners can allow certain people to delete issues in repositories owned by your organization.
|
||||
redirect_from:
|
||||
- /articles/allowing-people-to-delete-issues-in-your-organization
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
By default, issues cannot be deleted in an organization's repositories. An organization owner must enable this feature for all of the organization's repositories first.
|
||||
|
||||
Once enabled, organization owners and people with admin permissions in an organization-owned repository can delete issues. People with admin permissions in a repository include organization members and outside collaborators with admin privileges. For more information, see "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization/)" and "[Deleting an issue](/articles/deleting-an-issue)."
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.member-privileges %}
|
||||
5. Under "Issue deletion", select **Allow members to delete issues for this organization**.
|
||||
|
||||
6. Click **Save**.
|
||||
@@ -1,26 +0,0 @@
|
||||
---
|
||||
title: Approving OAuth Apps for your organization
|
||||
intro: 'When an organization member requests {% data variables.product.prodname_oauth_app %} access to organization resources, organization owners can approve or deny the request.'
|
||||
redirect_from:
|
||||
- /articles/approving-third-party-applications-for-your-organization/
|
||||
- /articles/approving-oauth-apps-for-your-organization
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
When {% data variables.product.prodname_oauth_app %} access restrictions are enabled, organization members must [request approval](/articles/requesting-organization-approval-for-oauth-apps) from an organization owner before they can authorize an {% data variables.product.prodname_oauth_app %} that has access to the organization's resources.
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.oauth_app_access %}
|
||||
5. Next to the application you'd like to approve, click **Review**.
|
||||
|
||||
6. After you review the information about the requested application, click **Grant access**.
|
||||
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)"
|
||||
@@ -1,20 +0,0 @@
|
||||
---
|
||||
title: Can I create accounts for people in my organization?
|
||||
redirect_from:
|
||||
- /articles/can-i-create-accounts-for-those-in-my-organization/
|
||||
- /articles/can-i-create-accounts-for-people-in-my-organization
|
||||
intro: 'While you can add users to an organization you''ve created, you can''t create personal user accounts on behalf of another person.'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
Because you access an organization by logging in to a personal account, each of your team members needs a personal account. Once you have user names for each person you'd like to add to your organization, you can add them to teams.
|
||||
|
||||
### Adding users to your organization
|
||||
|
||||
1. Provide each person instructions to [create a personal account](/articles/signing-up-for-a-new-github-account).
|
||||
2. Ask for the username of each person you want to give organization membership to.
|
||||
3. [Invite the new personal accounts to join](/articles/inviting-users-to-join-your-organization) your organization. Use [organization roles](/articles/permission-levels-for-an-organization) and [repository permissions](/articles/repository-permission-levels-for-an-organization) to limit the access of each account.
|
||||
@@ -1,25 +0,0 @@
|
||||
---
|
||||
title: Canceling an invitation to become an outside collaborator in your organization
|
||||
intro: You can cancel all invitations for a person to become an outside collaborator on repositories owned by your organization.
|
||||
permissions: Organization owners can cancel an invitation to become an outside collaborator in the organization.
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
You can view a list of all people with pending invitations to become an outside collaborator on any repository owned by your organization.
|
||||
|
||||
For each pending collaborator, you can cancel all invitations to join organization repositories at the same time.
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.people %}
|
||||
{% data reusables.organizations.people_tab_outside_collaborators %}
|
||||
5. Click **X pending collaborators**.
|
||||
|
||||
6. To the right of the person you want to cancel invitations for, click **Cancel invitations**.
|
||||
|
||||
7. Click **Cancel invitations for pending collaborators**.
|
||||
|
||||
@@ -1,32 +0,0 @@
|
||||
---
|
||||
title: Canceling or editing an invitation to join your organization
|
||||
intro: Organization owners can edit or cancel an invitation to become a member of your organization any time before the user accepts.
|
||||
redirect_from:
|
||||
- /articles/canceling-or-editing-an-invitation-to-join-your-organization
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.people %}
|
||||
4. On the People tab, click **Pending invitation**.
|
||||
|
||||
5. Next to the username or email address of the person whose invitation you'd like to edit or cancel, click **Edit invitation**.
|
||||
|
||||
|
||||
You may need to click **View all invitations** at the bottom of the window to find the person you're looking for.
|
||||
6. Decide whether to edit or cancel the user's invitation to join your organization.
|
||||
|
||||
- To edit the user's invitation, select a different role or team, then click **Update invitation**.
|
||||
- To cancel the user's invitation to join your organization, click **Cancel invitation**.
|
||||
|
||||
### Further reading
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
- "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)"
|
||||
{% endif %}
|
||||
- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)"
|
||||
@@ -1,31 +0,0 @@
|
||||
---
|
||||
title: Changing team visibility
|
||||
intro: Team maintainers and organization owners can determine whether a team is *visible* or *secret*.
|
||||
redirect_from:
|
||||
- /articles/changing-team-visibility
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
{% data reusables.organizations.types-of-team-visibility %}
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** If a team has [child or parent teams](/articles/about-teams), you cannot make it a secret team.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.teams %}
|
||||
3. Select the team or teams whose visibility you'd like to change.
|
||||
|
||||
4. Above the list of teams, use the drop-down menu and click **Change visibility**.
|
||||
|
||||
5. Choose whether to make the team or teams visible or secret, then click **Change visibility**.
|
||||
|
||||
@@ -1,24 +0,0 @@
|
||||
---
|
||||
title: Changing the visibility of your organization's dependency insights
|
||||
intro: You can allow all organization members to view dependency insights for your organization or limit viewing to organization owners.
|
||||
product: '{% data reusables.gated-features.org-insights %}'
|
||||
redirect_from:
|
||||
- /articles/changing-the-visibility-of-your-organizations-dependency-insights
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
Organization owners can set limitations for viewing organization dependency insights. All members of an organization can view organization dependency insights by default.
|
||||
|
||||
Enterprise owners can set limitations for viewing organization dependency insights on all organizations in your enterprise account. For more information, see "[Enforcing a policy on dependency insights in your enterprise account](/articles/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account)."
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.member-privileges %}
|
||||
5. Under "Member organization permissions", select or unselect **Allow members to view dependency insights**.
|
||||
|
||||
6. Click **Save**.
|
||||
@@ -1,16 +0,0 @@
|
||||
---
|
||||
title: Collaborating with groups in organizations
|
||||
intro: Groups of people can collaborate across many projects at the same time in organization accounts.
|
||||
redirect_from:
|
||||
- /articles/creating-a-new-organization-account/
|
||||
- /articles/collaborating-with-groups-in-organizations
|
||||
mapTopic: true
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
@@ -1,15 +0,0 @@
|
||||
---
|
||||
title: Collaborating with your team
|
||||
intro: 'Within an organization, your team can work together across projects using team discussions.'
|
||||
mapTopic: true
|
||||
redirect_from:
|
||||
- /articles/collaborating-with-your-team
|
||||
- /github/building-a-strong-community/collaborating-with-your-team
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- community
|
||||
---
|
||||
|
||||
@@ -1,84 +0,0 @@
|
||||
---
|
||||
title: Configuring SAML single sign-on and SCIM using Okta
|
||||
intro: 'You can use Security Assertion Markup Language (SAML) single sign-on (SSO) and System for Cross-domain Identity Management (SCIM) with Okta to automatically manage access to your organization on {% data variables.product.prodname_dotcom %}.'
|
||||
product: '{% data reusables.gated-features.saml-sso %}'
|
||||
permissions: Organization owners can configure SAML SSO and SCIM using Okta for an organization.
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
### About SAML and SCIM with Okta
|
||||
|
||||
You can control access to your {% data variables.product.prodname_dotcom %} organization and other web applications from one central interface by configuring the organization to use SAML SSO and SCIM with Okta, an Identity Provider (IdP).
|
||||
|
||||
SAML SSO controls and secures access to organization resources like repositories, issues, and pull requests. SCIM automatically adds, manages, and removes members' access to your {% data variables.product.prodname_dotcom %} organization when you make changes in Okta. For more information, see "[About identity and access management with SAML single sign-on](/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on)" and "[About SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)."
|
||||
|
||||
After you enable SCIM, the following provisioning features are available for any users that you assign your {% data variables.product.prodname_ghe_cloud %} application to in Okta.
|
||||
|
||||
| Feature | Description |
|
||||
| --- | --- |
|
||||
| Push New Users | When you create a new user in Okta, the user will receive an email to join your {% data variables.product.prodname_dotcom %} organization. |
|
||||
| Push User Deactivation | When you deactivate a user in Okta, Okta will remove the user from your {% data variables.product.prodname_dotcom %} organization. |
|
||||
| Push Profile Updates | When you update a user's profile in Okta, Okta will update the metadata for the user's membership in your {% data variables.product.prodname_dotcom %} organization. |
|
||||
| Reactivate Users | When you reactivate a user in Okta, Okta will send an email invitation for the user to rejoin your {% data variables.product.prodname_dotcom %} organization. |
|
||||
|
||||
### Prerequisites
|
||||
|
||||
{% data reusables.saml.use-classic-ui %}
|
||||
|
||||
### Adding the {% data variables.product.prodname_ghe_cloud %} application in Okta
|
||||
|
||||
{% data reusables.saml.okta-dashboard-click-applications %}
|
||||
{% data reusables.saml.add-okta-application %}
|
||||
{% data reusables.saml.search-ghec-okta %}
|
||||
4. To the right of "Github Enterprise Cloud - Organization", click **Add**.
|
||||
|
||||
|
||||
5. In the **GitHub Organization** field, type the name of your {% data variables.product.prodname_dotcom %} organization. For example, if your organization's URL is https://github.com/octo-org, the organization name would be `octo-org`.
|
||||
|
||||
|
||||
6. Click **Done**.
|
||||
|
||||
### Enabling and testing SAML SSO
|
||||
|
||||
{% data reusables.saml.okta-dashboard-click-applications %}
|
||||
{% data reusables.saml.okta-applications-click-ghec-application-label %}
|
||||
{% data reusables.saml.assign-yourself-to-okta %}
|
||||
{% data reusables.saml.okta-sign-on-tab %}
|
||||
{% data reusables.saml.okta-view-setup-instructions %}
|
||||
6. Enable and test SAML SSO on {% data variables.product.prodname_dotcom %} using the sign on URL, issuer URL, and public certificates from the "How to Configure SAML 2.0" guide. For more information, see "[Enabling and testing SAML single sign-on for your organization](/github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization)."
|
||||
|
||||
### Configuring access provisioning with SCIM in Okta
|
||||
|
||||
{% data reusables.saml.okta-dashboard-click-applications %}
|
||||
{% data reusables.saml.okta-applications-click-ghec-application-label %}
|
||||
{% data reusables.saml.okta-provisioning-tab %}
|
||||
{% data reusables.saml.okta-configure-api-integration %}
|
||||
{% data reusables.saml.okta-enable-api-integration %}
|
||||
|
||||
|
||||
6. Click **Authenticate with Github Enterprise Cloud - Organization**.
|
||||
|
||||
|
||||
7. To the right of your organization's name, click **Grant**.
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: If you don't see your organization in the list, go to `https://github.com/orgs/ORGANIZATION-NAME/sso` in your browser and authenticate with your organization via SAML SSO using your administrator account on the IdP. For example, if your organization's name is `octo-org`, the URL would be `https://github.com/orgs/octo-org/sso`. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."
|
||||
|
||||
{% endnote %}
|
||||
1. Click **Authorize OktaOAN**.
|
||||
|
||||
{% data reusables.saml.okta-save-provisioning %}
|
||||
{% data reusables.saml.okta-edit-provisioning %}
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[Configuring SAML single sign-on and SCIM for your enterprise account using Okta](/github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta)"
|
||||
- "[Managing team synchronization for your organization](/github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization#enabling-team-synchronization-for-okta)"
|
||||
- [Understanding SAML](https://developer.okta.com/docs/concepts/saml/) in the Okta documentation
|
||||
- [Understanding SCIM](https://developer.okta.com/docs/concepts/scim/) in the Okta documentation
|
||||
@@ -1,20 +0,0 @@
|
||||
---
|
||||
title: Configuring the retention period for GitHub Actions artifacts and logs in your organization
|
||||
intro: 'You can configure the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your organization.'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.23'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
{% data reusables.actions.about-artifact-log-retention %}
|
||||
|
||||
## Setting the retention period for an organization
|
||||
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.settings-sidebar-actions %}
|
||||
{% data reusables.github-actions.change-retention-period-for-artifacts-logs %}
|
||||
@@ -1,33 +0,0 @@
|
||||
---
|
||||
title: Connecting your identity provider to your organization
|
||||
intro: 'To use SAML single sign-on and SCIM, you must connect your identity provider to your {% data variables.product.product_name %} organization.'
|
||||
product: '{% data reusables.gated-features.saml-sso %}'
|
||||
redirect_from:
|
||||
- /articles/connecting-your-identity-provider-to-your-organization
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
Before [enabling SAML SSO](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) in your {% data variables.product.product_name %} organization, you'll need to connect your identity provider (IdP) to your organization.
|
||||
|
||||
You can find the SAML and SCIM implementation details for your IdP in their documentation:
|
||||
- Active Directory Federation Services (AD FS) [SAML](https://docs.microsoft.com/windows-server/identity/active-directory-federation-services)
|
||||
- Azure Active Directory (Azure AD) [SAML](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-tutorial) and [SCIM](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-provisioning-tutorial)
|
||||
- Okta [SAML](http://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-Github-com.html) and [SCIM](http://developer.okta.com/standards/SCIM/)
|
||||
- OneLogin [SAML](https://onelogin.service-now.com/support?id=kb_article&sys_id=2929ddcfdbdc5700d5505eea4b9619c6) and [SCIM](https://onelogin.service-now.com/support?id=kb_article&sys_id=5aa91d03db109700d5505eea4b96197e)
|
||||
- PingOne [SAML](https://support.pingidentity.com/s/marketplace-integration/a7i1W0000004ID3QAM/github-connector)
|
||||
- Shibboleth [SAML](https://wiki.shibboleth.net/confluence/display/IDP30/Home)
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data variables.product.product_name %} supported identity providers for SCIM are Azure AD, Okta, and OneLogin. For more information about SCIM, see "[About SCIM](/articles/about-scim)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
|
||||
- "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)"
|
||||
@@ -1,31 +0,0 @@
|
||||
---
|
||||
title: Converting an admin team to improved organization permissions
|
||||
intro: 'If your organization was created after September 2015, your organization has improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved permissions model. Members of legacy admin teams automatically retain the ability to create repositories until those teams are migrated to the improved organization permissions model.'
|
||||
redirect_from:
|
||||
- /articles/converting-your-previous-admin-team-to-the-improved-organization-permissions/
|
||||
- /articles/converting-an-admin-team-to-improved-organization-permissions
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
You can remove the ability for members of legacy admin teams to create repositories by creating a new team for these members, ensuring that the team has necessary access to the organization's repositories, then deleting the legacy admin team.
|
||||
|
||||
For more information, see "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization/)."
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warnings:**
|
||||
- If there are members of your legacy Admin team who are not members of other teams, deleting the team will remove those members from the organization. Before deleting the team, ensure members are already direct members of the organization, or have collaborator access to necessary repositories.
|
||||
- To prevent the loss of private forks made by members of the legacy Admin team, you must follow steps 1-3 below before deleting the legacy Admin team.
|
||||
- Because "admin" is a term for organization members with specific [access to certain repositories](/articles/repository-permission-levels-for-an-organization) in the organization, we recommend you avoid that term in any team name you decide on.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
1. [Create a new team](/articles/creating-a-team).
|
||||
2. [Add each of the members](/articles/adding-organization-members-to-a-team) of your legacy admin team to the new team.
|
||||
3. [Give the new team equivalent access](/articles/managing-team-access-to-an-organization-repository) to each of the repositories the legacy team could access.
|
||||
4. [Delete the legacy admin team](/articles/deleting-a-team).
|
||||
@@ -1,32 +0,0 @@
|
||||
---
|
||||
title: Converting an organization into a user
|
||||
intro: 'It''s not possible to convert an organization into a personal user account, but you can create a new user account and transfer the organization''s repositories to it.'
|
||||
redirect_from:
|
||||
- /articles/converting-an-organization-into-a-user
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
|
||||
1. [Sign up](/articles/signing-up-for-a-new-github-account) for a new GitHub user account.
|
||||
2. [Have the user's role changed to an owner](/articles/changing-a-person-s-role-to-owner).
|
||||
3. {% data variables.product.signin_link %} to the new user account.
|
||||
4. [Transfer each organization repository](/articles/how-to-transfer-a-repository) to the new user account.
|
||||
5. [Delete the organization](/articles/deleting-an-organization-account).
|
||||
6. [Rename the user](/articles/changing-your-github-username) to the organization's name.
|
||||
|
||||
{% else %}
|
||||
|
||||
1. Sign up for a new GitHub Enterprise user account.
|
||||
2. [Have the user's role changed to an owner](/articles/changing-a-person-s-role-to-owner).
|
||||
3. {% data variables.product.signin_link %} to the new user account.
|
||||
4. [Transfer each organization repository](/articles/how-to-transfer-a-repository) to the new user account.
|
||||
5. [Delete the organization](/articles/deleting-an-organization-account).
|
||||
6. [Rename the user](/articles/changing-your-github-username) to the organization's name.
|
||||
|
||||
{% endif %}
|
||||
@@ -1,46 +0,0 @@
|
||||
---
|
||||
title: Converting an organization member to an outside collaborator
|
||||
intro: 'If a current member of your organization only needs access to certain repositories, such as consultants or temporary employees, you can convert them to an *outside collaborator*.'
|
||||
redirect_from:
|
||||
- /articles/converting-an-organization-member-to-an-outside-collaborator
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
{% data reusables.organizations.owners-and-admins-can %} convert organization members into outside collaborators.
|
||||
|
||||
{% data reusables.organizations.outside-collaborators-use-seats %} {% data reusables.organizations.outside_collaborator_forks %}
|
||||
|
||||
After converting an organization member to an outside collaborator, they'll only have access to the repositories that their current team membership allows. The person will no longer be an explicit member of the organization, and will no longer be able to:
|
||||
|
||||
- Create teams
|
||||
- See all organization members and teams
|
||||
- @mention any visible team
|
||||
- Be a team maintainer
|
||||
|
||||
For more information, see "[Permission levels for an organization](/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization)."
|
||||
|
||||
We recommend reviewing the organization member's access to repositories to ensure their access is as you expect. For more information, see "[Managing an individual's access to an organization repository](/articles/managing-an-individual-s-access-to-an-organization-repository)."
|
||||
|
||||
When you convert an organization member to an outside collaborator, their privileges as organization members are saved for three months so that you can restore their membership privileges if you{% if currentVersion == "free-pro-team@latest" %} invite them to rejoin{% else %} add them back to{% endif %} your organization within that time frame. For more information, see "[Reinstating a former member of your organization](/articles/reinstating-a-former-member-of-your-organization)."
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.people %}
|
||||
4. Select the person or people you'd like to convert to outside collaborators.
|
||||
|
||||
5. Above the list of members, use the drop-down menu and click **Convert to outside collaborator**.
|
||||
|
||||
6. Read the information about converting members to outside collaborators, then click **Convert to outside collaborator**.
|
||||
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[Adding outside collaborators to repositories in your organization](/articles/adding-outside-collaborators-to-repositories-in-your-organization)"
|
||||
- "[Removing an outside collaborator from an organization repository](/articles/removing-an-outside-collaborator-from-an-organization-repository)"
|
||||
- "[Converting an outside collaborator to an organization member](/articles/converting-an-outside-collaborator-to-an-organization-member)"
|
||||
@@ -1,39 +0,0 @@
|
||||
---
|
||||
title: Converting an outside collaborator to an organization member
|
||||
intro: 'If you would like to give an outside collaborator on your organization''s repositories broader permissions within your organization, you can {% if currentVersion == "free-pro-team@latest" %}invite them to become a member of{% else %}make them a member of{% endif %} the organization.'
|
||||
redirect_from:
|
||||
- /articles/converting-an-outside-collaborator-to-an-organization-member
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
permissions: 'Organization owners can {% if currentVersion == "free-pro-team@latest" %}invite users to join{% else %}add users to{% endif %} an organization.'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
If your organization is on a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." {% data reusables.organizations.org-invite-expiration %}{% endif %}
|
||||
|
||||
{% if currentVersion != "github-ae@latest" %}
|
||||
If your organization [requires members to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization), users {% if currentVersion == "free-pro-team@latest" %}you invite must [enable two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) before they can accept the invitation.{% else %}must [enable two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) before you can add them to the organization.{% endif %}
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.people %}
|
||||
{% data reusables.organizations.people_tab_outside_collaborators %}
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
5. To the right of the name of the outside collaborator you want to become a member, use the {% octicon "gear" aria-label="The gear icon" %} drop-down menu and click **Invite to organization**.
|
||||
{% else %}
|
||||
5. To the right of the name of the outside collaborator you want to become a member, click **Invite to organization**.
|
||||
{% endif %}
|
||||
{% data reusables.organizations.choose-to-restore-privileges %}
|
||||
{% data reusables.organizations.choose-user-role-send-invitation %}
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
{% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %}
|
||||
{% endif %}
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)"
|
||||
@@ -1,54 +0,0 @@
|
||||
---
|
||||
title: Converting an Owners team to improved organization permissions
|
||||
intro: 'If your organization was created after September 2015, your organization has improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved permissions model. The "Owner" is now an administrative role given to individual members of your organization. Members of your legacy Owners team are automatically given owner privileges.'
|
||||
redirect_from:
|
||||
- /articles/converting-your-previous-owners-team-to-the-improved-organization-permissions-early-access-program/
|
||||
- /articles/converting-your-previous-owners-team-to-the-improved-organization-permissions/
|
||||
- /articles/converting-an-owners-team-to-improved-organization-permissions
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
You have a few options to convert your legacy Owners team:
|
||||
|
||||
- Give the team a new name that denotes the members have a special status in the organization.
|
||||
- Delete the team after ensuring all members have been added to teams that grant necessary access to the organization's repositories.
|
||||
|
||||
### Give the Owners team a new name
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Note:** Because "admin" is a term for organization members with specific [access to certain repositories](/articles/repository-permission-levels-for-an-organization) in the organization, we recommend you avoid that term in any team name you decide on.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.owners-team %}
|
||||
{% data reusables.organizations.convert-owners-team-confirm %}
|
||||
5. In the team name field, choose a new name for the Owners team. For example:
|
||||
- If very few members of your organization were members of the Owners team, you might name the team "Core".
|
||||
- If all members of your organization were members of the Owners team so that they could [@mention teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), you might name the team "Employees".
|
||||
|
||||
6. Under the team description, click **Save and continue**.
|
||||
|
||||
7. Optionally, [make the team *public*](/articles/changing-team-visibility).
|
||||
|
||||
### Delete the legacy Owners team
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning:** If there are members of your Owners team who are not members of other teams, deleting the team will remove those members from the organization. Before deleting the team, ensure members are already direct members of the organization, or have collaborator access to necessary repositories.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.owners-team %}
|
||||
{% data reusables.organizations.convert-owners-team-confirm %}
|
||||
5. At the bottom of the page, review the warning and click **Delete the Owners team**.
|
||||
|
||||
@@ -1,27 +0,0 @@
|
||||
---
|
||||
title: Creating a new organization from scratch
|
||||
intro: Create an organization to apply fine-grained access permissions to repositories.
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
redirect_from:
|
||||
- /articles/creating-a-new-organization-from-scratch
|
||||
- /admin/user-management/creating-organizations
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
When you create a new organization from scratch, it doesn't have any repositories associated with it. For more information on adding repositories to your organization, see "[Creating a new repository](/articles/creating-a-new-repository)" and "[Transferring a repository](/articles/transferring-a-repository)."
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.organizations %}
|
||||
{% data reusables.organizations.new-organization %}
|
||||
4. Follow the prompts to create your organization. {% if currentVersion == "free-pro-team@latest" %}For more information about the plans available for your team, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/githubs-products)."{% endif %}
|
||||
|
||||
### Further reading
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
- "[Setting your billing email](/articles/setting-your-billing-email)"{% endif %}
|
||||
- "[About organizations](/articles/about-organizations)"
|
||||
@@ -1,32 +0,0 @@
|
||||
---
|
||||
title: Creating a team discussion
|
||||
intro: 'Any organization member can create a _public_ team discussion post. To create a _private_ team discussion post, you must be a member of the team or an organization owner.'
|
||||
redirect_from:
|
||||
- /articles/creating-a-team-discussion
|
||||
- /github/building-a-strong-community/creating-a-team-discussion
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- community
|
||||
---
|
||||
|
||||
{% data reusables.organizations.team-discussions-permissions %} For more information, see "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)."
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.specific_team %}
|
||||
{% data reusables.organizations.team-discussions-tab %}
|
||||
6. Type a team discussion title and a comment to start a conversation.
|
||||
|
||||
7. Optionally, select whether you want your post to be private or public using the drop-down menu.
|
||||
|
||||
8. Click **Comment**.
|
||||
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)"
|
||||
- "[Editing or deleting a team discussion](/github/setting-up-and-managing-organizations-and-teams/editing-or-deleting-a-team-discussion)"
|
||||
- "[Pinning a team discussion](/github/setting-up-and-managing-organizations-and-teams/pinning-a-team-discussion)"
|
||||
@@ -1,38 +0,0 @@
|
||||
---
|
||||
title: Creating a team
|
||||
intro: You can create independent or nested teams to manage repository permissions and mentions for groups of people.
|
||||
redirect_from:
|
||||
- /articles/creating-a-team-early-access-program/
|
||||
- /articles/creating-a-team
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
Only organization owners and maintainers of a parent team can create a new child team under a parent. Owners can also restrict creation permissions for all teams in an organization. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)."
|
||||
|
||||
{% data reusables.organizations.team-synchronization %}
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.new_team %}
|
||||
{% data reusables.organizations.team_name %}
|
||||
{% data reusables.organizations.team_description %}
|
||||
{% data reusables.organizations.create-team-choose-parent %}
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
1. Optionally, if your organization or enterprise account uses team synchronization, to connect an identity provider group to your team, use the "Identity Provider Groups" drop-down menu, and select up to 5 identity provider groups. For more information, see "[Synchronizing a team with an identity provider group](/github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group)."
|
||||
|
||||
{% endif %}
|
||||
{% data reusables.organizations.team_visibility %}
|
||||
{% data reusables.organizations.create_team %}
|
||||
9. Optionally, [give the team access to organization repositories](/articles/managing-team-access-to-an-organization-repository).
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[About teams](/articles/about-teams)"
|
||||
- "[Changing team visibility](/articles/changing-team-visibility)"
|
||||
- "[Moving a team in your organization's hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy)"
|
||||
@@ -1,29 +0,0 @@
|
||||
---
|
||||
title: Deleting a team
|
||||
intro: Organization owners can delete teams at any time from the team's settings page.
|
||||
redirect_from:
|
||||
- /articles/deleting-a-team
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** Only organization owners can delete parent teams. For more information, see "[About teams](/articles/about-teams)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.teams %}
|
||||
4. Select the team or teams you'd like to delete.
|
||||
|
||||
5. Above the list of teams, use the drop-down menu and click **Delete**.
|
||||
|
||||
6. Review the team or teams that will be deleted, then click **I understand, delete teams**.
|
||||
|
||||
@@ -1,34 +0,0 @@
|
||||
---
|
||||
title: Deleting an organization account
|
||||
intro: 'When you delete an organization, all repositories, forks of private repositories, wikis, issues, pull requests, and Project or Organization Pages are deleted as well. {% if currentVersion == "free-pro-team@latest" %}The organization name becomes available for use on a new user or organization account, and your billing will end.{% endif %}'
|
||||
redirect_from:
|
||||
- /articles/deleting-an-organization-account
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
{% tip %}
|
||||
|
||||
**Tip**: If you want to cancel your paid subscription, you can [downgrade your organization to {% data variables.product.prodname_free_team %}](/articles/downgrading-your-github-subscription) instead of deleting the organization and its content.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
### 1. Back up your organization content
|
||||
|
||||
Once you delete an organization, GitHub **cannot restore your content**. Therefore, before you delete your organization, make sure you have a copy of all repositories, wikis, issues, and project boards from the account.
|
||||
|
||||
### 2. Delete the organization
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
4. Near the bottom of the organization's settings page, click **Delete this Organization**.
|
||||
|
||||
@@ -1,21 +0,0 @@
|
||||
---
|
||||
title: Denying access to a previously approved OAuth App for your organization
|
||||
intro: 'If an organization no longer requires a previously authorized {% data variables.product.prodname_oauth_app %}, owners can remove the application''s access to the organization''s resources.'
|
||||
redirect_from:
|
||||
- /articles/denying-access-to-a-previously-approved-application-for-your-organization/
|
||||
- /articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.oauth_app_access %}
|
||||
5. Next to the application you'd like to disable, click {% octicon "pencil" aria-label="The edit icon" %}.
|
||||
|
||||
6. Click **Deny access**.
|
||||
|
||||
@@ -1,27 +0,0 @@
|
||||
---
|
||||
title: Disabling OAuth App access restrictions for your organization
|
||||
intro: 'Organization owners can disable restrictions on the {% data variables.product.prodname_oauth_app %}s that have access to the organization''s resources.'
|
||||
redirect_from:
|
||||
- /articles/disabling-third-party-application-restrictions-for-your-organization/
|
||||
- /articles/disabling-oauth-app-access-restrictions-for-your-organization
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
{% danger %}
|
||||
|
||||
**Warning**: When you disable {% data variables.product.prodname_oauth_app %} access restrictions for your organization, any organization member will automatically authorize {% data variables.product.prodname_oauth_app %} access to the organization's private resources when they approve an application for use in their personal account settings.
|
||||
|
||||
{% enddanger %}
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.oauth_app_access %}
|
||||
5. Click **Remove restrictions**.
|
||||
|
||||
6. After you review the information about disabling third-party application restrictions, click **Yes, remove application restrictions**.
|
||||
|
||||
@@ -1,86 +0,0 @@
|
||||
---
|
||||
title: Disabling or limiting GitHub Actions for your organization
|
||||
intro: 'Organization owners can disable, enable, and limit GitHub Actions for an organization.'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.22'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
### About {% data variables.product.prodname_actions %} permissions for your organization
|
||||
|
||||
{% data reusables.github-actions.disabling-github-actions %} For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)."
|
||||
|
||||
You can enable {% data variables.product.prodname_actions %} for all repositories in your organization. {% data reusables.github-actions.enabled-actions-description %} You can disable {% data variables.product.prodname_actions %} for all repositories in your organization. {% data reusables.github-actions.disabled-actions-description %}
|
||||
|
||||
Alternatively, you can enable {% data variables.product.prodname_actions %} for all repositories in your organization but limit the actions a workflow can run. {% data reusables.github-actions.enabled-local-github-actions %}
|
||||
|
||||
{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.23" %}
|
||||
|
||||
### Managing {% data variables.product.prodname_actions %} permissions for your organization
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.settings-sidebar-actions %}
|
||||
1. Under **Local and third-party Actions**, select an option.
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
|
||||
### Managing {% data variables.product.prodname_actions %} permissions for your organization
|
||||
|
||||
You can disable all workflows for an organization or set a policy that configures which actions can be used in an organization.
|
||||
|
||||
{% data reusables.actions.actions-use-policy-settings %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** You might not be able to manage these settings if your organization is managed by an enterprise that has overriding policy. For more information, {% if currentVersion == "free-pro-team@latest" %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% else %}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.settings-sidebar-actions %}
|
||||
1. Under **Policies**, select an option.
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
### Allowing specific actions to run
|
||||
|
||||
{% data reusables.actions.allow-specific-actions-intro %}
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.settings-sidebar-actions %}
|
||||
1. Under **Policies**, select **Allow select actions** and add your required actions to the list.
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
|
||||
### Enabling workflows for private repository forks
|
||||
|
||||
{% data reusables.github-actions.private-repository-forks-overview %}
|
||||
|
||||
#### Configuring the private fork policy for an organization
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.settings-sidebar-actions %}
|
||||
{% data reusables.github-actions.private-repository-forks-configure %}
|
||||
{% endif %}
|
||||
@@ -1,23 +0,0 @@
|
||||
---
|
||||
title: Disabling team discussions for your organization
|
||||
intro: Organization owners can choose to disable or enable team discussions across the organization.
|
||||
redirect_from:
|
||||
- /articles/disabling-team-discussions-for-your-organization
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
{% data reusables.organizations.team-discussions-default %} For more information on team discussions, see "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)."
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.teams_sidebar %}
|
||||
5. Under "Team discussions", unselect **Enable team discussions for this organization**.
|
||||
|
||||
6. Click **Save**.
|
||||
@@ -1,37 +0,0 @@
|
||||
---
|
||||
title: Downloading your organization's SAML single sign-on recovery codes
|
||||
intro: 'Organization administrators should download their organization''s SAML single sign-on recovery codes to ensure that they can access {% data variables.product.product_name %} even if the identity provider for the organization is unavailable.'
|
||||
redirect_from:
|
||||
- /articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes
|
||||
- /articles/downloading-your-organizations-saml-single-sign-on-recovery-codes
|
||||
product: '{% data reusables.gated-features.saml-sso %}'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
Recovery codes should not be shared or distributed. We recommend saving them with a password manager such as [LastPass](https://lastpass.com/), [1Password](https://1password.com/), or [Keeper](https://keepersecurity.com/).
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
5. Under "SAML single sign-on", in the note about recovery codes, click **Save your recovery codes**.
|
||||
|
||||
6. Save your recovery codes by clicking **Download**, **Print**, or **Copy**.
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Your recovery codes will help get you back into {% data variables.product.product_name %} if your IdP is unavailable. If you generate new recovery codes the recovery codes displayed on the "Single sign-on recovery codes" page are automatically updated.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
7. Once you use a recovery code to regain access to {% data variables.product.product_name %}, it cannot be reused. Access to {% data variables.product.product_name %} will only be available for 24 hours before you'll be asked to sign in using single sign-on.
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
|
||||
- "[Accessing your organization if your identity provider is unavailable](/articles/accessing-your-organization-if-your-identity-provider-is-unavailable)"
|
||||
@@ -1,29 +0,0 @@
|
||||
---
|
||||
title: Editing or deleting a team discussion
|
||||
intro: 'Organization members can edit or delete discussions on a team''s page. If you''re an organization member, you can edit or delete the discussion.'
|
||||
redirect_from:
|
||||
- /articles/editing-or-deleting-a-team-discussion
|
||||
- /github/building-a-strong-community/editing-or-deleting-a-team-discussion
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- community
|
||||
---
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.specific_team %}
|
||||
{% data reusables.organizations.team-discussions-tab %}
|
||||
6. Click {% octicon "kebab-horizontal" aria-label="The edit icon" %} next to the team discussion you want to edit or delete.
|
||||
7. Click **Edit**. Optionally, click **Delete**.
|
||||
|
||||
8. Modify the team discussion title and comment as needed, and click **Update comment**.
|
||||
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[About team discussions](/github/setting-up-and-managing-organizations-and-teams/about-team-discussions)"
|
||||
- "[Creating a team discussion](/github/setting-up-and-managing-organizations-and-teams/creating-a-team-discussion)"
|
||||
- "[Pinning a team discussion](/github/setting-up-and-managing-organizations-and-teams/pinning-a-team-discussion)"
|
||||
@@ -1,57 +0,0 @@
|
||||
---
|
||||
title: Enabling and testing SAML single sign-on for your organization
|
||||
intro: Organization owners and admins can enable SAML single sign-on to add an extra layer of security to their organization.
|
||||
product: '{% data reusables.gated-features.saml-sso %}'
|
||||
redirect_from:
|
||||
- /articles/enabling-and-testing-saml-single-sign-on-for-your-organization
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
You can enable SAML SSO in your organization without requiring all members to use it. Enabling but not enforcing SAML SSO in your organization can help smooth your organization's SAML SSO adoption. Once a majority of your organization's members use SAML SSO, you can enforce it within your organization.
|
||||
|
||||
If you enable but don't enforce SAML SSO, organization members who choose not to use SAML SSO can still be members of the organization. For more information on enforcing SAML SSO, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
|
||||
|
||||
{% data reusables.saml.outside-collaborators-exemption %}
|
||||
|
||||
Prior to enforcing SAML SSO in your organization, ensure that you've set up your identity provider (IdP). For more information, see "[Preparing to enforce SAML single sign-on in your organization](/articles/preparing-to-enforce-saml-single-sign-on-in-your-organization)."
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
5. Under "SAML single sign-on", select **Enable SAML authentication**.
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** After enabling SAML SSO, you can download your single sign-on recovery codes so that you can access your organization even if your IdP is unavailable. For more information, see "[Downloading your organization's SAML single sign-on recovery codes](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
6. In the "Sign on URL" field, type the HTTPS endpoint of your IdP for single sign-on requests. This value is available in your IdP configuration.
|
||||
|
||||
7. Optionally, in the "Issuer" field, type your SAML issuer's name. This verifies the authenticity of sent messages.
|
||||
|
||||
8. Under "Public Certificate," paste a certificate to verify SAML responses.
|
||||
|
||||
9. Click {% octicon "pencil" aria-label="The edit icon" %} and then in the Signature Method and Digest Method drop-downs, choose the hashing algorithm used by your SAML issuer to verify the integrity of the requests.
|
||||
|
||||
10. Before enabling SAML SSO for your organization, click **Test SAML configuration** to ensure that the information you've entered is correct. 
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** {% data reusables.saml.testing-saml-sso %}
|
||||
|
||||
{% endtip %}
|
||||
11. To enforce SAML SSO and remove all organization members who haven't authenticated via your IdP, select **Require SAML SSO authentication for all members of the _organization name_ organization**. For more information on enforcing SAML SSO, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
|
||||
|
||||
12. Click **Save**.
|
||||
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
|
||||
@@ -1,32 +0,0 @@
|
||||
---
|
||||
title: Enabling OAuth App access restrictions for your organization
|
||||
intro: 'Organization owners can enable {% data variables.product.prodname_oauth_app %} access restrictions to prevent untrusted apps from accessing the organization''s resources while allowing organization members to use {% data variables.product.prodname_oauth_app %}s for their personal accounts.'
|
||||
redirect_from:
|
||||
- /articles/enabling-third-party-application-restrictions-for-your-organization/
|
||||
- /articles/enabling-oauth-app-access-restrictions-for-your-organization
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
{% data reusables.organizations.oauth_app_restrictions_default %}
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warnings**:
|
||||
- Enabling {% data variables.product.prodname_oauth_app %} access restrictions will revoke organization access for all previously authorized {% data variables.product.prodname_oauth_app %}s and SSH keys. For more information, see "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)."
|
||||
- Once you've set up {% data variables.product.prodname_oauth_app %} access restrictions, make sure to re-authorize any {% data variables.product.prodname_oauth_app %} that require access to the organization's private data on an ongoing basis. All organization members will need to create new SSH keys, and the organization will need to create new deploy keys as needed.
|
||||
- When {% data variables.product.prodname_oauth_app %} access restrictions are enabled, applications can use an OAuth token to access information about {% data variables.product.prodname_marketplace %} transactions.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.oauth_app_access %}
|
||||
5. Under "Third-party application access policy," click **Setup application access restrictions**.
|
||||
|
||||
6. After you review the information about third-party access restrictions, click **Restrict third-party application access**.
|
||||
|
||||
@@ -1,30 +0,0 @@
|
||||
---
|
||||
title: Enforcing SAML single sign-on for your organization
|
||||
intro: Organization owners and admins can enforce SAML SSO so that all organization members must authenticate via an identity provider.
|
||||
product: '{% data reusables.gated-features.saml-sso %}'
|
||||
redirect_from:
|
||||
- /articles/enforcing-saml-single-sign-on-for-your-organization
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
If you enforce SAML SSO in your organization, any members, including admins who have not authenticated via your SAML identity provider (IdP), will be removed from the organization and will receive an email notifying them about the removal. Bots and service accounts that do not have external identities set up in your organization's IdP will also be removed. For more information on bots and service accounts, see "[Managing bots and service accounts with SAML single sign-on](/articles/managing-bots-and-service-accounts-with-saml-single-sign-on)." You can restore organization members once they successfully complete single sign-on.
|
||||
|
||||
If your organization is owned by an enterprise account, enabling SAML for the enterprise account will override your organization-level SAML configuration. For more information, see "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account)."
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** {% data reusables.saml.testing-saml-sso %}
|
||||
|
||||
{% endtip %}
|
||||
|
||||
1. Enable and test SAML SSO for your organization. For more information on this process, see "[Enabling and testing SAML single sign-on for your organization](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)."
|
||||
2. After you select **Require SAML SSO authentication for all members of the SAML SSO Org organization**, organization members who haven't authenticated via your IdP will be shown. If you enforce SAML SSO, these members will be removed from the organization.
|
||||
3. Click **Enforce SAML SSO** to enforce SAML SSO and remove the listed organization members.
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
|
||||
@@ -1,31 +0,0 @@
|
||||
---
|
||||
title: Giving "team maintainer" permissions to an organization member
|
||||
intro: 'An organization owner can promote any member of the organization to *team maintainer* for a team, giving them a subset of privileges available to organization owners.'
|
||||
redirect_from:
|
||||
- /articles/giving-team-maintainer-permissions-to-an-organization-member-early-access-program/
|
||||
- /articles/giving-team-maintainer-permissions-to-an-organization-member
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
{% data reusables.organizations.team_maintainers_can %}
|
||||
|
||||
### Promoting an organization member to team maintainer
|
||||
|
||||
Before promoting an organization member to team maintainer, the person must already be a member of the team.
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.specific_team %}
|
||||
{% data reusables.organizations.team_members_tab %}
|
||||
4. Select the person or people you'd like to promote to team maintainer.
|
||||
|
||||
5. Above the list of team members, use the drop-down menu and click **Change role...**.
|
||||
|
||||
6. Select a new role and click **Change role**.
|
||||
|
||||
@@ -1,13 +0,0 @@
|
||||
---
|
||||
title: Granting access to your organization with SAML single sign-on
|
||||
intro: 'Organization administrators can grant access to their organization with SAML single sign-on. This access can be granted to organization members, bots, and service accounts.'
|
||||
mapTopic: true
|
||||
redirect_from:
|
||||
- /articles/granting-access-to-your-organization-with-saml-single-sign-on
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
@@ -1,145 +0,0 @@
|
||||
---
|
||||
title: Setting up and managing organizations and teams
|
||||
shortTitle: Organizations and teams
|
||||
intro: Collaborate across many projects while managing access to projects and data and customizing settings for your organization.
|
||||
redirect_from:
|
||||
- /articles/about-improved-organization-permissions/
|
||||
- /categories/setting-up-and-managing-organizations-and-teams
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
|
||||
### Table of Contents
|
||||
|
||||
{% topic_link_in_list /collaborating-with-groups-in-organizations %}
|
||||
{% link_in_list /about-organizations %}
|
||||
{% link_in_list /about-your-organization-dashboard %}
|
||||
{% link_in_list /creating-a-new-organization-from-scratch %}
|
||||
{% link_in_list /accessing-your-organizations-settings %}
|
||||
{% link_in_list /about-your-organizations-news-feed %}
|
||||
{% link_in_list /viewing-insights-for-your-organization %}
|
||||
{% topic_link_in_list /managing-membership-in-your-organization %}
|
||||
{% link_in_list /inviting-users-to-join-your-organization %}
|
||||
{% link_in_list /canceling-or-editing-an-invitation-to-join-your-organization %}
|
||||
<!-- else -->
|
||||
{% link_in_list /adding-people-to-your-organization %}
|
||||
{% link_in_list /removing-a-member-from-your-organization %}
|
||||
{% link_in_list /reinstating-a-former-member-of-your-organization %}
|
||||
{% link_in_list /can-i-create-accounts-for-people-in-my-organization %}
|
||||
{% topic_link_in_list /managing-peoples-access-to-your-organization-with-roles %}
|
||||
{% link_in_list /permission-levels-for-an-organization %}
|
||||
{% link_in_list /maintaining-ownership-continuity-for-your-organization %}
|
||||
{% link_in_list /giving-team-maintainer-permissions-to-an-organization-member %}
|
||||
{% link_in_list /adding-a-billing-manager-to-your-organization %}
|
||||
{% link_in_list /removing-a-billing-manager-from-your-organization %}
|
||||
{% topic_link_in_list /organizing-members-into-teams %}
|
||||
{% link_in_list /about-teams %}
|
||||
{% link_in_list /creating-a-team %}
|
||||
{% link_in_list /setting-your-teams-profile-picture %}
|
||||
{% link_in_list /adding-organization-members-to-a-team %}
|
||||
{% link_in_list /managing-code-review-assignment-for-your-team %}
|
||||
{% link_in_list /renaming-a-team %}
|
||||
{% link_in_list /changing-team-visibility %}
|
||||
{% link_in_list /synchronizing-a-team-with-an-identity-provider-group %}
|
||||
{% link_in_list /moving-a-team-in-your-organizations-hierarchy %}
|
||||
{% link_in_list /requesting-to-add-a-child-team %}
|
||||
{% link_in_list /requesting-to-add-or-change-a-parent-team %}
|
||||
{% link_in_list /removing-organization-members-from-a-team %}
|
||||
{% link_in_list /disabling-team-discussions-for-your-organization %}
|
||||
{% link_in_list /managing-scheduled-reminders-for-your-team %}
|
||||
{% link_in_list /deleting-a-team %}
|
||||
{% topic_link_in_list /collaborating-with-your-team %}
|
||||
{% link_in_list /about-team-discussions %}
|
||||
{% link_in_list /creating-a-team-discussion %}
|
||||
{% link_in_list /editing-or-deleting-a-team-discussion %}
|
||||
{% link_in_list /pinning-a-team-discussion %}
|
||||
{% topic_link_in_list /managing-access-to-your-organizations-repositories %}
|
||||
{% link_in_list /repository-permission-levels-for-an-organization %}
|
||||
{% link_in_list /setting-base-permissions-for-an-organization %}
|
||||
{% link_in_list /viewing-people-with-access-to-your-repository %}
|
||||
{% link_in_list /managing-an-individuals-access-to-an-organization-repository %}
|
||||
{% link_in_list /managing-team-access-to-an-organization-repository %}
|
||||
{% link_in_list /adding-outside-collaborators-to-repositories-in-your-organization %}
|
||||
{% link_in_list /canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization %}
|
||||
{% link_in_list /removing-an-outside-collaborator-from-an-organization-repository %}
|
||||
{% link_in_list /converting-an-organization-member-to-an-outside-collaborator %}
|
||||
{% link_in_list /converting-an-outside-collaborator-to-an-organization-member %}
|
||||
{% link_in_list /reinstating-a-former-outside-collaborators-access-to-your-organization %}
|
||||
{% topic_link_in_list /managing-access-to-your-organizations-project-boards %}
|
||||
{% link_in_list /project-board-permissions-for-an-organization %}
|
||||
{% link_in_list /managing-access-to-a-project-board-for-organization-members %}
|
||||
{% link_in_list /managing-team-access-to-an-organization-project-board %}
|
||||
{% link_in_list /managing-an-individuals-access-to-an-organization-project-board %}
|
||||
{% link_in_list /adding-an-outside-collaborator-to-a-project-board-in-your-organization %}
|
||||
{% link_in_list /removing-an-outside-collaborator-from-an-organization-project-board %}
|
||||
{% topic_link_in_list /managing-access-to-your-organizations-apps %}
|
||||
{% link_in_list /adding-github-app-managers-in-your-organization %}
|
||||
{% link_in_list /removing-github-app-managers-from-your-organization %}
|
||||
{% topic_link_in_list /managing-organization-settings %}
|
||||
{% link_in_list /verifying-your-organizations-domain %}
|
||||
{% link_in_list /renaming-an-organization %}
|
||||
{% link_in_list /transferring-organization-ownership %}
|
||||
{% link_in_list /restricting-repository-creation-in-your-organization %}
|
||||
{% link_in_list /setting-permissions-for-deleting-or-transferring-repositories %}
|
||||
{% link_in_list /restricting-repository-visibility-changes-in-your-organization %}
|
||||
{% link_in_list /managing-the-forking-policy-for-your-organization %}
|
||||
{% link_in_list /disabling-or-limiting-github-actions-for-your-organization %}
|
||||
{% link_in_list /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization %}
|
||||
{% link_in_list /setting-permissions-for-adding-outside-collaborators %}
|
||||
{% link_in_list /allowing-people-to-delete-issues-in-your-organization %}{% if currentVersion == "free-pro-team@latest" %}
|
||||
{% link_in_list /managing-discussion-creation-for-repositories-in-your-organization %}{% endif %}
|
||||
{% link_in_list /setting-team-creation-permissions-in-your-organization %}
|
||||
{% link_in_list /managing-scheduled-reminders-for-your-organization %}
|
||||
{% link_in_list /managing-the-default-branch-name-for-repositories-in-your-organization %}
|
||||
{% link_in_list /managing-default-labels-for-repositories-in-your-organization %}
|
||||
{% link_in_list /changing-the-visibility-of-your-organizations-dependency-insights %}
|
||||
{% link_in_list /managing-the-display-of-member-names-in-your-organization %}
|
||||
{% link_in_list /managing-updates-from-accounts-your-organization-sponsors %}
|
||||
{% link_in_list /managing-the-publication-of-github-pages-sites-for-your-organization %}
|
||||
{% link_in_list /deleting-an-organization-account %}
|
||||
{% link_in_list /converting-an-organization-into-a-user %}
|
||||
{% link_in_list /integrating-jira-with-your-organization-project-board %}
|
||||
{% link_in_list /upgrading-to-the-corporate-terms-of-service %}
|
||||
{% topic_link_in_list /migrating-to-improved-organization-permissions %}
|
||||
{% link_in_list /converting-an-owners-team-to-improved-organization-permissions %}
|
||||
{% link_in_list /converting-an-admin-team-to-improved-organization-permissions %}
|
||||
{% link_in_list /migrating-admin-teams-to-improved-organization-permissions %}
|
||||
{% topic_link_in_list /restricting-access-to-your-organizations-data %}
|
||||
{% link_in_list /about-oauth-app-access-restrictions %}
|
||||
{% link_in_list /enabling-oauth-app-access-restrictions-for-your-organization %}
|
||||
{% link_in_list /disabling-oauth-app-access-restrictions-for-your-organization %}
|
||||
{% link_in_list /approving-oauth-apps-for-your-organization %}
|
||||
{% link_in_list /denying-access-to-a-previously-approved-oauth-app-for-your-organization %}
|
||||
{% topic_link_in_list /keeping-your-organization-secure %}
|
||||
{% link_in_list /viewing-whether-users-in-your-organization-have-2fa-enabled %}
|
||||
{% link_in_list /preparing-to-require-two-factor-authentication-in-your-organization %}
|
||||
{% link_in_list /requiring-two-factor-authentication-in-your-organization %}
|
||||
{% link_in_list /managing-security-and-analysis-settings-for-your-organization %}
|
||||
{% link_in_list /managing-allowed-ip-addresses-for-your-organization %}
|
||||
{% link_in_list /restricting-email-notifications-to-an-approved-domain %}
|
||||
{% link_in_list /reviewing-the-audit-log-for-your-organization %}
|
||||
{% link_in_list /reviewing-your-organizations-installed-integrations %}
|
||||
{% topic_link_in_list /managing-saml-single-sign-on-for-your-organization %}
|
||||
{% link_in_list /about-identity-and-access-management-with-saml-single-sign-on %}
|
||||
{% link_in_list /about-scim %}
|
||||
{% link_in_list /connecting-your-identity-provider-to-your-organization %}
|
||||
{% link_in_list /configuring-saml-single-sign-on-and-scim-using-okta %}
|
||||
{% link_in_list /enabling-and-testing-saml-single-sign-on-for-your-organization %}
|
||||
{% link_in_list /preparing-to-enforce-saml-single-sign-on-in-your-organization %}
|
||||
{% link_in_list /enforcing-saml-single-sign-on-for-your-organization %}
|
||||
{% link_in_list /downloading-your-organizations-saml-single-sign-on-recovery-codes %}
|
||||
{% link_in_list /managing-team-synchronization-for-your-organization %}
|
||||
{% link_in_list /accessing-your-organization-if-your-identity-provider-is-unavailable %}
|
||||
{% topic_link_in_list /granting-access-to-your-organization-with-saml-single-sign-on %}
|
||||
{% link_in_list /managing-bots-and-service-accounts-with-saml-single-sign-on %}
|
||||
{% link_in_list /viewing-and-managing-a-members-saml-access-to-your-organization %}
|
||||
{% link_in_list /about-two-factor-authentication-and-saml-single-sign-on %}
|
||||
{% topic_link_in_list /managing-git-access-to-your-organizations-repositories %}
|
||||
{% link_in_list /about-ssh-certificate-authorities %}
|
||||
{% link_in_list /managing-your-organizations-ssh-certificate-authorities %}
|
||||
@@ -1,28 +0,0 @@
|
||||
---
|
||||
title: Integrating Jira with your organization project board
|
||||
intro: 'You can integrate Jira Cloud with your organization account to scan commits and pull requests, creating relevant metadata and hyperlinks in any mentioned Jira issues.'
|
||||
redirect_from:
|
||||
- /articles/integrating-jira-with-your-organization-project-board
|
||||
versions:
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
---
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
2. In the left sidebar under **Organization settings**, click the name of your organization.
|
||||
|
||||
3. In the left sidebar under **Developer settings**, click **OAuth applications**.
|
||||
|
||||
4. Click **Register a new application**.
|
||||
5. Under **Application name**, type "Jira".
|
||||
6. Under **Homepage URL**, type the full URL to your Jira instance.
|
||||
7. Under **Authorization callback URL**, type the full URL to your Jira instance.
|
||||
8. Click **Register application**.
|
||||
|
||||
9. Under **Organization owned applications**, note the "Client ID" and "Client Secret" values.
|
||||
|
||||
{% data reusables.user_settings.jira_help_docs %}
|
||||
|
||||
### Further reading
|
||||
|
||||
- ["Integrating Jira with your personal projects"](/articles/integrating-jira-with-your-personal-projects)
|
||||
- <a href="https://confluence.atlassian.com/adminjiracloud/connect-jira-cloud-to-github-814188429.html" data-proofer-ignore>Connect Jira Cloud to GitHub</a> (Atlassian documentation)
|
||||
@@ -1,35 +0,0 @@
|
||||
---
|
||||
title: Inviting users to join your organization
|
||||
intro: 'You can invite anyone to become a member of your organization using their {% data variables.product.product_name %} username or email address.'
|
||||
permissions: Organization owners can invite users to join an organization.
|
||||
redirect_from:
|
||||
- /articles/adding-or-inviting-members-to-a-team-in-an-organization/
|
||||
- /articles/inviting-users-to-join-your-organization
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tips**:
|
||||
- If your organization has a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." {% data reusables.organizations.org-invite-expiration %}
|
||||
- If your organization requires members to use two-factor authentication, users that you invite must enable two-factor authentication before accepting the invitation. For more information, see "[Requiring two-factor authentication in your organization](/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization)" and "[Securing your account with two-factor authentication (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.people %}
|
||||
{% data reusables.organizations.invite_member_from_people_tab %}
|
||||
{% data reusables.organizations.invite_to_org %}
|
||||
{% data reusables.organizations.choose-to-restore-privileges %}
|
||||
{% data reusables.organizations.choose-user-role %}
|
||||
{% data reusables.organizations.add-user-to-teams %}
|
||||
{% data reusables.organizations.send-invitation %}
|
||||
{% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %}
|
||||
|
||||
### Further reading
|
||||
- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)"
|
||||
@@ -1,16 +0,0 @@
|
||||
---
|
||||
title: Keeping your organization secure
|
||||
redirect_from:
|
||||
- /articles/preventing-unauthorized-access-to-organization-information/
|
||||
- /articles/keeping-your-organization-secure
|
||||
intro: 'Organization owners have several features to help them keep their projects and data secure. If you''re the owner of an organization, you should regularly review your organization''s audit log{% if currentVersion != "github-ae@latest" %}, member 2FA status,{% endif %} and application settings to ensure that no unauthorized or malicious activity has occurred.'
|
||||
mapTopic: true
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
@@ -1,34 +0,0 @@
|
||||
---
|
||||
title: Maintaining ownership continuity for your organization
|
||||
intro: Organizations can have more than one organization owner to avoid lapses in ownership.
|
||||
redirect_from:
|
||||
- /articles/changing-a-person-s-role-to-owner
|
||||
- /articles/changing-a-persons-role-to-owner
|
||||
- /github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner
|
||||
permissions: Organization owners can promote any member of an organization to an organization owner.
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
### About maintaining ownership continuity for your organization
|
||||
|
||||
{% data reusables.organizations.org-ownership-recommendation %}
|
||||
|
||||
Organization owners have full administrative access to the organization. {% data reusables.organizations.new-org-permissions-more-info %}
|
||||
|
||||
### Appointing an organization owner
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.people %}
|
||||
4. Select the person or people you'd like to promote to owner.
|
||||
|
||||
5. Above the list of members, use the drop-down menu and click **Change role**.
|
||||
|
||||
6. Select a new role for the person or people, then click **Change role**.
|
||||
|
||||
@@ -1,39 +0,0 @@
|
||||
---
|
||||
title: Managing access to a project board for organization members
|
||||
intro: 'As an organization owner or project board admin, you can set a default permission level for a project board for all organization members.'
|
||||
redirect_from:
|
||||
- /articles/managing-access-to-a-project-board-for-organization-members
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
By default, organization members have write access to their organization's project boards unless organization owners or project board admins set different permissions for specific project boards.
|
||||
|
||||
### Setting a baseline permission level for all organization members
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** You can give an organization member higher permissions to project board. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.organization-wide-project %}
|
||||
{% data reusables.project-management.select-project %}
|
||||
{% data reusables.project-management.click-menu %}
|
||||
{% data reusables.project-management.access-collaboration-settings %}
|
||||
8. Under "Organization member permission", choose a baseline permission level for all organization members: **Read**, **Write**, **Admin**, or **None**.
|
||||
|
||||
9. Click **Save**.
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[Managing an individual’s access to an organization project board](/articles/managing-an-individual-s-access-to-an-organization-project-board)"
|
||||
- "[Managing team access to an organization project board](/articles/managing-team-access-to-an-organization-project-board)"
|
||||
- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)"
|
||||
@@ -1,16 +0,0 @@
|
||||
---
|
||||
title: Managing access to your organization's apps
|
||||
intro: 'As an organization owner, you can allow individual organization members to manage {% data variables.product.prodname_github_app %}s in your organization.'
|
||||
redirect_from:
|
||||
- /articles/managing-access-to-your-organization-s-apps
|
||||
- /articles/managing-access-to-your-organizations-apps
|
||||
mapTopic: true
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
@@ -1,16 +0,0 @@
|
||||
---
|
||||
title: Managing access to your organization’s project boards
|
||||
intro: 'As an organization owner or project board admin, you can give organization members, teams, and outside collaborators different levels of access to project boards owned by your organization.'
|
||||
redirect_from:
|
||||
- /articles/managing-access-to-your-organization-s-project-boards
|
||||
- /articles/managing-access-to-your-organizations-project-boards
|
||||
mapTopic: true
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
@@ -1,17 +0,0 @@
|
||||
---
|
||||
title: Managing access to your organization's repositories
|
||||
intro: Organization owners can manage individual and team access to the organization's repositories. Team maintainers can also manage a team's repository access.
|
||||
redirect_from:
|
||||
- /articles/permission-levels-for-an-organization-repository/
|
||||
- /articles/managing-access-to-your-organization-s-repositories
|
||||
- /articles/managing-access-to-your-organizations-repositories
|
||||
mapTopic: true
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
@@ -1,75 +0,0 @@
|
||||
---
|
||||
title: Managing allowed IP addresses for your organization
|
||||
intro: You can restrict access to your organization's assets by configuring a list of IP addresses that are allowed to connect.
|
||||
product: '{% data reusables.gated-features.allowed-ip-addresses %}'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
Organization owners can manage allowed IP addresses for an organization.
|
||||
|
||||
### About allowed IP addresses
|
||||
|
||||
You can restrict access to organization assets by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-enable %}
|
||||
|
||||
You can also configure allowed IP addresses for the organizations in an enterprise account. For more information, see {% if currentVersion == "github-ae@latest" %}"[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)." {% else %}"[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account)."{% endif %}
|
||||
|
||||
### Adding an allowed IP address
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
|
||||
|
||||
### Enabling allowed IP addresses
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
3. Under "IP allow list", select **Enable IP allow list**.
|
||||
|
||||
4. Click **Save**.
|
||||
|
||||
### Editing an allowed IP address
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
|
||||
8. Click **Update**.
|
||||
|
||||
### Deleting an allowed IP address
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
|
||||
|
||||
### Using {% data variables.product.prodname_actions %} with an IP allow list
|
||||
|
||||
{% if currentVersion == "github-ae@latest" %}
|
||||
|
||||
{% data reusables.github-actions.ip-allow-list-hosted-runners %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
|
||||
|
||||
{% endif %}
|
||||
@@ -1,62 +0,0 @@
|
||||
---
|
||||
title: Managing an individual’s access to an organization project board
|
||||
intro: 'As an organization owner or project board admin, you can manage an individual member''s access to a project board owned by your organization.'
|
||||
redirect_from:
|
||||
- /articles/managing-an-individual-s-access-to-an-organization-project-board
|
||||
- /articles/managing-an-individuals-access-to-an-organization-project-board
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data reusables.project-management.cascading-permissions %} For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Giving an organization member access to a project board
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.organization-wide-project %}
|
||||
{% data reusables.project-management.select-project %}
|
||||
{% data reusables.project-management.click-menu %}
|
||||
{% data reusables.project-management.access-collaboration-settings %}
|
||||
{% data reusables.project-management.collaborator-option %}
|
||||
9. Under "Search by username, full name or email address", type the collaborator's name, username, or {% data variables.product.prodname_dotcom %} email.
|
||||
|
||||
{% data reusables.project-management.add-collaborator %}
|
||||
{% data reusables.project-management.collaborator-permissions %}
|
||||
|
||||
### Changing an organization member's access to a project board
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.organization-wide-project %}
|
||||
{% data reusables.project-management.select-project %}
|
||||
{% data reusables.project-management.click-menu %}
|
||||
{% data reusables.project-management.access-collaboration-settings %}
|
||||
{% data reusables.project-management.collaborator-option %}
|
||||
{% data reusables.project-management.collaborator-permissions %}
|
||||
|
||||
### Removing an organization member's access to a project board
|
||||
|
||||
When you remove a collaborator from a project board, they may still retain access to the board based on the permissions they have for other roles. To completely remove access to a project board, you must remove access for each role the person has. For instance, a person may have access to the project board as an organization member or team member. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)."
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.organization-wide-project %}
|
||||
{% data reusables.project-management.select-project %}
|
||||
{% data reusables.project-management.click-menu %}
|
||||
{% data reusables.project-management.access-collaboration-settings %}
|
||||
{% data reusables.project-management.collaborator-option %}
|
||||
{% data reusables.project-management.remove-collaborator %}
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)"
|
||||
@@ -1,41 +0,0 @@
|
||||
---
|
||||
title: Managing an individual's access to an organization repository
|
||||
intro: You can manage a person's access to a repository owned by your organization.
|
||||
redirect_from:
|
||||
- /articles/managing-an-individual-s-access-to-an-organization-repository-early-access-program/
|
||||
- /articles/managing-an-individual-s-access-to-an-organization-repository
|
||||
- /articles/managing-an-individuals-access-to-an-organization-repository
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
People with admin permissions can manage the access of organization members and outside collaborators to an organization repository.
|
||||
|
||||
### Removing access to repositories
|
||||
|
||||
When you remove a collaborator from a repository in your organization, the collaborator loses read and write access to the repository. If the repository is private and the collaborator has forked the repository, then their fork is also deleted, but the collaborator will still retain any local clones of your repository.
|
||||
|
||||
{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
|
||||
|
||||
### Managing an individual's access to an organization repository
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.people %}
|
||||
4. Click either **Members** or **Outside collaborators** to manage people with different types of access. 
|
||||
5. To the right of the name of the person you'd like to manage, use the {% octicon "gear" aria-label="The Settings gear" %} drop-down menu, and click **Manage**.
|
||||
|
||||
6. On the "Manage access" page, next to the repository, click **Manage access**.
|
||||
|
||||
7. Review the person's access to a given repository, such as whether they're a collaborator or have access to the repository via team membership.
|
||||
|
||||
|
||||
### Further reading
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}- "[Limiting interactions with your repository](/articles/limiting-interactions-with-your-repository)"{% endif %}
|
||||
- "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)"
|
||||
@@ -1,24 +0,0 @@
|
||||
---
|
||||
title: Managing bots and service accounts with SAML single sign-on
|
||||
intro: Organizations that have enabled SAML single sign-on can retain access for bots and service accounts.
|
||||
product: '{% data reusables.gated-features.saml-sso %}'
|
||||
redirect_from:
|
||||
- /articles/managing-bots-and-service-accounts-with-saml-single-sign-on
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
To retain access for bots and service accounts, organization administrators can [enable](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization), but **not** [enforce](/articles/enforcing-saml-single-sign-on-for-your-organization) SAML single sign-on for their organization. If you need to enforce SAML single sign-on for your organization, you can create an external identity for the bot or service account with your identity provider (IdP).
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Note:** If you enforce SAML single sign-on for your organization and **do not** have external identities set up for bots and service accounts with your IdP, they will be removed from your organization.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
### Further reading
|
||||
|
||||
- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
|
||||
@@ -1,56 +0,0 @@
|
||||
---
|
||||
title: Managing code review assignment for your team
|
||||
intro: Code review assignments clearly indicate which members of a team are expected to submit a review for a pull request.
|
||||
product: '{% data reusables.gated-features.code-review-assignment %}'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=2.20'
|
||||
github-ae: '*'
|
||||
topics:
|
||||
- organizations
|
||||
- teams
|
||||
---
|
||||
|
||||
Team maintainers and organization owners can configure code review assignments.
|
||||
|
||||
### About code review assignments
|
||||
|
||||
By using code review assignments, any time your team has been requested to review a pull request, the team is removed as a reviewer and a specified subset of team members are assigned in the team's place. Code review assignments allow you to decide whether the whole team or just a subset of team members are notified when a team is requested for review.
|
||||
|
||||
When code owners are automatically requested for review, the team is still removed and replaced with individuals. The individual approvals don't satisfy the requirement for code owner approval in a protected branch. For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)."
|
||||
|
||||
### Routing algorithms
|
||||
|
||||
Code review assignments automatically choose and assign reviewers based on one of two possible algorithms.
|
||||
|
||||
The round robin algorithm chooses reviewers based on who's received the least recent review request, focusing on alternating between all members of the team regardless of the number of outstanding reviews they currently have.
|
||||
|
||||
The load balance algorithm chooses reviewers based on each member's total number of recent review requests and considers the number of outstanding reviews for each member. The load balance algorithm tries to ensure that each team member reviews an equal number of pull requests in any 30 day period.
|
||||
|
||||
### Configuring code review assignment
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.specific_team %}
|
||||
{% data reusables.organizations.team_settings %}
|
||||
5. In the left sidebar, click **Code review assignment**
|
||||
|
||||
6. Select **Enable auto assignment**.
|
||||
|
||||
7. Under "How many team members should be assigned to review?", use the drop-down menu and choose a number of reviewers to be assigned to each pull request.
|
||||
|
||||
8. Under "Routing algorithm", use the drop-down menu and choose which algorithm you'd like to use. For more information, see "[Routing algorithms](#routing-algorithms)."
|
||||
|
||||
9. Optionally, to always skip certain members of the team, select **Never assign certain team members**. Then, select one or more team members you'd like to always skip.
|
||||
|
||||
10. Optionally, to only notify the team members chosen by code review assignment for each pull review request, under "Notifications" select **If assigning team members, don't notify the entire team.**
|
||||
|
||||
11. Click **Save changes**.
|
||||
|
||||
### Disabling code review assignment
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.specific_team %}
|
||||
{% data reusables.organizations.team_settings %}
|
||||
5. Select **Enable auto assignment** to remove the checkmark.
|
||||
|
||||
6. Click **Save changes**.
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user