Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
e68b424d
Commit
e68b424d
authored
Sep 09, 2021
by
Marcin Sedlak-Jakubowski
Committed by
Amy Qualls
Sep 09, 2021
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Mention groups in project visibility docs
parent
8737cd0a
Changes
4
Hide whitespace changes
Inline
Side-by-side
Showing
4 changed files
with
22 additions
and
9 deletions
+22
-9
doc/administration/monitoring/gitlab_self_monitoring_project/index.md
...ration/monitoring/gitlab_self_monitoring_project/index.md
+1
-1
doc/public_access/public_access.md
doc/public_access/public_access.md
+18
-6
doc/user/gitlab_com/index.md
doc/user/gitlab_com/index.md
+1
-1
doc/user/permissions.md
doc/user/permissions.md
+2
-1
No files found.
doc/administration/monitoring/gitlab_self_monitoring_project/index.md
View file @
e68b424d
...
...
@@ -14,7 +14,7 @@ GitLab provides administrators insights into the health of their GitLab instance
To provide a native experience (similar interacting with an application deployed using GitLab), a
project called
**Monitoring**
is created:
-
With
[
internal visibility
](
../../../public_access/public_access.md#internal-projects
)
.
-
With
[
internal visibility
](
../../../public_access/public_access.md#internal-projects
-and-groups
)
.
-
Under a group called
**GitLab Instance**
.
The project is created specifically for visualizing and configuring the monitoring of your GitLab
...
...
doc/public_access/public_access.md
View file @
e68b424d
...
...
@@ -5,9 +5,9 @@ info: To determine the technical writer assigned to the Stage/Group associated w
type
:
reference
---
# Project visibility
# Project
and group
visibility
GitLab allows
[
Owners
](
../user/permissions.md
)
to set a project's visibility as:
GitLab allows
[
Owners
](
../user/permissions.md
)
to set a project's
or group's
visibility as:
-
**Public**
-
**Internal**
...
...
@@ -18,7 +18,7 @@ for your GitLab instance). For example, <https://gitlab.com/public>.
You can control the visibility of individual features with
[
project feature settings
](
../user/permissions.md#project-features
)
.
## Public projects
## Public projects
and groups
Public projects can be cloned
**without any**
authentication over HTTPS.
...
...
@@ -31,7 +31,7 @@ By default, `/public` is visible to unauthenticated users. However, if the
[
**Public** visibility level
](
../user/admin_area/settings/visibility_and_access_controls.md#restrict-visibility-levels
)
is restricted,
`/public`
is visible only to signed-in users.
## Internal projects
## Internal projects
and groups
Internal projects can be cloned by any signed-in user except
[
external users
](
../user/permissions.md#external-users
)
.
...
...
@@ -47,7 +47,7 @@ and snippets on GitLab.com. Existing projects, groups, and snippets using the `I
visibility setting keep this setting. You can read more about the change in the
[
relevant issue
](
https://gitlab.com/gitlab-org/gitlab/-/issues/12388
)
.
## Private projects
## Private projects
and groups
Private projects can only be cloned and viewed by project members (except for guests).
...
...
@@ -62,7 +62,19 @@ Prerequisite:
1.
On the top bar, select
**Menu > Projects**
and find your project.
1.
On the left sidebar, select
**Settings > General**
.
1.
Expand
**Visibility, project features, permissions**
.
1.
Change
**Project visibility**
to either Public, Internal, or Private.
1.
Change
**Project visibility**
to either
**Private**
,
**Internal**
, or
**Public**
.
1.
Select
**Save changes**
.
## Change group visibility
Prerequisite:
-
You must have the Owner role for a group.
1.
On the top bar, select
**Menu > Groups**
and find your project.
1.
On the left sidebar, select
**Settings > General**
.
1.
Expand
**Naming, visibility**
.
1.
Under
**Visibility level**
select either
**Private**
,
**Internal**
, or
**Public**
.
1.
Select
**Save changes**
.
## Restrict use of public or internal projects
...
...
doc/user/gitlab_com/index.md
View file @
e68b424d
...
...
@@ -362,7 +362,7 @@ doesn't return the following headers:
### Visibility settings
If created before GitLab 12.2 (July 2019), these items have the
[
Internal visibility
](
../../public_access/public_access.md#internal-projects
)
[
Internal visibility
](
../../public_access/public_access.md#internal-projects
-and-groups
)
setting
[
disabled on GitLab.com
](
https://gitlab.com/gitlab-org/gitlab/-/issues/12388
)
:
-
Projects
...
...
doc/user/permissions.md
View file @
e68b424d
...
...
@@ -280,6 +280,7 @@ The following table lists group permissions available for each role:
|--------------------------------------------------------|-------|----------|-----------|------------|-------|
| Browse group | ✓ | ✓ | ✓ | ✓ | ✓ |
| Edit SAML SSO Billing
**(PREMIUM SAAS)**
| ✓ | ✓ | ✓ | ✓ | ✓ (4) |
| Pull a container image using the dependency proxy | ✓ | ✓ | ✓ | ✓ | ✓ |
| View Contribution analytics | ✓ | ✓ | ✓ | ✓ | ✓ |
| View group epic
**(PREMIUM)**
| ✓ | ✓ | ✓ | ✓ | ✓ |
| View group wiki pages
**(PREMIUM)**
| ✓ (6) | ✓ | ✓ | ✓ | ✓ |
...
...
@@ -301,7 +302,6 @@ The following table lists group permissions available for each role:
| Create/edit/delete iterations | | | ✓ | ✓ | ✓ |
| Create/edit/delete metrics dashboard annotations | | | ✓ | ✓ | ✓ |
| Enable/disable a dependency proxy | | | ✓ | ✓ | ✓ |
| Pull a container image using the dependency proxy | ✓ | ✓ | ✓ | ✓ | ✓ |
| Purge the dependency proxy for a group | | | | | ✓ |
| Publish
[
packages
](
packages/index.md
)
| | | ✓ | ✓ | ✓ |
| Use security dashboard
**(ULTIMATE)**
| | | ✓ | ✓ | ✓ |
...
...
@@ -314,6 +314,7 @@ The following table lists group permissions available for each role:
| View/manage group-level Kubernetes cluster | | | | ✓ | ✓ |
| Administer project compliance frameworks | | | | | ✓ |
| Create/Delete group deploy tokens | | | | | ✓ |
| Change group visibility level | | | | | ✓ |
| Delete group | | | | | ✓ |
| Delete group epic
**(PREMIUM)**
| | | | | ✓ |
| Disable notification emails | | | | | ✓ |
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment