Skip to content

Commit 43eee44

Browse files
authored
Branch was updated using the 'autoupdate branch' Actions workflow.
2 parents d67a42e + 4baf121 commit 43eee44

39 files changed

Lines changed: 245 additions & 158 deletions

File tree

3.37 KB
Loading
23.9 KB
Loading
21.2 KB
Loading
17.3 KB
Loading
15.2 KB
Loading
Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Changing project board visibility
3-
intro: 'As an organization owner or project board admin, you can make a project board public or private.'
3+
intro: 'As an organization owner or project board admin, you can make a project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private.'
44
redirect_from:
55
- /articles/changing-project-board-visibility
66
versions:
@@ -13,12 +13,12 @@ versions:
1313

1414
{% tip %}
1515

16-
**Tip:** When you make your project board public, organization members are given read access by default. You can give specific organization members write or admin permissions by giving project board access to teams they're on or by adding them to the project board as a collaborator. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)."
16+
**Tip:** When you make your project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %}, organization members are given read access by default. You can give specific organization members write or admin permissions by giving project board access to teams they're on or by adding them to the project board as a collaborator. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)."
1717

1818
{% endtip %}
1919

20-
1. Navigate to the project board you want to make public or private.
20+
1. Navigate to the project board you want to make {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private.
2121
{% data reusables.project-management.click-menu %}
2222
{% data reusables.project-management.access-collaboration-settings %}
23-
4. Under "Visibility", select **Public** or **Private**. Then, click **Save**.
24-
![Public and private radio buttons](/assets/images/help/projects/project-board-visibility-options.png)
23+
{% data reusables.project-management.choose-visibility %}
24+
1. Click **Save**.

content/github/managing-your-work-on-github/copying-a-project-board.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,6 @@ A project board's automation is also enabled by default. For more information, s
2727
![Field to type a description for the copied project board](/assets/images/help/projects/copied-project-board-description.png)
2828
7. Optionally, under "Automation settings", select whether you want to copy the configured automatic workflows. This option is enabled by default. For more information, see "[About automation for project boards](/articles/about-automation-for-project-boards/)."
2929
![Select automation settings for copied project board](/assets/images/help/projects/copied-project-board-automation-settings.png)
30-
8. If you are copying an organization-owned project board, under "Visibility", select whether you want your copied project board to be private or public.
31-
![Select visibility settings for copied project board](/assets/images/help/projects/copied-project-board-visibility-settings.png)
30+
{% data reusables.project-management.choose-visibility %}
3231
9. Click **Copy project**.
3332
![Confirm Copy button](/assets/images/help/projects/confirm-copy-project-board.png)

content/github/managing-your-work-on-github/creating-a-project-board.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,7 @@ You can also configure workflow automations to keep your project board in sync w
3030
{% data reusables.project-management.click-new-project %}
3131
{% data reusables.project-management.create-project-name-description %}
3232
{% data reusables.project-management.choose-template %}
33+
{% data reusables.project-management.choose-visibility %}
3334
{% data reusables.project-management.linked-repositories %}
3435
{% data reusables.project-management.create-project-button %}
3536
{% data reusables.project-management.add-column-new-project %}
@@ -49,6 +50,7 @@ You can also configure workflow automations to keep your project board in sync w
4950
{% data reusables.project-management.click-new-project %}
5051
{% data reusables.project-management.create-project-name-description %}
5152
{% data reusables.project-management.choose-template %}
53+
{% data reusables.project-management.choose-visibility %}
5254
{% data reusables.project-management.linked-repositories %}
5355
{% data reusables.project-management.create-project-button %}
5456
{% data reusables.project-management.add-column-new-project %}

content/github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ versions:
1414

1515
After you configure SAML SSO, members of your {% data variables.product.prodname_dotcom %} organization will continue to log into their user accounts on {% data variables.product.prodname_dotcom %}. When a member accesses resources within your organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} redirects the member to your IdP to authenticate. After successful authentication, your IdP redirects the member back to {% data variables.product.prodname_dotcom %}, where the member can access your organization's resources.
1616

17-
Enterprise owners can also enforce SAML SSO for all organizations in an enterprise account. For more information, see "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)."
17+
Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. For more information, see "[Enabling SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account)."
1818

1919
{% data reusables.saml.outside-collaborators-exemption %}
2020

@@ -32,6 +32,8 @@ If members are signed in with a SAML SSO session when they create a new reposito
3232

3333
Organization members must also have an active SAML session to authorize an {% data variables.product.prodname_oauth_app %}. You can opt out of this requirement by contacting {% data variables.contact.contact_support %}. {% data variables.product.product_name %} does not recommend opting out of this requirement, which will expose your organization to a higher risk of account takeovers and potential data loss.
3434

35+
{% data reusables.saml.saml-single-logout-not-supported %}
36+
3537
### Supported SAML services
3638

3739
{% data reusables.saml.saml-supported-idps %}
@@ -42,12 +44,12 @@ Some IdPs support provisioning access to a {% data variables.product.prodname_d
4244

4345
After you enable SAML SSO, there are multiple ways you can add new members to your organization. Organization owners can invite new members manually on {% data variables.product.product_name %} or using the API. For more information, see "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)" and "[Members](/rest/reference/orgs#add-or-update-organization-membership)."
4446

45-
{% data reusables.organizations.team-synchronization %}
46-
4747
To provision new users without an invitation from an organization owner, you can use the URL `https://github.com/orgs/ORGANIZATION/sso/sign_up`, replacing _ORGANIZATION_ with the name of your organization. For example, you can configure your IdP so that anyone with access to the IdP can click a link on the IdP's dashboard to join your {% data variables.product.prodname_dotcom %} organization.
4848

4949
If your IdP supports SCIM, {% data variables.product.prodname_dotcom %} can automatically invite members to join your organization when you grant access on your IdP. If you remove a member's access to your {% data variables.product.prodname_dotcom %} organization on your SAML IdP, the member will be automatically removed from the {% data variables.product.prodname_dotcom %} organization. For more information, see "[About SCIM](/github/setting-up-and-managing-organizations-and-teams/about-scim)."
5050

51+
{% data reusables.organizations.team-synchronization %}
52+
5153
{% data reusables.saml.saml-single-logout-not-supported %}
5254

5355
### Further reading

content/github/setting-up-and-managing-organizations-and-teams/about-scim.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ These identity providers are compatible with the {% data variables.product.produ
1717
- Okta
1818
- OneLogin
1919

20-
{% data reusables.scim.enterprise-account-scim %} For more information, see "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#managing-user-provisioning-for-organizations-in-your-enterprise-account)."
20+
{% data reusables.scim.enterprise-account-scim %} For more information, see "[About user provisioning for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account)."
2121

2222
### Further reading
2323

0 commit comments

Comments
 (0)