Skip to content

Commit 91fbefd

Browse files
authored
Update github-enterprise-models.md
1 parent a401fd0 commit 91fbefd

File tree

1 file changed

+3
-8
lines changed

1 file changed

+3
-8
lines changed

learn-pr/github/manage-github-actions-enterprise/includes/github-enterprise-models.md

Lines changed: 3 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,9 @@ In this unit, you'll explore the different GitHub Enterprise deployment models
33
## How users are managed
44
GitHub Enterprise Cloud (GHEC) is a cloud-based solution tailored for organizations that need the flexibility and scalability of GitHub's infrastructure while maintaining enterprise-grade security and compliance. It offers features such as centralized user management, data residency options, and integration with identity providers like SAML and SCIM for single sign-on and user provisioning.
55

6-
GHEC is ideal for globally distributed teams, as it ensures high availability, automated backups, and seamless access to GitHub’s robust collaboration tools. It supports regulatory compliance (e.g., GDPR) and provides detailed audit logs for governance. With GHEC, organizations can leverage GitHub’s advanced capabilities without managing on-premises infrastructure.
7-
8-
### Standard User Model
6+
GHEC is ideal for globally distributed teams, as it ensures high availability, automated backups, and seamless access to GitHub’s robust collaboration tools. It supports regulatory compliance and provides detailed audit logs for governance. With GHEC, organizations can leverage GitHub’s advanced capabilities without managing on-premises infrastructure.
97

8+
### 1. Standard User Model
109
This is the traditional user model on GitHub, where users manage their own account.
1110

1211
**Characteristics of standard user model**:
@@ -18,7 +17,6 @@ This is the traditional user model on GitHub, where users manage their own accou
1817

1918

2019
### The Enterprise Managed User (EMU) model
21-
2220
This is the model designed for organizations requiring centralized user account management, offering better control and compliance features.
2321

2422
**In EMU model**:
@@ -30,8 +28,7 @@ This is the model designed for organizations requiring centralized user account
3028

3129

3230

33-
### GitHub Enterprise Cloud (GHEC) with **Data Residency**
34-
31+
### GitHub Enterprise Cloud (GHEC) with **Data Residency**
3532
GitHub Enterprise Cloud (GHEC) with **Data Residency** is an important feature of GHEC for organizations that must comply with data protection regulations by ensuring specific data is stored in particular geographical regions.
3633

3734
**It allows users to**:
@@ -52,8 +49,6 @@ GitHub Enterprise Cloud (GHEC) with **Data Residency** is an important feature o
5249
- Certain types of backup data may be replicated outside the region but remain encrypted.
5350

5451
## 2. GitHub Enterprise Server (GHES)
55-
56-
5752
GitHub Enterprise Server (GHES) is a self-hosted version of GitHub designed for organizations that require complete control over their GitHub instance. It is ideal for companies that want to host their repositories and associated data on-premises or in a private cloud environment for compliance, security, or performance reasons.
5853

5954
### Key Features of GitHub Enterprise Server

0 commit comments

Comments
 (0)