1
0
mirror of synced 2026-01-05 12:07:35 -05:00

Revert "clarify limitations of project board visibility settings"

This reverts commit 8b6a02bc1f.
This commit is contained in:
Jules Parker
2021-08-24 09:32:37 +02:00
parent 8d01eef3eb
commit 84aba0b84c

View File

@@ -1,6 +1,6 @@
---
title: Changing project board visibility
intro: 'Account owners and project board admins can make their user owned or organization owned project boards {% ifversion ghae %}internal{% else %}public{% endif %} or private. Repository owned project boards inherit their visibility from the owning repository.'
intro: 'As an organization owner or project board admin, you can make a project board {% ifversion ghae %}internal{% else %}public{% endif %} or private.'
redirect_from:
- /github/managing-your-work-on-github/managing-project-boards/changing-project-board-visibility
- /articles/changing-project-board-visibility
@@ -19,7 +19,7 @@ shortTitle: Change visibility
{% tip %}
**Tip:** When you make your organization owned project board {% ifversion ghae %}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)."
**Tip:** When you make your project board {% ifversion ghae %}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)."
{% endtip %}