You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: github/github-introduction-administration/5-knowledge-check.yml
+19-19Lines changed: 19 additions & 19 deletions
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ title: Knowledge check
4
4
metadata:
5
5
title: Check your knowledge
6
6
description: Review what you've learned.
7
-
ms.date: 8/23/2021
7
+
ms.date: 2/16/2023
8
8
author: lucie-docs
9
9
ms.author: lucielenaour
10
10
ms.topic: interactive-tutorial
@@ -13,45 +13,45 @@ durationInMinutes: 3
13
13
quiz:
14
14
title: Check your knowledge
15
15
questions:
16
-
- content: "You want to grant a user the permissions required to add and remove organization members to a team. Which permission would you need to grant that user?"
16
+
- content: "You want to grant a user the permissions required to add and remove organization members to and from a team. Which permission would you need to grant that user?"
17
17
choices:
18
18
- content: "The admin permission on a repository"
19
19
isCorrect: false
20
-
explanation: "The admin permission on a repository will only allow you to perform full administration-related tasks on a specific repository; it will not affect membership on a team."
20
+
explanation: "Incorrect. The admin permission on a repository only allows you to perform full administration-related tasks on a specific repository; it doesn't affect membership on a team."
21
21
- content: "The maintain permission on a repository"
22
22
isCorrect: false
23
-
explanation: "The maintain permission on a repository will only allow you to perform limited administration-related tasks on a specific repository; it will not affect membership on a team."
23
+
explanation: "Incorrect. The maintain permission on a repository only allows you to perform limited administration-related tasks on a specific repository; it doesn't affect membership on a team."
24
24
- content: "Organization billing manager"
25
25
isCorrect: false
26
-
explanation: "The organization billing manager permission only allows the user to handle billing related tasks; it will not affect membership on a team."
26
+
explanation: "Incorrect. The organization billing manager permission only allows the user to handle billing related tasks; it doesn't affect membership on a team."
27
27
- content: "Team maintainer"
28
28
isCorrect: true
29
-
explanation: "As a team maintainer, the user will be able to add and remove organization members to a team."
30
-
- content: "As an organization owner, you want to ensure that everyone who is signed in to your corporate network can access the GitHub website without requiring a second sign-in. Which technology will you enable to accomplish this?"
29
+
explanation: "Correct! As a team maintainer, the user can add and remove organization members to and from a team."
30
+
- content: "As an organization owner, you want to ensure that everyone who is signed in to your corporate network can access the GitHub website without requiring a second sign-in. Which technology would you enable to accomplish this?"
31
31
choices:
32
-
- content: "Single Sign-On"
32
+
- content: "Single sign-on"
33
33
isCorrect: true
34
-
explanation: "Single Sign-On is the right technology to allow network users to access the GitHub website without additional sign-ins."
34
+
explanation: "Correct! Single sign-on is the right technology to allow network users to access the GitHub website without extra sign-ins."
35
35
- content: "Two-factor authentication"
36
36
isCorrect: false
37
-
explanation: "Two-factor authentication would require each user to sign in using a second means of identifying themselves, like using an authenticator app on their phones. It would not be used in this scenario."
38
-
- content: "SSH Keys"
39
-
isCorrect: false
40
-
explanation: "Personal Access Tokens provide access for the git client or web API by using a cryptographic key. You do not use them to access the GitHub website."
37
+
explanation: "Incorrect. Two-factor authentication requires each user to sign in by using a second means of identifying themselves, like using an authenticator app on their phones."
41
38
- content: "Personal Access Tokens"
42
39
isCorrect: false
43
-
explanation: "Personal Access Tokens provide access for the git client through a username and password. You do not use them to access the GitHub website."
44
-
- content: "What is the appropriate repository permission level for contributors who will actively push changes to your repository?"
40
+
explanation: "Incorrect. Personal Access Tokens provide access for the git client or web API by using a cryptographic key. You don't use them to access the GitHub website."
41
+
- content: "SSH keys"
42
+
isCorrect: false
43
+
explanation: "Incorrect. SSH keys provide access for the git client through a username and password. You don't use them to access the GitHub website."
44
+
- content: "What's the appropriate repository permission level for contributors who need to actively push changes to your repository?"
45
45
choices:
46
46
- content: "admin"
47
47
isCorrect: false
48
-
explanation: "The admin permission is not appropriate because provides too much access to the administration functions of the repository."
48
+
explanation: "Incorrect. The admin permission isn't appropriate because it provides too much access to the administration functions of the repository."
49
49
- content: "write"
50
50
isCorrect: true
51
-
explanation: "The write permission is the appropriate permission level."
51
+
explanation: "Correct! The write permission is the appropriate permission level."
52
52
- content: "triage"
53
53
isCorrect: false
54
-
explanation: "The triage permission is not appropriate because it is intended for contributors who need to proactively manage issues and pull requests without write access."
54
+
explanation: "Incorrect. The triage permission is for contributors who need to proactively manage issues and pull requests without making changes."
55
55
- content: "maintain"
56
56
isCorrect: false
57
-
explanation: "The maintain permission is not appropriate because it is intended for project managers who need to manage the repository without access to sensitive or destructive actions. It would provide too much access for other users."
57
+
explanation: "Incorrect. The maintain permission is for contributors who need to manage the repository without access to sensitive or destructive actions. It provides too much access for other users."
GitHub administrators work to ensure that their organization's code and content assets are protected while providing each team access to the repositories they rely on to collaborate and share their work.
1
+
GitHub administrators work to protect their organization's code and content assets while providing each team access to the repositories they rely on to collaborate and share their work.
2
2
3
-
Imagine that your CIO asks you for an adoption plan to help the entire company benefit from GitHub. You want to ensure every group has adequate access to the right repositories and that there is a sustainable way to provide adequate permissions to the appropriate software development and content teams. You will need to think through the kinds of tasks that administrators need to perform and assign them the right level of access. But first, you really need to understand what options are available to you from GitHub.
3
+
Imagine that your CIO asks you for an adoption plan to help the entire company benefit from GitHub. You want to ensure every group has adequate access to the right repositories and that there's a sustainable way to provide adequate permissions to the appropriate software development and content teams. You'll need to think through the kinds of tasks that administrators need to perform and assign them the right level of access. But first, you really need to understand what options are available to you from GitHub.
4
4
5
-
In this module, you will learn about:
5
+
In this module, you'll learn about:
6
6
7
7
- GitHub administrative tasks and their purpose at each hierarchical level.
8
8
- The various ways that administrators can configure authentication so that users can access GitHub via the web browser and the git client.
9
9
- Hierarchical permission levels and what these permissions allow you to do in GitHub.
10
10
11
11
## Learning objectives
12
12
13
-
By the end of this module, you will be able to:
13
+
By the end of this module, you'll be able to:
14
14
15
15
- Summarize the organizational structures and permission levels that GitHub administrators can use to organize members to control access and security.
16
16
- Identify the various technologies that enable a secure authentication strategy, allowing administrators to centrally manage repository access.
17
-
- Describe the technologies required to centrally manage teams and members using existing directory information services and how GitHub can itself be used as an identity provider for authentication and authorization.
17
+
- Describe the technologies required to centrally manage teams and members using existing directory information services and how you can use GitHub itself as an identity provider for authentication and authorization.
18
18
19
-
## Prerequisites
20
-
21
-
- Familiarity with GitHub, repositories, and the basics of managing individual accounts
22
-
- Familiarity with personal and organizational authentication technologies and processes
Copy file name to clipboardExpand all lines: github/github-introduction-administration/includes/2-what-is-github-administration.md
+13-14Lines changed: 13 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,39 +2,41 @@ As a GitHub administrator, your goal is to keep everything working smoothly for
2
2
3
3
## Administration at team level
4
4
5
-
:::image type="content" source="../media/teams.png" alt-text="Screenshot of organization screen with Teams tab highlighted.":::
5
+
:::image type="content" source="../media/teams.png" alt-text="Screenshot of the organization screen with the Teams tab highlighted.":::
6
6
7
-
In GitHub, each user is an organization member that can be added to a team. You can create teams in your organization with cascading access permissions and mentions to reflect your company or group's structure. Teams are useful for refining repository permissions on a more granular level and enabling communication and notification between team members.
7
+
In GitHub, each user is an organization member that you can add to a team. You can create teams in your organization with cascading access permissions and mentions to reflect your company or group's structure. Teams are useful for refining repository permissions on a more granular level and enabling communication and notification between team members.
8
8
9
-
Additionally, GitHub allows you to sync your teams with identity provider (IdP) groups such as Azure Active Directory (Azure AD). When you synchronize a GitHub team with an Azure AD, changes to the Azure AD group are automatically reflected on GitHub, reducing the need for manual updates and custom scripts. You can use an Azure AD with team synchronization to manage administrative tasks such as onboarding new members, granting new permissions for movements within an organization, and removing member access from the organization.
9
+
Additionally, GitHub allows you to sync your teams with identity provider (IdP) groups such as Azure Active Directory (Azure AD). When you synchronize a GitHub team with Azure AD, you can replicate changes to GitHub automatically, which reduces the need for manual updates and custom scripts. You can use Azure AD with team synchronization to manage administrative tasks such as onboarding new members, granting new permissions, and removing member access to the organization.
10
10
11
11
Members of a team with *team maintainer* or repository *admin* permissions can:
12
12
13
-
- Create a new team, as well as select or change the parent team.
13
+
- Create a new team, and select or change the parent team.
14
14
- Delete or rename a team.
15
15
- Add or remove organization members from a team, or synchronize a GitHub team's membership with an IdP group.
16
-
- Add or remove outside collaborators (people who are not explicitly members of your organization, such as consultants or temporary employees) from team repositories.
17
-
- Enable or disable team discussions, where the team can plan together, update one another, or talk about any topic in discussion posts on the organization's team's page.
16
+
- Add or remove outside collaborators (people who aren't explicitly members of your organization, such as consultants or temporary employees) from team repositories.
17
+
- Enable or disable team discussionson the team's page.
18
18
- Change the visibility of the team within the organization.
Creating teams in your organization enables greater flexibility for collaboration and can make it easier to separate repositories and permissions. The following are some best practices for setting up teams on GitHub:
24
26
25
27
- Create nested teams to reflect your group or company's hierarchy within your GitHub organization.
26
28
- Create teams based on interests or specific technology (JavaScript, data science, etc.) to help streamline PR review processes. Individuals can choose to join these teams according to their interests or skills.
27
-
- Enable team synchronization between your identity provider (IdP) and GitHub to allow organization owners and team maintainers to connect teams in your organization with IdP groups. When you synchronize a GitHub team with an IdP group, changes to the IdP group are reflected on GitHub automatically, reducing the need for manual updates and custom scripts. You can use an IdP with team synchronization to manage administrative tasks such as onboarding new members, granting new permissions for movements within an organization, and removing member access to the organization.
29
+
- Enable team synchronization between your identity provider (IdP) and GitHub to allow organization owners and team maintainers to connect teams in your organization with IdP groups. When you synchronize a GitHub team with an IdP group, you can replicate changes to GitHub automatically, reducing the need for manual updates and custom scripts. You can use an IdP with team synchronization to manage administrative tasks such as onboarding new members, granting new permissions, and removing member access to the organization.
28
30
29
31
## Administration at organization level
30
32
31
33
In GitHub, organizations are shared spaces enabling users to collaborate across many projects at once. Owners and administrators can manage member access to the organization's data and repositories with sophisticated security and administrative features.
32
34
33
35
Members of an organization with the *owner* permission can perform a wide range of activities at the organization level including:
34
36
35
-
- Invite users to join the organization, as well as remove members from the organization.
37
+
- Invite users to join the organization and remove members from the organization.
36
38
- Organize users into a team, and grant "team maintainer" permissions to organization members.
37
-
- Add or remove outside collaborators (people who are not explicitly members of your organization, such as consultants or temporary employees) to organizational repositories.
39
+
- Add or remove outside collaborators (people who aren't explicitly members of your organization, such as consultants or temporary employees) to organizational repositories.
38
40
- Grant repository permission levels to members, and set the base (default) permission level for a given repository.
39
41
- Set up organization security.
40
42
- Set up billing or assign a billing manager for the organization.
@@ -43,14 +45,12 @@ Members of an organization with the *owner* permission can perform a wide range
43
45
44
46
We recommend setting up only one organization for your users and repositories. If specific constraints in your company require you to create multiple organizations, be aware that:
45
47
46
-
- It is not possible to duplicate an organization or share configurations between two organizations. This means that you must set up everything from scratch every time you create an organization, which increases the risk of errors in your settings.
48
+
- It isn't possible to duplicate an organization or share configurations between two organizations. This means that you must set up everything from scratch every time you create an organization, which increases the risk of errors in your settings.
47
49
- Depending on your software providers' policies, you might incur extra costs if you need to install some applications in multiple organizations.
48
50
- Managing multiple organizations is generally more difficult!
49
51
50
52
## Administration at enterprise level
51
53
52
-
:::image type="content" source="../media/avocado-corp.png" alt-text="Screenshot of enterprise screen.":::
53
-
54
54
Enterprise accounts include GitHub Enterprise Cloud and Enterprise Server instances and enable owners to centrally manage policy and billing for multiple organizations.
55
55
56
56
At the enterprise level, members of an enterprise with the *owner* permissions can:
@@ -64,6 +64,5 @@ At the enterprise level, members of an enterprise with the *owner* permissions c
64
64
65
65
## Learn more
66
66
67
-
This link provides more information about the topics covered in this module:
67
+
Read more about [nested teams](https://docs.github.com/organizations/organizing-members-into-teams/about-teams#nested-teams)in GitHub Docs.
68
68
69
-
[GitHub documentation on nested teams](https://docs.github.com/organizations/organizing-members-into-teams/about-teams#nested-teams)
0 commit comments