Make images accessible in the `images/help/organizations` directory (3/4) (#36113)
Co-authored-by: Sophie <29382425+sophietheking@users.noreply.github.com>
Двоичные данные
assets/images/help/organizations/Organization-add-team.png
До Ширина: | Высота: | Размер: 22 KiB |
Двоичные данные
assets/images/help/organizations/integration-access-requests.png
До Ширина: | Высота: | Размер: 10 KiB |
До Ширина: | Высота: | Размер: 110 KiB |
Двоичные данные
assets/images/help/organizations/list-of-organizations.png
До Ширина: | Высота: | Размер: 15 KiB |
Двоичные данные
assets/images/help/organizations/member-privileges.png
До Ширина: | Высота: | Размер: 21 KiB |
Двоичные данные
assets/images/help/organizations/member-search-box.png
До Ширина: | Высота: | Размер: 6.0 KiB |
Двоичные данные
assets/images/help/organizations/member-visibility-link.png
До Ширина: | Высота: | Размер: 38 KiB После Ширина: | Высота: | Размер: 48 KiB |
Двоичные данные
assets/images/help/organizations/member_only_profile.png
До Ширина: | Высота: | Размер: 185 KiB |
Двоичные данные
assets/images/help/organizations/name-of-business.png
До Ширина: | Высота: | Размер: 16 KiB |
Двоичные данные
assets/images/help/organizations/new-label-button.png
До Ширина: | Высота: | Размер: 10 KiB |
Двоичные данные
assets/images/help/organizations/new-org-name.png
До Ширина: | Высота: | Размер: 9.0 KiB |
Двоичные данные
assets/images/help/organizations/org_member_readme.png
До Ширина: | Высота: | Размер: 1.2 MiB |
Двоичные данные
assets/images/help/organizations/org_public_readme.png
До Ширина: | Высота: | Размер: 1.5 MiB |
До Ширина: | Высота: | Размер: 151 KiB |
Двоичные данные
assets/images/help/organizations/organization-add-owner.png
До Ширина: | Высота: | Размер: 36 KiB |
До Ширина: | Высота: | Размер: 37 KiB |
Двоичные данные
assets/images/help/organizations/organization-belongs-to.png
До Ширина: | Высота: | Размер: 5.5 KiB |
До Ширина: | Высота: | Размер: 37 KiB |
До Ширина: | Высота: | Размер: 74 KiB |
До Ширина: | Высота: | Размер: 72 KiB |
До Ширина: | Высота: | Размер: 21 KiB |
Двоичные данные
assets/images/help/organizations/organization-settings-tab.png
До Ширина: | Высота: | Размер: 40 KiB После Ширина: | Высота: | Размер: 60 KiB |
До Ширина: | Высота: | Размер: 497 KiB После Ширина: | Высота: | Размер: 154 KiB |
Двоичные данные
assets/images/help/organizations/public_profile.png
До Ширина: | Высота: | Размер: 174 KiB |
До Ширина: | Высота: | Размер: 22 KiB |
Двоичные данные
assets/images/help/organizations/repository-role-create-role.png
До Ширина: | Высота: | Размер: 12 KiB |
До Ширина: | Высота: | Размер: 8.2 KiB |
До Ширина: | Высота: | Размер: 66 KiB |
До Ширина: | Высота: | Размер: 36 KiB |
Двоичные данные
assets/images/help/organizations/repository-role-description.png
До Ширина: | Высота: | Размер: 20 KiB |
Двоичные данные
assets/images/help/organizations/repository-role-drop-down.png
До Ширина: | Высота: | Размер: 36 KiB |
До Ширина: | Высота: | Размер: 32 KiB После Ширина: | Высота: | Размер: 40 KiB |
Двоичные данные
assets/images/help/organizations/repository-role-name.png
До Ширина: | Высота: | Размер: 28 KiB |
Двоичные данные
assets/images/help/organizations/repository-role-update.png
До Ширина: | Высота: | Размер: 8.3 KiB |
Двоичные данные
assets/images/help/organizations/require-2fa-checkbox.png
До Ширина: | Высота: | Размер: 43 KiB |
Двоичные данные
assets/images/help/organizations/require-signoffs.png
До Ширина: | Высота: | Размер: 10 KiB |
Двоичные данные
assets/images/help/organizations/require-ssh-cert.png
До Ширина: | Высота: | Размер: 35 KiB |
Двоичные данные
assets/images/help/organizations/retry-invitation-pop-up.png
До Ширина: | Высота: | Размер: 34 KiB |
Двоичные данные
assets/images/help/organizations/retry-or-cancel-invitation.png
До Ширина: | Высота: | Размер: 70 KiB После Ширина: | Высота: | Размер: 52 KiB |
До Ширина: | Высота: | Размер: 62 KiB |
Двоичные данные
assets/images/help/organizations/team-project-add-project.png
До Ширина: | Высота: | Размер: 8.9 KiB |
Двоичные данные
assets/images/help/organizations/team-project-board-button.png
До Ширина: | Высота: | Размер: 9.3 KiB После Ширина: | Высота: | Размер: 34 KiB |
Двоичные данные
assets/images/help/organizations/team-project-search.png
До Ширина: | Высота: | Размер: 12 KiB |
Двоичные данные
assets/images/help/organizations/team-repositories-button.png
До Ширина: | Высота: | Размер: 6.5 KiB |
Двоичные данные
assets/images/help/organizations/trash-button.png
До Ширина: | Высота: | Размер: 21 KiB |
Двоичные данные
assets/images/help/organizations/update-profile-button.png
До Ширина: | Высота: | Размер: 3.9 KiB |
Двоичные данные
assets/images/help/organizations/verified-badge.png
До Ширина: | Высота: | Размер: 35 KiB |
Двоичные данные
assets/images/help/settings/convert-to-organization.png
До Ширина: | Высота: | Размер: 2.8 KiB |
|
@ -22,9 +22,10 @@ shortTitle: Show or hide membership
|
|||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.people %}
|
||||
4. Locate your username in the list of members. If the list is large, you can search for your username in the search box.
|
||||
![Organization member search box](/assets/images/help/organizations/member-search-box.png)
|
||||
5. In the menu to the right of your username, choose a new visibility option:
|
||||
1. Locate your username in the list of members. If the list is large, you can search for your username in the search box.
|
||||
1. Next to your username, select the visibility dropdown menu, then click a new visibility.
|
||||
|
||||
- To publicize your membership, choose **Public**.
|
||||
- To hide your membership, choose **Private**.
|
||||
![Organization member visibility link](/assets/images/help/organizations/member-visibility-link.png)
|
||||
|
||||
![Screenshot of an entry in the list of organization members. To the right of the username, a dropdown menu, labeled "Private", is outlined in dark orange.](/assets/images/help/organizations/member-visibility-link.png)
|
||||
|
|
|
@ -48,27 +48,22 @@ You can also convert your personal account directly into an organization. Conver
|
|||
- Automatically invites collaborators to teams with permissions equivalent to what they had before
|
||||
{% ifversion fpt or ghec %}- For personal accounts on {% data variables.product.prodname_pro %}, automatically transitions billing to [the paid {% data variables.product.prodname_team %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) without the need to re-enter payment information, adjust your billing cycle, or double pay at any time{% endif %}
|
||||
|
||||
When you convert a personal account into an organization, we'll add collaborators on repositories that belong to the account to the new organization as outside collaborators. You can then invite outside collaborators to become members of your new organization if you wish. For more information, see "[AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
|
||||
|
||||
1. Create a new personal account, which you'll use to sign into GitHub and access the organization and your repositories after you convert.
|
||||
2. [Leave any organizations](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization) the personal account you're converting has joined.
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.organizations %}
|
||||
5. Under "Transform account", click **Turn <username> into an organization**.
|
||||
![Organization conversion button](/assets/images/help/settings/convert-to-organization.png)
|
||||
6. In the Account Transformation Warning dialog box, review and confirm the conversion. Note that the information in this box is the same as the warning at the top of this article.
|
||||
![Conversion warning](/assets/images/help/organizations/organization-account-transformation-warning.png)
|
||||
7. On the "Transform your user into an organization" page, under "Choose an organization owner", choose either the secondary personal account you created in the previous section or another user you trust to manage the organization.
|
||||
![Add organization owner page](/assets/images/help/organizations/organization-add-owner.png)
|
||||
8. Choose your new organization's subscription and enter your billing information if prompted.
|
||||
9. Click **Create Organization**.
|
||||
10. Sign in to the new personal account you created in step one, then use the context switcher to access your new organization.
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip**: When you convert a personal account into an organization, we'll add collaborators on repositories that belong to the account to the new organization as *outside collaborators*. You can then invite *outside collaborators* to become members of your new organization if you wish. For more information, see "[AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
|
||||
|
||||
{% endtip %}
|
||||
1. In the "Transform account" section, click **Turn USERNAME into an organization**.
|
||||
1. Review the warning, then click **Turn USERNAME into an organization**.
|
||||
1. Under "Choose an organization owner", type either the secondary personal account you created in the previous section, or another user you trust, to manage the organization.
|
||||
1. Choose your new organization's subscription and enter your billing information, if prompted.
|
||||
1. Click **Create Organization**.
|
||||
1. Sign in to the new personal account you created earlier, then use the context switcher to access your new organization.
|
||||
|
||||
## Further reading
|
||||
- "[AUTOTITLE](/organizations/organizing-members-into-teams)"
|
||||
{% ifversion fpt or ghec %}- "[AUTOTITLE](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)"{% endif %}
|
||||
{% ifversion fpt or ghec %}
|
||||
- "[AUTOTITLE](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)"
|
||||
{% endif %}
|
||||
- "[AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/accessing-an-organization)"
|
||||
|
|
|
@ -69,7 +69,6 @@ To verify your enterprise account's domain, you must have access to modify domai
|
|||
1. After confirming your TXT record is added to your DNS, follow steps one through four above to navigate to your enterprise account's approved and verified domains.
|
||||
{% data reusables.enterprise-accounts.continue-verifying-domain %}
|
||||
1. Optionally, after the "Verified" badge is visible on your organizations' profiles, delete the TXT entry from the DNS record at your domain hosting service.
|
||||
![Verified badge](/assets/images/help/organizations/verified-badge.png)
|
||||
|
||||
## Approving a domain for your enterprise account
|
||||
|
||||
|
|
|
@ -22,36 +22,30 @@ Teams are granted read permissions on any project they are added to. This permis
|
|||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.specific_team %}
|
||||
1. Click {% octicon "project" aria-label="The Projects icon" %} **Projects**.
|
||||
|
||||
![Screenshot showing the team projects tab.](/assets/images/help/organizations/team-project-board-button.png)
|
||||
|
||||
1. Click **Add project**.
|
||||
|
||||
![Screenshot showing the "Add project" button.](/assets/images/help/organizations/team-project-add-project.png)
|
||||
|
||||
1. Start typing the name of the project you want to add and then select the project in the list of matches.
|
||||
|
||||
1. Click {% octicon "project" aria-hidden="true" %} **Projects**.
|
||||
|
||||
![Screenshot of the main page for a team. In the horizontal navigation bar, the "Projects" tab is outlined in dark orange.](/assets/images/help/organizations/team-project-board-button.png)
|
||||
|
||||
1. Click **Link a project**.
|
||||
1. In the search field, start typing the name of the project you want to add and then select the project in the list of matches.
|
||||
|
||||
{% note %}
|
||||
|
||||
|
||||
**Note:** If this change will result in increased project permissions for the team's members, {% data variables.product.product_name %} will prompt you to confirm your choice.
|
||||
|
||||
|
||||
{% endnote %}
|
||||
|
||||
![Screenshot showing the "Add project" form.](/assets/images/help/organizations/team-project-search.png)
|
||||
|
||||
|
||||
## Removing a project from a team
|
||||
|
||||
{% data reusables.projects.project-settings %}
|
||||
1. Click **Manage access**.
|
||||
|
||||
|
||||
![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png)
|
||||
|
||||
|
||||
1. Next to the team that you want to remove from the project, click **Remove**.
|
||||
|
||||
|
||||
![Screenshot showing removing a collaborator](/assets/images/help/projects-v2/access-remove-member.png)
|
||||
|
||||
|
||||
|
||||
{% ifversion projects-v1 %}
|
||||
|
||||
|
|
|
@ -16,16 +16,12 @@ shortTitle: Customize organization profile
|
|||
{% ifversion org-profile-pin-private %}
|
||||
You can customize your organization's Overview page to show a README and pinned repositories dedicated to public users or members of the organization.
|
||||
|
||||
![Image of a public organization profile page](/assets/images/help/organizations/public_profile.png)
|
||||
|
||||
Members of your organization who are signed into {% data variables.product.prodname_dotcom %}, can select a `member` or `public` view of the README and pinned repositories when they visit your organization's profile page.
|
||||
|
||||
![Image of a public organization profile page view context switcher](/assets/images/help/organizations/profile_view_switcher_public.png)
|
||||
![Image of an organization's profile page. In the right sidebar, a dropdown menu, labeled "View as: Public", is outlined in dark orange.](/assets/images/help/organizations/profile_view_switcher_public.png)
|
||||
|
||||
The view defaults to `member` if either a members-only README or members-only pinned repositories are present, and `public` otherwise.
|
||||
|
||||
![Image of a members only organization profile page](/assets/images/help/organizations/member_only_profile.png)
|
||||
|
||||
Users who are not members of your organization will be shown a `public` view.
|
||||
|
||||
### Pinned repositories
|
||||
|
@ -49,21 +45,21 @@ You can format text and include emoji, images, and GIFs in your organization pro
|
|||
|
||||
## Adding a public organization profile README
|
||||
|
||||
1. If your organization does not already have a public `.github` repository, create a public `.github` repository.
|
||||
2. In your organization's `.github` repository, create a `README.md` file in the `profile` folder.
|
||||
3. Commit the changes to the `README.md` file. The content of the `README.md` will appear on your organization's public profile.
|
||||
The content of public `README.md` will appear on your organization's public profile.
|
||||
|
||||
![Image of an organization's public README](/assets/images/help/organizations/org_public_readme.png)
|
||||
1. If your organization does not already have a public `.github` repository, create a public `.github` repository.
|
||||
1. In your organization's `.github` repository, create a `README.md` file in the `profile` folder.
|
||||
1. Commit the changes to the `README.md` file.
|
||||
|
||||
{% ifversion org-profile-pin-private %}
|
||||
|
||||
## Adding a member-only organization profile README
|
||||
|
||||
1. If your organization does not already have a `.github-private` repository, create a private repository called `.github-private`.
|
||||
2. In your organization's `.github-private` repository, create a `README.md` file in the `profile` folder.
|
||||
3. Commit the changes to the `README.md` file. The content of the `README.md` will be displayed in the member view of your organization's profile.
|
||||
The content of a member-only `README.md` will be displayed in the member view of your organization's profile.
|
||||
|
||||
![Image of an organization's member-only README](/assets/images/help/organizations/org_member_readme.png)
|
||||
1. If your organization does not already have a `.github-private` repository, create a private repository called `.github-private`.
|
||||
1. In your organization's `.github-private` repository, create a `README.md` file in the `profile` folder.
|
||||
1. Commit the changes to the `README.md` file.
|
||||
|
||||
## Pinning repositories to your organization's profile
|
||||
|
||||
|
|
|
@ -25,10 +25,9 @@ shortTitle: View 2FA usage
|
|||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.people %}
|
||||
1. To view organization members, including organization owners, who have enabled or disabled two-factor authentication, on the right, select **2FA**, then click **Enabled** or **Disabled**.
|
||||
|
||||
|
||||
![Screenshot of the list of organization members. A dropdown menu, labeled "2FA", is expanded and outlined in orange.](/assets/images/help/2fa/filter-org-members-by-2fa.png)
|
||||
1. To view outside collaborators in your organization, under the "People" tab, click **Outside collaborators**.
|
||||
![select-outside-collaborators](/assets/images/help/organizations/select-outside-collaborators.png)
|
||||
1. To view outside collaborators in your organization, in the "Organization permissions" sidebar, click **Outside collaborators**.
|
||||
1. To view which outside collaborators have enabled or disabled two-factor authentication, above the list of outside collaborators, select the **2FA** dropdown menu, then click **Enabled** or **Disabled**.
|
||||
|
||||
![Screenshot of the list of outside collaborators. A dropdown menu, labeled "2FA", is expanded and outlined in orange.](/assets/images/help/2fa/filter-outside-collaborators-by-2fa.png)
|
||||
|
|
|
@ -43,10 +43,10 @@ You can give an entire team the same permission level to a {% data variables.pro
|
|||
{% data reusables.project-management.select-project %}
|
||||
{% data reusables.project-management.click-menu %}
|
||||
{% data reusables.project-management.access-collaboration-settings %}
|
||||
8. In the left sidebar, click **Teams**.
|
||||
9. To add a team, click **Add a team: Select team**. Then, choose a team from the drop-down menu or search for the team you'd like to add.
|
||||
1. In the left sidebar, click **Teams**.
|
||||
1. To add a team, click **Add a team: Select team**. Then, choose a team from the dropdown menu or search for the team you'd like to add.
|
||||
![Add a team drop-down menu with list of teams in organization](/assets/images/help/projects/add-a-team.png)
|
||||
10. Next to the team name, use the drop-down menu to select the desired permission level: **Read**, **Write**, or **Admin**.
|
||||
1. Next to the team name, use the dropdown menu to select the desired permission level: **Read**, **Write**, or **Admin**.
|
||||
![Team permissions drop-down menu with read, write, and admin options](/assets/images/help/projects/org-project-team-choose-permissions.png)
|
||||
|
||||
## Configuring a team's access to a {% data variables.projects.projects_v1_board %}
|
||||
|
@ -56,10 +56,9 @@ If a team's access to a {% data variables.projects.projects_v1_board %} is inher
|
|||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.specific_team %}
|
||||
4. Above the team's conversation, click {% octicon "project" aria-label="The Projects icon" %} **Projects**.
|
||||
1. Above the team's conversation, click {% octicon "project" aria-label="The Projects icon" %} **Projects**.
|
||||
![The team repositories tab](/assets/images/help/organizations/team-project-board-button.png)
|
||||
5. To change permissions levels, to the right of the {% data variables.projects.projects_v1_board %} you want to update, use the drop-down. To remove a {% data variables.projects.projects_v1_board %}, click **{% octicon "trash" aria-label="The trash icon" %}**.
|
||||
![Remove a project board from your team trash button](/assets/images/help/organizations/trash-button.png)
|
||||
1. To change permissions levels, to the right of the {% data variables.projects.projects_v1_board %} you want to update, use the permission level dropdown menu.
|
||||
|
||||
{% ifversion projects-v2-add-to-team %}
|
||||
|
||||
|
|
|
@ -17,7 +17,7 @@ shortTitle: Cancel or edit invitation
|
|||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.people %}
|
||||
1. Under "Organization permissions", click **Invitations**.
|
||||
1. Next to the username of the person whose invitation you'd like to edit or cancel, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit invitation**, or click **Cancel invitation**.
|
||||
1. Next to the username of the person whose invitation you'd like to edit or cancel, click {% octicon "kebab-horizontal" aria-label="Invitation options" %}, then click **Edit invitation**, or click **Cancel invitation**.
|
||||
|
||||
![Screenshot of the "Invitations" page. The "Edit invitation" and "Cancel invitation" buttons are highlighted with an orange outline.](/assets/images/help/organizations/organization-edit-or-cancel-invitation.png)
|
||||
|
||||
|
|
|
@ -19,7 +19,6 @@ You can also set announcement banners at the enterprise level. For more informat
|
|||
{% data reusables.profile.org_settings %}
|
||||
1. In the "Messages" section of the sidebar, click **{% octicon "megaphone" aria-hidden="true" %} Announcement**.
|
||||
1. Under "Announcement", in the text field, type the announcement you want displayed in a banner.
|
||||
![Screenshot of the text field to enter announcement](/assets/images/help/organizations/organization-announcement-text-field.png)
|
||||
1. Optionally, under "Expires on", select the calendar drop-down menu and click an expiration date.
|
||||
|
||||
{% note %}
|
||||
|
|
|
@ -24,9 +24,7 @@ Default labels are included in every new repository in your organization, but an
|
|||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.repository-defaults %}
|
||||
|
||||
5. Under "Repository labels", click **New label**.
|
||||
![New label button](/assets/images/help/organizations/new-label-button.png)
|
||||
1. Under "Repository labels", click **New label**.
|
||||
{% data reusables.project-management.name-label %}
|
||||
{% data reusables.project-management.label-description %}
|
||||
{% data reusables.project-management.label-color-randomizer %}
|
||||
|
|
|
@ -23,7 +23,6 @@ You can also disable updates from accounts your organization sponsors. For more
|
|||
{% 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**.
|
||||
![Update profile button](/assets/images/help/organizations/update-profile-button.png)
|
||||
|
||||
## Further reading
|
||||
|
||||
|
|
|
@ -69,8 +69,7 @@ To verify a domain, you must have access to modify domain records with your doma
|
|||
```
|
||||
1. After confirming your TXT record is added to your DNS, follow steps one through three above to navigate to your organization's approved and verified domains.
|
||||
{% data reusables.organizations.continue-verifying-domain %}
|
||||
11. Optionally, once the "Verified" badge is visible on your organization's profile page, you can delete the TXT entry from the DNS record at your domain hosting service.
|
||||
![Verified badge](/assets/images/help/organizations/verified-badge.png)
|
||||
1. Optionally, once the "Verified" badge is visible on your organization's profile page, you can delete the TXT entry from the DNS record at your domain hosting service.
|
||||
|
||||
## Approving a domain for your organization
|
||||
|
||||
|
|
|
@ -17,7 +17,7 @@ To perform any actions on {% data variables.product.product_name %}, such as cre
|
|||
|
||||
Within an organization, you can assign roles at the organization, team, and repository level. For more information about the different levels of roles, see "[AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
|
||||
|
||||
You can have more granular control over the permissions you grant at the repository level by creating up to {% ifversion authz-increased-custom-repo-roles %}five {% else %}three {% endif %} custom repository roles. {% data reusables.organizations.about-custom-repo-roles %} For more information, see "[AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).
|
||||
You can have more granular control over the permissions you grant at the repository level by creating up to {% ifversion authz-increased-custom-repo-roles %}five {% else %}three {% endif %} custom repository roles. {% data reusables.organizations.about-custom-repo-roles %} For more information, see "[AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
|
||||
|
||||
After you create a custom role, anyone with admin access to a repository can assign the role to an individual or team. For more information, see "[AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)" and "[AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)."
|
||||
|
||||
|
@ -65,18 +65,18 @@ You can only choose an additional permission if it's not already included in the
|
|||
|
||||
- Create a discussion category
|
||||
- Edit a discussion category
|
||||
- Delete a discussion category
|
||||
- Mark or unmark discussion answers
|
||||
- Hide or unhide discussion comments
|
||||
- Convert issues to discussions
|
||||
- Delete a discussion category
|
||||
- Mark or unmark discussion answers
|
||||
- Hide or unhide discussion comments
|
||||
- Convert issues to discussions
|
||||
|
||||
For more information, see "[AUTOTITLE](/discussions)."
|
||||
{% endif %}
|
||||
|
||||
### Issue and Pull Requests
|
||||
|
||||
- Assign or remove a user
|
||||
- Add or remove a label
|
||||
- Assign or remove a user
|
||||
- Add or remove a label
|
||||
|
||||
### Issue
|
||||
|
||||
|
@ -94,17 +94,17 @@ For more information, see "[AUTOTITLE](/discussions)."
|
|||
### Repository
|
||||
|
||||
- Set milestones
|
||||
- Manage wiki settings
|
||||
- Manage wiki settings
|
||||
- Manage project settings
|
||||
- Manage pull request merging settings
|
||||
- Manage pull request merging settings
|
||||
- Manage {% data variables.product.prodname_pages %} settings (see "[AUTOTITLE](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)")
|
||||
- Manage webhooks
|
||||
- Manage deploy keys
|
||||
- Manage webhooks
|
||||
- Manage deploy keys
|
||||
- Edit repository metadata
|
||||
{%- ifversion ghec %}
|
||||
- Set interaction limits
|
||||
{%- endif %}
|
||||
- Set the social preview
|
||||
- Set the social preview
|
||||
- Push commits to protected branches (branch protection rules will still apply)
|
||||
- Create protected tags
|
||||
- Delete protected tags
|
||||
|
@ -117,13 +117,13 @@ For more information, see "[AUTOTITLE](/discussions)."
|
|||
|
||||
### Security
|
||||
|
||||
- View {% data variables.product.prodname_code_scanning %} results
|
||||
- View {% data variables.product.prodname_code_scanning %} results
|
||||
- Dismiss or reopen {% data variables.product.prodname_code_scanning %} results
|
||||
- Delete {% data variables.product.prodname_code_scanning %} results
|
||||
- View {% data variables.product.prodname_dependabot_alerts %}
|
||||
- Dismiss or reopen {% data variables.product.prodname_dependabot_alerts %}
|
||||
- View {% data variables.product.prodname_secret_scanning %} results
|
||||
- Dismiss or reopen {% data variables.product.prodname_secret_scanning %} results
|
||||
- Delete {% data variables.product.prodname_code_scanning %} results
|
||||
- View {% data variables.product.prodname_dependabot_alerts %}
|
||||
- Dismiss or reopen {% data variables.product.prodname_dependabot_alerts %}
|
||||
- View {% data variables.product.prodname_secret_scanning %} results
|
||||
- Dismiss or reopen {% data variables.product.prodname_secret_scanning %} results
|
||||
|
||||
## Precedence for different levels of access
|
||||
|
||||
|
|
|
@ -22,23 +22,15 @@ redirect_from:
|
|||
|
||||
To create a new repository role, you add permissions to an inherited role and give the custom role a name.
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.org-list %}
|
||||
{% data reusables.organizations.org-settings-repository-roles %}
|
||||
5. Click **Create a Role**.
|
||||
![Screenshot of "Create a Role" button](/assets/images/help/organizations/repository-role-create-role.png)
|
||||
4. Under "Name", type the name of your repository role.
|
||||
![Field to type a name for the repository role](/assets/images/help/organizations/repository-role-name.png)
|
||||
5. Under "Description", type a description of your repository role.
|
||||
![Field to type a description for the repository role](/assets/images/help/organizations/repository-role-description.png)
|
||||
6. Under "Choose a role to inherit", select the role you want to inherit.
|
||||
![Selecting repository role base role option](/assets/images/help/organizations/repository-role-base-role-option.png)
|
||||
7. Under "Add Permissions", use the drop-down menu to select the permissions you want your custom role to include.
|
||||
![Selecting permission levels from repository role drop-down](/assets/images/help/organizations/repository-role-drop-down.png)
|
||||
7. Click **Create role**.
|
||||
![Confirm creating a repository role](/assets/images/help/organizations/repository-role-creation-confirm.png)
|
||||
1. Scroll to the "Custom roles" section, then click **Create a Role**.
|
||||
1. Under "Name", type the name of your repository role.
|
||||
1. Under "Description", type a description of your repository role.
|
||||
1. Under "Choose a role to inherit", select the role you want to inherit.
|
||||
1. Under "Add Permissions", select the dropdown menu and click the permissions you want your custom role to include.
|
||||
1. Click **Create role**.
|
||||
|
||||
## Editing a repository role
|
||||
|
||||
|
@ -47,10 +39,10 @@ To create a new repository role, you add permissions to an inherited role and gi
|
|||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.org-list %}
|
||||
{% data reusables.organizations.org-settings-repository-roles %}
|
||||
3. To the right of the role you want to edit, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit**.
|
||||
![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-edit-setting.png)
|
||||
4. Edit, then click **Update role**.
|
||||
![Edit fields and update repository roles](/assets/images/help/organizations/repository-role-update.png)
|
||||
1. To the right of the role you want to edit, click {% octicon "kebab-horizontal" aria-label="Show custom role actions" %}, then click **Edit**.
|
||||
|
||||
![Screenshot of the list of custom roles for an organization. To the right of a role, a kebab icon is outlined in dark orange.](/assets/images/help/organizations/repository-role-edit-setting.png)
|
||||
1. Edit, then click **Update role**.
|
||||
|
||||
## Deleting a repository role
|
||||
|
||||
|
@ -61,7 +53,7 @@ If you delete an existing repository role, all pending invitations, teams, and u
|
|||
{% data reusables.organizations.org_settings %}
|
||||
{% data reusables.organizations.org-list %}
|
||||
{% data reusables.organizations.org-settings-repository-roles %}
|
||||
3. To the right of the role you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**.
|
||||
![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-delete-setting.png)
|
||||
4. Review changes for the role you want to remove, then click **Delete role**.
|
||||
![Confirm deleting a repository role](/assets/images/help/organizations/repository-role-delete-confirm.png)
|
||||
1. To the right of the role you want to delete, click {% octicon "kebab-horizontal" aria-label="Show custom role actions" %}, then click **Delete**.
|
||||
|
||||
![Screenshot of the list of custom roles for an organization. To the right of a role, a kebab icon is outlined in dark orange.](/assets/images/help/organizations/repository-role-edit-setting.png)
|
||||
1. Review changes for the role you want to remove, then click **Delete role**.
|
||||
|
|
|
@ -17,7 +17,7 @@ redirect_from:
|
|||
|
||||
When integration access requests are enabled, outside collaborators can request organization access for {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} which have not yet been approved by your organization. If you disable integration access requests, only organization members will be able to request organization access for unapproved {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}. Outside collaborators will still be able to consent to pre-approved {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} accessing the same resources the requesting outside collaborator has access to.
|
||||
|
||||
By default, integration access requests are enabled. If your organization has a large number of outside collaborators, you may want to disable integration access requests, to reduce the number of requests you have to review.
|
||||
By default, integration access requests are enabled. If your organization has a large number of outside collaborators, you may want to disable integration access requests, to reduce the number of requests you have to review.
|
||||
|
||||
## Enabling or disabling integration access requests
|
||||
|
||||
|
@ -25,4 +25,3 @@ By default, integration access requests are enabled. If your organization has a
|
|||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.profile.org_member_privileges %}
|
||||
1. Under "Integration access requests" select or deselect **Allow integration requests from outside collaborators** and click **Save**.
|
||||
![Screenshot of integration access requests setting](/assets/images/help/organizations/integration-access-requests.png)
|
||||
|
|
|
@ -28,11 +28,11 @@ If your organization [requires members to use two-factor authentication](/organi
|
|||
{% data reusables.organizations.people %}
|
||||
{% data reusables.organizations.people_tab_outside_collaborators %}
|
||||
{% ifversion fpt or ghec %}
|
||||
5. To the right of the name of the outside collaborator you want to become a member, select the {% octicon "kebab-horizontal" aria-label="Collaborator settings" %} dropdown menu and click **Invite to organization**.
|
||||
1. To the right of the name of the outside collaborator you want to become a member, select the {% octicon "kebab-horizontal" aria-label="Collaborator settings" %} dropdown menu and click **Invite to organization**.
|
||||
|
||||
![Invite outside collaborators to organization](/assets/images/help/organizations/invite_outside_collaborator_to_organization.png)
|
||||
![Screenshot of the outside collaborator list for an organization. To the right of a collaborator, a kebab icon is outlined in dark orange.](/assets/images/help/organizations/manage-outside-collaborator.png)
|
||||
{% else %}
|
||||
5. To the right of the name of the outside collaborator you want to become a member, click **Invite to organization**.![Invite outside collaborators to organization](/assets/images/enterprise/orgs-and-teams/invite_outside_collabs_to_org.png)
|
||||
1. 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 %}
|
||||
|
|
|
@ -1,4 +1,2 @@
|
|||
1. Optionally, if your organization is owned by a business or institution, select **This account is owned by a business**.
|
||||
![Checkbox for organizations that are owned by a business](/assets/images/help/organizations/organization-belongs-to.png)
|
||||
2. If your organization is owned by a business or institution, type the name of the business or institution.
|
||||
![Name of business or institution field](/assets/images/help/organizations/name-of-business.png)
|
||||
1. If your organization is owned by a business or institution, under "Name of business or institution this organization belongs to", type the name of the business or institution.
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
{% ifversion fpt or ghec %}
|
||||
1. Add an organization member to the team or invite a non-member to join a team:
|
||||
1. Add an organization member to the team or invite a non-member to join a team.
|
||||
- If the person you want to add is already a member of your organization, type their username and click **Enter**. The user will immediately be added to the team.
|
||||
- If the person you want to add is not member of your organization, type their username or email address and click **Enter**. The user will receive an email invitation to join your organization and will be added to the team once they accept the invitation.{% else %}
|
||||
- If the person you want to add is not member of your organization, type their username or email address and click **Enter**. The user will receive an email invitation to join your organization and will be added to the team once they accept the invitation.
|
||||
{% else %}
|
||||
1. Type the username of the person you want to add and click **Enter**. The user will immediately be added to the team.
|
||||
![Add team member popup](/assets/images/help/organizations/Organization-add-team.png)
|
||||
{% endif %}
|
||||
|
|
|
@ -1,6 +1,5 @@
|
|||
{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
|
||||
1. In the "Access" section of the sidebar, click **{% octicon "people" aria-label="The people icon" %} Member privileges**.
|
||||
1. In the "Access" section of the sidebar, click **{% octicon "people" aria-hidden="true" %} Member privileges**.
|
||||
{% else %}
|
||||
4. In the left sidebar, click **Member privileges**.
|
||||
![Member privileges option in org settings](/assets/images/help/organizations/org-settings-member-privileges.png)
|
||||
{% endif %}
|
||||
|
|
|
@ -1,2 +1 @@
|
|||
1. Under "Organizations", next to the name of your organization, click **Settings**.
|
||||
![Screenshot of an organization next to the "Settings" button](/assets/images/help/organizations/list-of-organizations.png)
|
||||
|
|
|
@ -1,7 +1,3 @@
|
|||
1. Under your organization name, click {% octicon "gear" aria-label="The Settings gear" %} **Settings**.
|
||||
1. Under your organization name, click {% octicon "gear" aria-hidden="true" %} **Settings**. If you cannot see the "Settings" tab, select the **{% octicon "kebab-horizontal" aria-label="More" %}** dropdown menu, then click **Settings**.
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
![Organization settings button](/assets/images/help/organizations/organization-settings-tab-with-overview-tab.png)
|
||||
{% else %}
|
||||
![Organization settings button](/assets/images/help/organizations/organization-settings-tab.png)
|
||||
{% endif %}
|
||||
![Screenshot of the horizontal navigation bar for an organization. The "Settings" tab is outlined in dark orange.](/assets/images/help/organizations/organization-settings-tab.png)
|
||||
|
|
|
@ -1,2 +1 @@
|
|||
1. Under "Organization account name", type a name for your organization account.
|
||||
![Field to type an organization name](/assets/images/help/organizations/new-org-name.png)
|
||||
|
|
|
@ -1,2 +1 @@
|
|||
4. Under the "People" tab, click **Outside collaborators**.
|
||||
![Button to select outside collaborators for an organization](/assets/images/help/organizations/select-outside-collaborators.png)
|
||||
1. In the "Organization permissions" sidebar, click **Outside collaborators**.
|
||||
|
|
|
@ -1,5 +1,4 @@
|
|||
1. Optionally, to require members to use SSH certificates, select **Require SSH Certificates**, then click **Save**.
|
||||
![Require SSH Certificate checkbox and save button](/assets/images/help/organizations/require-ssh-cert.png)
|
||||
|
||||
{% note %}
|
||||
|
||||
|
|
|
@ -1,2 +1 @@
|
|||
1. Under "Authentication", select **Require two-factor authentication for everyone in your organization**, then click **Save**.
|
||||
![Require 2FA checkbox](/assets/images/help/organizations/require-2fa-checkbox.png)
|
||||
1. Under "Two-factor authentication", select **Require two-factor authentication for everyone in your organization**, then click **Save**.
|
||||
|
|
|
@ -1,19 +1,6 @@
|
|||
1. To view all expired and failed invitations, click **Failed invitations**, under "Organization permissions" on the left.
|
||||
1. In the "Organization permissions" sidebar, click **Failed invitations**.
|
||||
1. Next to an invitation, select the {% octicon "kebab-horizontal" aria-label="Member settings" %} dropdown menu, then click **Retry invitation** or **Cancel invitation**.
|
||||
|
||||
![Screenshot of the people tab with the failed invitations option emphasized](/assets/images/help/organizations/organization-failed-invitations.png)
|
||||
![Screenshot of the list of failed invitations for an organization. To the right of the first entry, a kebab icon is outlined in dark orange.](/assets/images/help/organizations/retry-or-cancel-invitation.png)
|
||||
|
||||
2. To retry or cancel a single invitation, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} next to the expiration warning, and select **Retry invitation** or **Cancel invitation**.
|
||||
|
||||
![Screenshot of the failed invitations view with the retry and cancel invitation options highlighted](/assets/images/help/organizations/retry-or-cancel-invitation.png)
|
||||
|
||||
3. To confirm, click **Retry invitation** or **Cancel invitation** in the pop-up.
|
||||
|
||||
![Screenshot of the retry invitation pop-up](/assets/images/help/organizations/retry-invitation-pop-up.png)
|
||||
|
||||
4. Optionally, to retry or cancel multiple invitations at the same time, select the checkboxes next to the invitations. Click the dropdown at the top of the list and select **Retry invitations** or **Cancel invitations**.
|
||||
|
||||
![Screenshot of the dropdown to edit multiple invitations](/assets/images/help/organizations/organization-invitations-multiple-selection.png)
|
||||
|
||||
5. Optionally, to retry or cancel all invitations on the page, check the box at the top of the list, and click **Retry invitations** or **Cancel invitations**.
|
||||
|
||||
![Screenshot of the dropdown to bulk edit all invitations on the page](/assets/images/help/organizations/organization-invitations-bulk-select.png)
|
||||
1. To confirm, click **Retry invitation** or **Cancel invitation**.
|
|
@ -1,2 +0,0 @@
|
|||
1. Above the list of team members, click {% octicon "repo" aria-label="The Repository icon" %} **Repositories**.
|
||||
![The team repositories tab](/assets/images/help/organizations/team-repositories-button.png)
|
|
@ -1,2 +1 @@
|
|||
3. Under "Access", click **Member privileges**.
|
||||
![Screenshot of the member privileges tab](/assets/images/help/organizations/member-privileges.png)
|
||||
1. In the "Access" section of the sidebar, click **Member privileges**.
|
||||
|
|
|
@ -1,3 +1,3 @@
|
|||
1. Under your repository name, click {% octicon "gear" aria-hidden="true" %} **Settings**. If you cannot see the "Settings" tab, select the **{% octicon "kebab-horizontal" aria-hidden="true" %}** dropdown menu, then click **Settings**.
|
||||
1. Under your repository name, click {% octicon "gear" aria-hidden="true" %} **Settings**. If you cannot see the "Settings" tab, select the **{% octicon "kebab-horizontal" aria-label="More" %}** dropdown menu, then click **Settings**.
|
||||
|
||||
![Screenshot of a repository header showing the tabs. The "Settings" tab is highlighted by a dark orange outline.](/assets/images/help/repository/repo-actions-settings.png)
|
||||
|
|