зеркало из https://github.com/github/docs.git
Replace organizations.org_settings reusable with profile.org_settings reusable in some files
This commit is contained in:
Lee Dohm
Родитель
afcb44ffed
Коммит
cce98fc96d
|
|
@ -57,7 +57,7 @@ In your organization's repositories, blocked users also cannot:
|
|||
1. To block an organization member, first [remove the user](/articles/removing-a-member-from-your-organization) from the organization.
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.block_users %}
|
||||
6. Under "Block a user", type the username of the user you'd like to block.
|
||||
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ If you selected a specific amount of time to block the user, they will be automa
|
|||
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.block_users %}
|
||||
5. Under "Blocked users", next to the user you'd like to unblock, click **Unblock**.
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ topics:
|
|||
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.block_users %}
|
||||
5. Under "Blocked users", review the list of users who are blocked from your organization.
|
||||
|
||||
|
|
|
|||
|
|
@ -24,13 +24,13 @@ Members of the organization are not affected by any of the limit types.
|
|||
|
||||
When you enable organization-wide activity limitations, you can't enable or disable interaction limits on individual repositories. For more information on limiting activity for an individual repository, see "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)."
|
||||
|
||||
Organization owners can also block users for a specific amount of time. After the block expires, the user is automatically unblocked. For more information, see "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)."
|
||||
Organization owners can also block users for a specific amount of time. After the block expires, the user is automatically unblocked. For more information, see "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)."
|
||||
|
||||
### Limiting interactions in your organization
|
||||
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the organization settings sidebar, click **Moderation settings**.
|
||||
|
||||
1. Under "Moderation settings", click **Interaction limits**.
|
||||
|
|
|
|||
|
|
@ -13,16 +13,16 @@ Once your organization has been verified, you can publish paid plans for your ap
|
|||
|
||||
To offer paid plans for your app, the app must be owned by an organization and you must have owner permissions in the organization. If your app is currently owned by a user account, you'll need to transfer the ownership of the app to an organization. For more information, see "[Transferring ownership of a GitHub App](/developers/apps/transferring-ownership-of-a-github-app)" or "[Transferring ownership of an OAuth App](/developers/apps/transferring-ownership-of-an-oauth-app)."
|
||||
|
||||
### Requesting publisher verification
|
||||
### Requesting publisher verification
|
||||
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. In the left sidebar, click **Developer settings**.
|
||||
|
||||
1. Under "Developer settings", click **Publisher Verification**.
|
||||
|
||||
1. Under "Publisher Verification", complete the information in the checklist:
|
||||
1. Under "Publisher Verification", complete the information in the checklist:
|
||||
- Ensure that your basic profile information is present and accurate. Also, make sure that you've included the best email address for support and updates from {% data variables.product.company_short %}.
|
||||
- Ensure that Two-factor authentication is enabled for your organization. For more information, see "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)."
|
||||
- Submit a verified domain and ensure that a "Verified" badge displays on your organization's profile page. For related information, see "[Verifying your organization's domain](/organizations/managing-organization-settings/verifying-your-organizations-domain)."
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ Restoring a repository will not restore release attachments or team permissions.
|
|||
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.deleted-repos %}
|
||||
{% data reusables.user_settings.restore-repo %}
|
||||
{% data reusables.user_settings.restore-confirmation %}
|
||||
|
|
|
|||
|
|
@ -39,9 +39,9 @@ When you enable access and security for a repository owned by your organization,
|
|||
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.click-codespaces %}
|
||||
5. To approve of the [pre-release program terms of service](/github/site-policy/github-pre-release-program) on behalf of your organization and enable {% data variables.product.prodname_codespaces %}, under "User permissions", select **Selected users**, then type the username for each person to grant access to. Repeat for all users who you want to have access to your organization's codespaces.
|
||||
5. To approve of the [pre-release program terms of service](/github/site-policy/github-pre-release-program) on behalf of your organization and enable {% data variables.product.prodname_codespaces %}, under "User permissions", select **Selected users**, then type the username for each person to grant access to. Repeat for all users who you want to have access to your organization's codespaces.
|
||||
|
||||
1. Under "Access and security", select the setting you want for your organization.
|
||||
|
||||
|
|
|
|||
|
|
@ -58,7 +58,7 @@ Downgrading to {% data variables.product.prodname_free_team %} for organizations
|
|||
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
5. Under "{% data variables.product.prodname_ghe_cloud %} Free Trial", click **Buy Enterprise** or **Downgrade to Team**.
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ When you disable project boards, you will no longer see project board informatio
|
|||
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
4. Decide whether to disable organization-wide project boards, disable repository project boards in the organization, or both. Then, under "Projects":
|
||||
- To disable organization-wide project boards, unselect **Enable projects for the organization**.
|
||||
- To disable repository project boards in the organization, unselect **Enable projects for all repositories**.
|
||||
|
|
|
|||
|
|
@ -42,7 +42,7 @@ Your receipts include your {% data variables.product.prodname_dotcom %} subscrip
|
|||
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.user_settings.payment-info-link %}
|
||||
{% data reusables.dotcom_billing.extra_info_receipt %}
|
||||
|
|
|
|||
|
|
@ -41,7 +41,7 @@ If your organization is outside of the US or if you're using a corporate checkin
|
|||
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.dotcom_billing.update_payment_method %}
|
||||
1. If your account has an existing credit card that you want to update, click **New Card**.
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ When you cancel a free trial on a paid plan, your subscription is immediately ca
|
|||
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.marketplace.cancel-app-billing-settings %}
|
||||
{% data reusables.marketplace.cancel-app %}
|
||||
|
|
@ -48,7 +48,7 @@ When you cancel a free trial on a paid plan, your subscription is immediately ca
|
|||
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.marketplace.cancel-free-trial-billing-settings %}
|
||||
{% data reusables.marketplace.cancel-app %}
|
||||
|
|
|
|||
|
|
@ -46,7 +46,7 @@ If you already have a personal {% data variables.product.prodname_dotcom %} user
|
|||
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.dotcom_billing.upgrade_org %}
|
||||
{% data reusables.dotcom_billing.choose_org_plan %} (You can add more seats to the organization in the next step.)
|
||||
|
|
@ -58,7 +58,7 @@ If you already have a personal {% data variables.product.prodname_dotcom %} user
|
|||
### Step 4: Upgrade the number of paid seats in the organization
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.dotcom_billing.add-seats %}
|
||||
{% data reusables.dotcom_billing.number-of-seats %}
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@ When you downgrade your number of data packs, your change takes effect on your n
|
|||
{% data reusables.dotcom_billing.org-billing-perms %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.dotcom_billing.lfs-remove-data %}
|
||||
{% data reusables.large_files.downgrade_data_packs %}
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ When you downgrade an app, your subscription remains active until the end of you
|
|||
{% data reusables.marketplace.marketplace-org-perms %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.marketplace.downgrade-app-billing-settings %}
|
||||
{% data reusables.marketplace.choose-new-plan %}
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ If you downgrade your organization from {% data variables.product.prodname_team
|
|||
If you downgrade your organization from {% data variables.product.prodname_ghe_cloud %} to {% data variables.product.prodname_team %} or {% data variables.product.prodname_free_team %}, the account will lose access to advanced security, compliance, and deployment controls. {% data reusables.gated-features.more-info %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
1. Under "Current plan", use the **Edit** drop-down and click the downgrade option you want.
|
||||
|
||||
|
|
@ -60,7 +60,7 @@ If you downgrade your organization from {% data variables.product.prodname_ghe_c
|
|||
{% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see "[Switching your organization from per-repository to per-user pricing](/github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)."
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
5. Under "Subscriptions", select the "Edit" drop-down, and click **Edit plan**.
|
||||
|
||||
|
|
@ -77,7 +77,7 @@ To reduce the number of paid seats your organization uses, you can remove member
|
|||
- "[Managing an individual's access to an organization repository](/articles/managing-an-individual-s-access-to-an-organization-repository)"
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
1. Under "Current plan", use the **Edit** drop-down and click **Remove seats**.
|
||||
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ Anyone can manage the spending limit for {% data variables.product.prodname_acti
|
|||
Organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_actions %} for an organization.
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.dotcom_billing.manage-spending-limit %}
|
||||
{% data reusables.dotcom_billing.monthly-spending-limit %}
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ Anyone can manage the spending limit for {% data variables.product.prodname_regi
|
|||
Organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_registry %} for an organization.
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.dotcom_billing.manage-spending-limit %}
|
||||
{% data reusables.dotcom_billing.monthly-spending-limit %}
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ If you're paying for your {% data variables.product.product_name %} subscription
|
|||
{% data reusables.dotcom_billing.org-billing-perms %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.user_settings.payment-info-link %}
|
||||
{% data reusables.dotcom_billing.remove-payment-method %}
|
||||
|
|
|
|||
|
|
@ -21,9 +21,9 @@ topics:
|
|||
### Updating your organization's credit card
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.dotcom_billing.update_payment_method %}
|
||||
1. Under "Payment method", click **New Card**.
|
||||
1. Under "Payment method", click **New Card**.
|
||||
|
||||
{% data reusables.dotcom_billing.enter-payment-info %}
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ Your organization's billing email is where {% data variables.product.product_nam
|
|||
{% data reusables.dotcom_billing.org-billing-perms %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
4. Under **Billing email**, type a valid email address. The email does not need to be unique to the organization account.
|
||||
|
||||
5. To confirm your changes, click **Update profile**.
|
||||
|
|
@ -42,7 +42,7 @@ If you have users that want to receive billing reports, you can add their email
|
|||
#### Adding a recipient for billing notifications
|
||||
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
1. Under "Billing management", to the right of "Email recipients", click **Add**.
|
||||
|
||||
|
|
@ -54,7 +54,7 @@ If you have users that want to receive billing reports, you can add their email
|
|||
One address must always be designated as the primary recipient. The address with this designation can't be removed until a new primary recipient is selected.
|
||||
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
1. Under "Billing management", find the email address you want to set as the primary recipient.
|
||||
1. To the right of the email address, use the "Edit" drop-down menu, and click **Mark as primary**.
|
||||
|
|
@ -63,7 +63,7 @@ One address must always be designated as the primary recipient. The address with
|
|||
#### Removing a recipient from billing notifications
|
||||
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
1. Under "Email recipients", find the email address you want to remove.
|
||||
1. For the user's entry in the list, click **Edit**.
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ topics:
|
|||
{% data reusables.dotcom_billing.org-billing-perms %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.dotcom_billing.lfs-add-data %}
|
||||
{% data reusables.large_files.pack_selection %}
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ topics:
|
|||
### Upgrading an organization's number of paid seats
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.dotcom_billing.add-seats %}
|
||||
{% data reusables.dotcom_billing.number-of-seats %}
|
||||
|
|
@ -34,7 +34,7 @@ After you add seats, the payment method on file for the organization will be cha
|
|||
### Downgrading an organization's number of paid seats to free
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.dotcom_billing.downgrade-org-to-free %}
|
||||
{% data reusables.dotcom_billing.confirm_cancel_org_plan %}
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ When you upgrade an app, your payment method is charged a prorated amount based
|
|||
{% data reusables.marketplace.marketplace-org-perms %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.marketplace.upgrade-app-billing-settings %}
|
||||
{% data reusables.marketplace.choose-new-plan %}
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ You can upgrade your organization from {% data variables.product.prodname_free_t
|
|||
{% data reusables.dotcom_billing.org-billing-perms %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.dotcom_billing.upgrade_org %}
|
||||
{% data reusables.dotcom_billing.choose_org_plan %}
|
||||
|
|
@ -65,7 +65,7 @@ If you'd like to use an enterprise account with {% data variables.product.prodna
|
|||
If you'd like additional users to have access to your {% data variables.product.prodname_team %} organization's private repositories, you can purchase more seats anytime.
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.dotcom_billing.add-seats %}
|
||||
{% data reusables.dotcom_billing.number-of-seats %}
|
||||
|
|
@ -76,7 +76,7 @@ If you'd like additional users to have access to your {% data variables.product.
|
|||
{% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see "[About per-user pricing](/articles/about-per-user-pricing)."
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
5. To the right of your plan name, use the **Edit** drop-down menu, and select **Edit plan**.
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ When you cancel a pending change, your subscription will not change on your next
|
|||
### Viewing and managing pending changes to your organization's subscription
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.dotcom_billing.review-pending-changes %}
|
||||
{% data reusables.dotcom_billing.cancel-pending-changes %}
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ topics:
|
|||
{% data reusables.dotcom_billing.org-billing-perms %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.dotcom_billing.lfs-data %}
|
||||
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@ Anyone can view {% data variables.product.prodname_actions %} usage for their ow
|
|||
Organization owners and billing managers can view {% data variables.product.prodname_actions %} usage for an organization. For organizations managed by an enterprise account, only the organization owners can view {% data variables.product.prodname_actions %} usage in the organization billing page.
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.dotcom_billing.actions-minutes %}
|
||||
{% data reusables.dotcom_billing.actions-packages-storage %}
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ Anyone can view {% data variables.product.prodname_registry %} usage for their o
|
|||
Organization owners and billing managers can view {% data variables.product.prodname_registry %} usage for an organization. For organizations managed by an enterprise account, only the organization owners can view {% data variables.product.prodname_registry %} usage in the organization billing page.
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.dotcom_billing.packages-data %}
|
||||
{% data reusables.dotcom_billing.actions-packages-storage %}
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ topics:
|
|||
{% data reusables.dotcom_billing.org-billing-perms %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.dotcom_billing.view-payment-history %}
|
||||
{% data reusables.dotcom_billing.download_receipt %}
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ topics:
|
|||
{% data reusables.dotcom_billing.org-billing-perms %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
{% data reusables.dotcom_billing.next_billing_date %}
|
||||
|
||||
|
|
|
|||
|
|
@ -29,4 +29,4 @@ topics:
|
|||
{% endif %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ topics:
|
|||
---
|
||||
|
||||
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 %}
|
||||
|
|
@ -27,7 +27,7 @@ You can also configure allowed IP addresses for the organizations in an enterpri
|
|||
### Adding an allowed IP address
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.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 %}
|
||||
|
|
@ -36,7 +36,7 @@ You can also configure allowed IP addresses for the organizations in an enterpri
|
|||
### Enabling allowed IP addresses
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
3. Under "IP allow list", select **Enable IP allow list**.
|
||||
|
||||
|
|
@ -45,7 +45,7 @@ You can also configure allowed IP addresses for the organizations in an enterpri
|
|||
### Editing an allowed IP address
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.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 %}
|
||||
|
|
@ -55,7 +55,7 @@ You can also configure allowed IP addresses for the organizations in an enterpri
|
|||
### Deleting an allowed IP address
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.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 %}
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ topics:
|
|||
### Displaying the security and analysis settings
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security-and-analysis %}
|
||||
|
||||
The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization.
|
||||
|
|
@ -45,7 +45,7 @@ You can enable or disable features for all repositories. {% if currentVersion ==
|
|||
- **{% data variables.product.prodname_GH_advanced_security %}** - Your changes affect only private repositories because {% data variables.product.prodname_GH_advanced_security %} and the related features are always enabled for public repositories.
|
||||
- **{% data variables.product.prodname_secret_scanning_caps %}** - Your changes affect only private repositories where {% data variables.product.prodname_GH_advanced_security %} is also enabled. {% data variables.product.prodname_secret_scanning_caps %} is always enabled for public repositories.{% endif %}
|
||||
|
||||
{% data reusables.advanced-security.note-org-enable-uses-seats %}
|
||||
{% data reusables.advanced-security.note-org-enable-uses-seats %}
|
||||
|
||||
1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)."
|
||||
2. Under "Configure security and analysis features", to the right of the feature, click **Disable all** or **Enable all**. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %}The control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled if you have no available seats in your {% data variables.product.prodname_GH_advanced_security %} license.{% endif %}
|
||||
|
|
@ -112,7 +112,7 @@ To allow {% data variables.product.prodname_dependabot %} to access a private {%
|
|||
|
||||
1. Start typing the name of the repository you want to allow.
|
||||
|
||||
1. Click the repository you want to allow.
|
||||
1. Click the repository you want to allow.
|
||||
|
||||
1. Optionally, to remove a repository from the list, to the right of the repository, click {% octicon "x" aria-label="The X icon" %}.
|
||||
|
||||
|
|
|
|||
|
|
@ -43,7 +43,7 @@ Before you require use of two-factor authentication, we recommend notifying {% i
|
|||
### Requiring two-factor authentication in your organization
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
{% data reusables.organizations.require_two_factor_authentication %}
|
||||
{% data reusables.organizations.removed_outside_collaborators %}
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ If your organization is owned by an enterprise account, organization members wil
|
|||
### Restricting email notifications to an approved domain
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.verified-domains %}
|
||||
{% data reusables.organizations.restrict-email-notifications %}
|
||||
6. Click **Save**.
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ topics:
|
|||
The audit log lists events triggered by activities that affect your organization within the last 90 days. Only owners can access an organization's audit log.
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.audit_log.audit_log_sidebar_for_org_admins %}
|
||||
|
||||
### Searching the audit log
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ topics:
|
|||
---
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
4. In the left sidebar, click **Installed {% data variables.product.prodname_github_app %}s**.
|
||||
|
||||
5. Next to the {% data variables.product.prodname_github_app %} you'd like to review, click **Configure**.
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ For more information about {% data variables.product.prodname_github_app %} mana
|
|||
### Giving someone the ability to manage all {% data variables.product.prodname_github_app %}s owned by the organization
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.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**.
|
||||
|
||||
|
|
@ -26,7 +26,7 @@ For more information about {% data variables.product.prodname_github_app %} mana
|
|||
### Giving someone the ability to manage an individual {% data variables.product.prodname_github_app %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.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.
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ For more information about {% data variables.product.prodname_github_app %} mana
|
|||
### Removing a {% data variables.product.prodname_github_app %} manager's permissions for the entire organization
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.github-apps-settings-sidebar %}
|
||||
1. Under "Management", find the username of the person you want to remove {% data variables.product.prodname_github_app %} manager permissions from, and click **Revoke**.
|
||||
|
||||
|
|
@ -26,7 +26,7 @@ For more information about {% data variables.product.prodname_github_app %} mana
|
|||
### Removing a {% data variables.product.prodname_github_app %} manager's permissions for an individual {% data variables.product.prodname_github_app %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.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 remove a {% data variables.product.prodname_github_app %} manager from.
|
||||
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ If someone with admin permissions to an organization's repository grants a membe
|
|||
### Setting base permissions
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.member-privileges %}
|
||||
5. Under "Base permissions", use the drop-down to select new base permissions.
|
||||
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ You can allow members to access your organization's repositories using SSH certi
|
|||
{% data reusables.organizations.add-extension-to-cert %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
{% data reusables.organizations.new-ssh-ca %}
|
||||
{% data reusables.organizations.require-ssh-cert %}
|
||||
|
|
@ -31,6 +31,6 @@ You can allow members to access your organization's repositories using SSH certi
|
|||
### Deleting an SSH certificate authority
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
{% data reusables.organizations.delete-ssh-ca %}
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ By default, issues cannot be deleted in an organization's repositories. An organ
|
|||
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_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.member-privileges %}
|
||||
5. Under "Issue deletion", select **Allow members to delete issues for this organization**.
|
||||
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ Organization owners can set limitations for viewing organization dependency insi
|
|||
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_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.member-privileges %}
|
||||
5. Under "Member organization permissions", select or unselect **Allow members to view dependency insights**.
|
||||
|
||||
|
|
|
|||
|
|
@ -29,6 +29,6 @@ Once you delete an organization, GitHub **cannot restore your content**. Therefo
|
|||
### 2. Delete the organization
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
4. Near the bottom of the organization's settings page, click **Delete this Organization**.
|
||||
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ Alternatively, you can enable {% data variables.product.prodname_actions %} for
|
|||
### Managing {% data variables.product.prodname_actions %} permissions for your organization
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.settings-sidebar-actions %}
|
||||
1. Under **Local and third-party Actions**, select an option.
|
||||
|
||||
|
|
@ -40,7 +40,7 @@ Alternatively, you can enable {% data variables.product.prodname_actions %} for
|
|||
|
||||
### 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.
|
||||
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 %}
|
||||
|
||||
|
|
@ -51,7 +51,7 @@ You can disable all workflows for an organization or set a policy that configure
|
|||
{% endnote %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.settings-sidebar-actions %}
|
||||
1. Under **Policies**, select an option.
|
||||
|
||||
|
|
@ -62,7 +62,7 @@ You can disable all workflows for an organization or set a policy that configure
|
|||
{% data reusables.actions.allow-specific-actions-intro %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.settings-sidebar-actions %}
|
||||
1. Under **Policies**, select **Allow select actions** and add your required actions to the list.
|
||||
|
||||
|
|
@ -78,7 +78,7 @@ You can disable all workflows for an organization or set a policy that configure
|
|||
#### Configuring the private fork policy for an organization
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.settings-sidebar-actions %}
|
||||
{% data reusables.github-actions.private-repository-forks-configure %}
|
||||
{% endif %}
|
||||
|
|
@ -96,7 +96,7 @@ You can set the default permissions for the `GITHUB_TOKEN` in the settings for y
|
|||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.settings-sidebar-actions %}
|
||||
1. Under **Workflow permissions**, choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope.
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ Default labels are included in every new repository in your organization, but an
|
|||
### Creating a default label
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
|
||||
{% data reusables.organizations.repository-defaults %}
|
||||
{% else %}
|
||||
|
|
@ -36,7 +36,7 @@ Default labels are included in every new repository in your organization, but an
|
|||
### Editing a default label
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
|
||||
{% data reusables.organizations.repository-defaults %}
|
||||
{% else %}
|
||||
|
|
@ -51,7 +51,7 @@ Default labels are included in every new repository in your organization, but an
|
|||
### Deleting a default label
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %}
|
||||
{% data reusables.organizations.repository-defaults %}
|
||||
{% else %}
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ topics:
|
|||
By default, organization members with read access can create discussions if a repository administrator or organization owner enables discussions for a repository owned by the organization.
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.member-privileges %}
|
||||
5. Under "Repository discussions", select or deselect **Allow users with read access to create discussions**.
|
||||
|
||||
|
|
|
|||
|
|
@ -14,13 +14,13 @@ topics:
|
|||
|
||||
{% data reusables.reminders.about-scheduled-reminders-teams-orgs %}
|
||||
|
||||
Organization owners can schedule a reminder for one or more teams in their organization, for all pull requests the team or teams have been requested to review.
|
||||
Organization owners can schedule a reminder for one or more teams in their organization, for all pull requests the team or teams have been requested to review.
|
||||
|
||||
{% data reusables.reminders.scheduled-reminders-limitations %}
|
||||
|
||||
### Creating a scheduled reminder for an organization
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.reminders.scheduled-reminders %}
|
||||
|
||||
{% data reusables.reminders.add-reminder %}
|
||||
|
|
@ -29,7 +29,7 @@ Organization owners can schedule a reminder for one or more teams in their organ
|
|||
{% data reusables.reminders.days-dropdown %}
|
||||
{% data reusables.reminders.times-dropdowns %}
|
||||
{% data reusables.reminders.tracked-repos %}
|
||||
11. Under "Filter by team assigned to review code", click the **Add a team** dropdown and choose one or more teams. You can add up to 100 teams. If the team you select doesn't have access to the "Tracked repositories" selected above, you won't be able to create the scheduled reminder.
|
||||
11. Under "Filter by team assigned to review code", click the **Add a team** dropdown and choose one or more teams. You can add up to 100 teams. If the team you select doesn't have access to the "Tracked repositories" selected above, you won't be able to create the scheduled reminder.
|
||||
|
||||
{% data reusables.reminders.ignore-drafts %}
|
||||
{% data reusables.reminders.no-review-requests %}
|
||||
|
|
@ -44,7 +44,7 @@ Organization owners can schedule a reminder for one or more teams in their organ
|
|||
|
||||
### Managing a scheduled reminder for an organization
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.reminders.scheduled-reminders %}
|
||||
|
||||
{% data reusables.reminders.edit-existing %}
|
||||
|
|
@ -53,7 +53,7 @@ Organization owners can schedule a reminder for one or more teams in their organ
|
|||
|
||||
### Deleting a scheduled reminder for an organization
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.reminders.scheduled-reminders %}
|
||||
|
||||
{% data reusables.reminders.delete %}
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ If an enterprise owner has enforced a policy for the default branch name for you
|
|||
### Setting the default branch name
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.repository-defaults %}
|
||||
3. Under "Repository default branch", click **Change default branch name now**.
|
||||
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ Organization owners can manage the display of member names in an organization.
|
|||
Each organization member chooses their own profile name in their settings. For more information, see "[Personalizing your profile](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#changing-your-profile-name)."
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.member-privileges %}
|
||||
5. Under "Admin repository permissions", select or unselect **Allow members to see comment author's profile name in private repositories**.
|
||||
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ If you allow forking of private{% if currentVersion == "free-pro-team@latest" or
|
|||
{% data reusables.organizations.internal-repos-enterprise %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.member-privileges %}
|
||||
5. Under "Repository forking", select **Allow forking of private repositories** or **Allow forking of private and internal repositories**.
|
||||
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ If your organization uses {% data variables.product.prodname_ghe_cloud %}, you c
|
|||
If you disallow publication of {% data variables.product.prodname_pages %} sites, any sites that are already published will remain published. You can manually unpublish the site. For more information, see "[Unpublishing a {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site)."
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.member-privileges %}{% if currentVersion == "free-pro-team@latest" %}
|
||||
1. Under "Pages creation", select the visibilities you want to allow and deselect the visibilities you want to disallow.
|
||||
{% else %}
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ The developers and organizations that your organization sponsors can send you up
|
|||
You can also disable updates from accounts your organization sponsors. For more information, see "[Managing your sponsorship](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship#managing-email-updates-for-your-sponsorship)."
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
1. Under "Sponsors update email (Private)", type the email address you want to receive updates from accounts your organization sponsors.
|
||||
|
||||
1. Click **Update profile**.
|
||||
|
|
|
|||
|
|
@ -41,7 +41,7 @@ After changing your organization's name:
|
|||
### Changing your organization's name
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
4. Near the bottom of the settings page, under "Rename organization", click **Rename Organization**.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ Organization owners can always create any type of repository.
|
|||
{% data reusables.organizations.internal-repos-enterprise %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.member-privileges %}
|
||||
5. Under "Repository creation", select one or more options.
|
||||
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ You can restrict the ability to change repository visibility to organization own
|
|||
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.member-privileges %}
|
||||
5. Under "Repository visibility change", deselect **Allow members to change repository visibilities for this organization**.
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ Organization owners, and members with admin privileges for a repository, can inv
|
|||
{% data reusables.organizations.outside-collaborators-use-seats %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.member-privileges %}
|
||||
5. Under "Repository invitations", select **Allow members to invite outside collaborators to repositories for this organization**.{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}
|
||||
{% else %}
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ topics:
|
|||
Owners can set permissions for deleting or transferring repositories in an organization.
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.member-privileges %}
|
||||
5. Under "Repository deletion and transfer", select or deselect **Allow members to delete or transfer repositories for this organization**.
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ Organization owners can set team creation permissions.
|
|||
If you do not set team creation permissions, all organization members will be able to create teams by default.
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.member-privileges %}
|
||||
5. Under "Team creation rules", select or deselect **Allow members to create teams**.
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ On {% data variables.product.prodname_ghe_cloud %}, after verifying ownership of
|
|||
### Verifying your organization's domain
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.verified-domains %}
|
||||
5. Click **Add a domain**.
|
||||
|
||||
|
|
|
|||
|
|
@ -50,7 +50,7 @@ Billing managers **are not** able to:
|
|||
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_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
1. Under "Billing management", next to "Billing managers", click **Add**.
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ topics:
|
|||
{% endwarning %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
1. In the "Billing managers" list under "Billing management", next to the name of the person you want to remove, click **Remove**.
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ topics:
|
|||
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_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
5. Under "SAML single sign-on", in the note about recovery codes, click **Save your recovery codes**.
|
||||
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ If you enable but don't enforce SAML SSO, organization members who choose not to
|
|||
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_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
5. Under "SAML single sign-on", select **Enable SAML authentication**.
|
||||
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ You must authenticate to your organization using SAML SSO and the supported IdP.
|
|||
{% data reusables.identity-and-permissions.team-sync-azure-permissions %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
{% data reusables.identity-and-permissions.team-sync-confirm-saml %}
|
||||
{% data reusables.identity-and-permissions.enable-team-sync-azure %}
|
||||
|
|
@ -60,7 +60,7 @@ You must authenticate to your organization using SAML SSO and the supported IdP.
|
|||
{% data reusables.identity-and-permissions.team-sync-okta-requirements %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
{% data reusables.identity-and-permissions.team-sync-confirm-saml %}
|
||||
{% data reusables.identity-and-permissions.enable-team-sync-okta %}
|
||||
|
|
@ -74,7 +74,7 @@ You must authenticate to your organization using SAML SSO and the supported IdP.
|
|||
{% data reusables.identity-and-permissions.team-sync-disable %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
5. Under "Team synchronization", click **Disable team synchronization**.
|
||||
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ For more information, see "[Repository permission levels for an organization](/a
|
|||
### Migrating all of your organization's legacy admin teams
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.teams_sidebar %}
|
||||
1. Review your organization's legacy admin teams, then click **Migrate all teams**.
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ topics:
|
|||
{% data reusables.organizations.team-discussions-default %} For more information on team discussions, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)."
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.teams_sidebar %}
|
||||
5. Under "Team discussions", unselect **Enable team discussions for this organization**.
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ topics:
|
|||
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_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.oauth_app_access %}
|
||||
5. Next to the application you'd like to approve, click **Review**.
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ topics:
|
|||
---
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.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" %}.
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ topics:
|
|||
{% enddanger %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.oauth_app_access %}
|
||||
5. Click **Remove restrictions**.
|
||||
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ topics:
|
|||
{% endwarning %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.oauth_app_access %}
|
||||
5. Under "Third-party application access policy," click **Setup application access restrictions**.
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
title: Configuring access control and visibility for container images
|
||||
intro: 'Choose who has read, write, or admin access to your container image and the visibility of your container images on {% data variables.product.prodname_dotcom %}.'
|
||||
product: '{% data reusables.gated-features.packages %}'
|
||||
redirect_from:
|
||||
redirect_from:
|
||||
- /packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
|
|
@ -50,9 +50,9 @@ Once a repository is synced, you can't access the package's granular access sett
|
|||
2. Under "Repository source", select **Inherit access from repository (recommended)**.
|
||||
|
||||
|
||||
### Ensuring workflow access to your package
|
||||
### Ensuring workflow access to your package
|
||||
|
||||
To ensure that a {% data variables.product.prodname_actions %} workflow has access to your package, you must give explicit access to the repository where the workflow is stored.
|
||||
To ensure that a {% data variables.product.prodname_actions %} workflow has access to your package, you must give explicit access to the repository where the workflow is stored.
|
||||
|
||||
The specified repository does not need to be the repository where the source code for the package is kept. You can give multiple repositories workflow access to a package.
|
||||
|
||||
|
|
@ -63,7 +63,7 @@ The specified repository does not need to be the repository where the source cod
|
|||
{% endnote %}
|
||||
|
||||
{% data reusables.package_registry.package-settings-from-org-level %}
|
||||
1. In the left sidebar, click **Actions access**.
|
||||
1. In the left sidebar, click **Actions access**.
|
||||
|
||||
2. Click **Add repository** and search for the repository you want to add.
|
||||
|
||||
|
|
@ -94,11 +94,11 @@ A public package can be accessed anonymously without authentication. Once you ma
|
|||
You can choose the visibility of containers that organization members can publish by default.
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
4. On the left, click **Packages**.
|
||||
6. Under "Container creation", choose whether you want to enable the creation of public, private, or internal container images.
|
||||
- To enable organization members to create public container images, click **Public**.
|
||||
- To enable organization members to create private container images that are only visible to other organization members, click **Private**. You can further customize the visibility of private container images.
|
||||
- To enable organization members to create private container images that are only visible to other organization members, click **Private**. You can further customize the visibility of private container images.
|
||||
- **For {% data variables.product.prodname_ghe_cloud %} only:** To enable organization members to create internal container images that are only visible to other organization members, click **Internal**.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
title: Enabling improved container support
|
||||
intro: 'To use {% data variables.product.prodname_github_container_registry %}, you must enable it for your user or organization account.'
|
||||
product: '{% data reusables.gated-features.packages %}'
|
||||
redirect_from:
|
||||
redirect_from:
|
||||
- /packages/getting-started-with-github-container-registry/enabling-improved-container-support
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
|
|
@ -29,7 +29,7 @@ To use {% data variables.product.prodname_github_container_registry %} within an
|
|||
Before organization owners or members can publish container images to {% data variables.product.prodname_github_container_registry %}, an organization owner must enable the feature preview for the organization.
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
4. On the left, click **Packages**.
|
||||
5. Under "Improved container support", select "Enable improved container support" and click **Save**.
|
||||
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче