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: content/actions/reference/environments.md
+3-1Lines changed: 3 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,9 @@ versions:
15
15
You can configure environments with protection rules and secrets. When a workflow job references an environment, the job won't start until all of the environment's protection rules pass. A job also cannot access secrets that are defined in an environment until all the environment protection rules pass.
16
16
17
17
{% ifversion fpt %}
18
-
Environment protection rules and environment secrets are only available on public repositories and private repositories on an enterprise plan. If you convert a repository from public to private on a non-enterprise plan, any configured protection rules or environment secrets will be ignored, and you will not be able to configure any environments. If you convert your repository back to public, you will have access to any previously configured protection rules and environment secrets.
18
+
Environment protection rules and environment secrets are only available on private repositories with {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
19
+
20
+
If you don't use {% data variables.product.prodname_ghe_cloud %} and convert a repository from public to private, any configured protection rules or environment secrets will be ignored, and you will not be able to configure any environments. If you convert your repository back to public, you will have access to any previously configured protection rules and environment secrets.
Copy file name to clipboardExpand all lines: content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,8 @@ versions:
7
7
8
8
This guide will walk you through setting up, configuring and managing your {% data variables.product.prodname_ghe_cloud %} account as an organization or enterprise owner.
9
9
10
+
{% data reusables.enterprise.ghec-cta-button %}
11
+
10
12
## Part 1: Choosing your account type
11
13
12
14
{% data variables.product.prodname_dotcom %} provides two types of Enterprise products:
Copy file name to clipboardExpand all lines: content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
+23-27Lines changed: 23 additions & 27 deletions
Original file line number
Diff line number
Diff line change
@@ -12,37 +12,38 @@ topics:
12
12
- Accounts
13
13
shortTitle: Enterprise Cloud trial
14
14
---
15
+
16
+
{% data reusables.enterprise.ghec-cta-button %}
17
+
18
+
19
+
## About {% data variables.product.prodname_ghe_cloud %}
20
+
21
+
{% data reusables.organizations.about-organizations %}
22
+
23
+
You can use organizations for free with {% data variables.product.prodname_free_team %}, which includes limited features. For additional features, such as SAML single sign-on (SSO), access control for {% data variables.product.prodname_pages %}, and included {% data variables.product.prodname_actions %} minutes, you can upgrade to {% data variables.product.prodname_ghe_cloud %}. For a detailed list of the features available with {% data variables.product.prodname_ghe_cloud %}, see our [Pricing](https://github.com/pricing) page.
24
+
25
+
{% data reusables.saml.saml-accounts %} For more information, see "<ahref="/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on"class="dotcom-only">About identity and access management with SAML single sign-on</a>."
26
+
27
+
{% data reusables.products.which-product-to-use %}
28
+
15
29
## About trials of {% data variables.product.prodname_ghe_cloud %}
16
30
17
-
You can set up a 14-day trial to evaluate {% data variables.product.prodname_ghe_cloud %} on a new organization account. You do not need to provide a payment method during the trial unless you add {% data variables.product.prodname_marketplace %} apps to your organization that require a payment method. For more information, see "<ahref="/articles/about-billing-for-github-marketplace/"class="dotcom-only">About billing for {% data variables.product.prodname_marketplace %}</a>."
31
+
You can set up a 14-day trial to evaluate {% data variables.product.prodname_ghe_cloud %}. You do not need to provide a payment method during the trial unless you add {% data variables.product.prodname_marketplace %} apps to your organization that require a payment method. For more information, see "<ahref="/articles/about-billing-for-github-marketplace/"class="dotcom-only">About billing for {% data variables.product.prodname_marketplace %}</a>."
18
32
19
33
Your trial includes 50 seats. If you need more seats to evaluate {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. At the end of the trial, you can choose a different number of seats.
20
34
21
35
Trials are also available for {% data variables.product.prodname_ghe_server %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)."
22
36
23
-
{% data reusables.products.which-product-to-use %}
24
-
25
37
## Setting up your trial of {% data variables.product.prodname_ghe_cloud %}
26
38
27
-
Before you can start your trial of {% data variables.product.prodname_ghe_cloud %}, you must have an existing user account or create a new user account. For more information, see "<ahref="/articles/signing-up-for-a-new-github-account"class="dotcom-only">Signing up for a new {% data variables.product.prodname_dotcom %} account</a>."
28
-
29
-
{% data reusables.user_settings.access_settings %}
30
-
{% data reusables.user_settings.organizations %}
31
-
{% data reusables.organizations.new-organization %}
32
-
4. Under "Enterprise", click **Start your 14-day free trial**.
33
-
34
-
5. Type your company name.
35
-
36
-
{% data reusables.organizations.organization-name %}
37
-
7. Under "Full name", type your full name.
38
-
39
-
8. Under "Work email", type the email address you use for work.
9. Use the **Number of employees** drop-down menu, and select the number of employees at your company.
44
-
45
-
10. Review the <ahref="/articles/github-enterprise-cloud-evaluation-agreement"class="dotcom-only">Evaluation License Agreement</a>, then click **Next**.
39
+
Before you can try {% data variables.product.prodname_ghe_cloud %}, you must be signed into a user account. If you don't already have a user account on {% data variables.product.prodname_dotcom_the_website %}, you must create one. For more information, see "<ahref="/articles/signing-up-for-a-new-github-account"class="dotcom-only">Signing up for a new {% data variables.product.prodname_dotcom %} account</a>."
40
+
41
+
1. Navigate to [{% data variables.product.prodname_dotcom %} for enterprises](https://github.com/enterprise).
42
+
1. Click **Start a free trial**.
43
+
## Exploring {% data variables.product.prodname_ghe_cloud %}
48
49
@@ -58,14 +59,9 @@ If you don't purchase {% data variables.product.prodname_enterprise %} or {% dat
58
59
59
60
Downgrading to {% data variables.product.prodname_free_team %} for organizations also disables any SAML settings configured during the trial period. Once you purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %}, your SAML settings will be enabled again for users in your organization to authenticate.
60
61
61
-
62
62
{% data reusables.profile.access_org %}
63
63
{% data reusables.profile.org_settings %}
64
64
{% data reusables.organizations.billing_plans %}
65
65
5. Under "{% data variables.product.prodname_ghe_cloud %} Free Trial", click **Buy Enterprise** or **Downgrade to Team**.
66
66
67
67
6. Follow the prompts to enter your payment method, then click **Submit**.
68
-
69
-
## Further reading
70
-
71
-
- "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)"
Copy file name to clipboardExpand all lines: content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md
+9-6Lines changed: 9 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,8 @@ topics:
14
14
shortTitle: Add outside collaborator
15
15
---
16
16
17
+
## About outside collaborators
18
+
17
19
{% data reusables.organizations.owners-and-admins-can %} add outside collaborators to a repository, unless an organization owner has restricted the ability to invite collaborators. For more information, see "[Setting permissions for adding outside collaborators](/articles/setting-permissions-for-adding-outside-collaborators)."
18
20
19
21
{% data reusables.organizations.outside-collaborators-use-seats %}
@@ -24,6 +26,12 @@ If your organization [requires members and outside collaborators to use two-fact
24
26
25
27
{% data reusables.organizations.outside_collaborator_forks %}
26
28
29
+
{% ifversion fpt %}
30
+
To further support your team's collaboration abilities, you can upgrade to {% data variables.product.prodname_ghe_cloud %}, which includes features like protected branches and code owners on private repositories. {% data reusables.enterprise.link-to-ghec-trial %}
31
+
{% endif %}
32
+
33
+
## Adding outside collaborators to a repository
34
+
27
35
{% data reusables.repositories.navigate-to-repo %}
28
36
{% data reusables.repositories.sidebar-settings %}
29
37
{% ifversion fpt %}
@@ -40,9 +48,4 @@ If your organization [requires members and outside collaborators to use two-fact
40
48
41
49
7. Next to the new collaborator's name, choose the appropriate permission level: *Write*, *Read*, or *Admin*.
Copy file name to clipboardExpand all lines: content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md
+7-8Lines changed: 7 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -14,9 +14,9 @@ topics:
14
14
- Organizations
15
15
- Teams
16
16
shortTitle: Repository permissions
17
-
---
17
+
permissions: People with admin permissions can manage individual and team access to an organization-owned repository.
18
18
19
-
People with admin permissions can manage individual and team access to an organization-owned repository.
19
+
---
20
20
21
21
## Permission levels for repositories owned by an organization
22
22
@@ -29,12 +29,6 @@ From least access to most access, the permission levels for an organization repo
29
29
-**Maintain**: Recommended for project managers who need to manage the repository without access to sensitive or destructive actions
30
30
-**Admin**: Recommended for people who need full access to the project, including sensitive and destructive actions like managing security or deleting a repository
31
31
32
-
{% ifversion fpt %}
33
-
34
-
{% endif %}
35
-
36
-
For more information about giving people and teams access to repositories, see "[Managing access to your organization's repositories](/articles/managing-access-to-your-organizations-repositories)."
37
-
38
32
Organization owners can set base permissions that apply to all members of an organization when accessing any of the organization's repositories. For more information, see "[Setting base permissions for an organization](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)."
39
33
40
34
Organization owners can also choose to further limit access to certain settings and actions across the organization. For more information on options for specific settings, see "[Managing organization settings](/articles/managing-organization-settings)."
@@ -48,6 +42,11 @@ In addition to managing organization-level settings, organization owners have ad
48
42
{% endwarning %}
49
43
50
44
## Repository access for each permission level
45
+
46
+
{% ifversion fpt %}
47
+
Some of the features listed below are limited to organizations using {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
Copy file name to clipboardExpand all lines: content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ If your organization is owned by an enterprise account, a "Verified" badge will
27
27
28
28
{% data reusables.organizations.verified-domains-details %}
29
29
30
-
On {% data variables.product.prodname_ghe_cloud %}, after verifying ownership of your organization's domain, you can restrict email notifications for the organization to that domain. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
30
+
On {% data variables.product.prodname_ghe_cloud %}, after verifying ownership of your organization's domain, you can restrict email notifications for the organization to that domain. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)." {% data reusables.enterprise.link-to-ghec-trial %}
0 commit comments