Move public access page into user docs

This old page should be in the user docs, not in a top
level directory by itself.

doc/administration/clusters/kas.md

@@ -116,7 +116,7 @@ If you get the following error message:
 
 The project specified by the manifest (`root/kas-manifest001`)
 doesn't exist or the project where the manifest is kept is private. To fix this issue,
-ensure the project path is correct and that the project's visibility is [set to public](../../public_access/public_access.md).
+ensure the project path is correct and that the project's visibility is [set to public](../../user/public_access.md).
 
 ### Configuration file not found
 

doc/administration/index.md

@@ -146,7 +146,7 @@ Learn how to install, configure, update, and maintain your GitLab instance.
 - [Issue closing pattern](issue_closing_pattern.md): Customize how to close an issue from commit messages.
 - [Gitaly](gitaly/index.md): Configuring Gitaly, the Git repository storage service for GitLab.
 - [Default labels](../user/admin_area/labels.md): Create labels that are automatically added to every new project.
-- [Restrict the use of public or internal projects](../public_access/public_access.md#restrict-use-of-public-or-internal-projects): Restrict the use of visibility levels for users when they create a project or a snippet.
+- [Restrict the use of public or internal projects](../user/public_access.md#restrict-use-of-public-or-internal-projects): Restrict the use of visibility levels for users when they create a project or a snippet.
 - [Custom project templates](../user/admin_area/custom_project_templates.md): Configure a set of projects to be used as custom templates when creating a new project.
 
 ## Package Registry administration

doc/administration/monitoring/gitlab_self_monitoring_project/index.md

@@ -19,7 +19,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-and-groups).
+- With [internal visibility](../../../user/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/api/projects.md

@@ -19,7 +19,7 @@ Values for the project visibility level are:
 - `internal`: the project can be cloned by any signed-in user except [external users](../user/permissions.md#external-users).
 - `public`: the project can be accessed without any authentication.
 
-For more, read [Project visibility](../public_access/public_access.md).
+For more, read [Project visibility](../user/public_access.md).
 
 ## Project merge method
 

doc/ci/pipelines/merge_request_pipelines.md

@@ -147,7 +147,7 @@ a warning that you must accept before you can trigger the pipeline.
 Prerequisites:
 
 - You must be a member of the parent project and have at least the [Developer role](../../user/permissions.md).
-- The fork project must be [visible](../../public_access/public_access.md) to the
+- The fork project must be [visible](../../user/public_access.md) to the
   user running the pipeline. Otherwise, the **Pipelines** tab does not display
   in the merge request.
 

doc/ci/pipelines/multi_project_pipelines.md

@@ -282,7 +282,7 @@ tag in a different project.
 
 Prerequisites:
 
-- The upstream project must be [public](../../public_access/public_access.md).
+- The upstream project must be [public](../../user/public_access.md).
 - The user must have the Developer role
   in the upstream project.
 

doc/integration/omniauth.md

@@ -197,7 +197,7 @@ To enable automatic linking for SAML, see the [SAML setup instructions](saml.md#
 ## Create an external providers list
 
 You can define a list of external OmniAuth providers.
-Users who create accounts or sign in to GitLab through the listed providers do not get access to [internal projects](../public_access/public_access.md#internal-projects-and-groups).
+Users who create accounts or sign in to GitLab through the listed providers do not get access to [internal projects](../user/public_access.md#internal-projects-and-groups).
 
 To define the external providers list, use the full name of the provider,
 for example, `google_oauth2` for Google. For provider names, see the

doc/public_access/public_access.md

 ---
-stage: Manage
-group: Workspace
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
-type: reference
+redirect_to: '../user/public_access.md'
+remove_date: '2022-06-18'
 ---
 
-# Project and group visibility **(FREE)**
+This document was moved to [another location](../user/public_access.md).
 
-GitLab allows users with the Owner role to set a project's or group's visibility as:
-
-- **Public**
-- **Internal**
-- **Private**
-
-These visibility levels affect who can see the project in the public access directory (`/public`
-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 and groups
-
-Public projects can be cloned **without any** authentication over HTTPS.
-
-They are listed in the public access directory (`/public`) for all users.
-
-**Any signed-in user** has the Guest role on the repository.
-
-NOTE:
-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 and groups
-
-Internal projects can be cloned by any signed-in user except
-[external users](../user/permissions.md#external-users).
-
-They are also listed in the public access directory (`/public`), but only for signed-in users.
-
-Any signed-in users except [external users](../user/permissions.md#external-users) have the
-Guest role on the repository.
-
-NOTE:
-From July 2019, the `Internal` visibility setting is disabled for new projects, groups,
-and snippets on GitLab.com. Existing projects, groups, and snippets using the `Internal`
-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 and groups
-
-Private projects can only be cloned and viewed by project members (except for guests).
-
-They appear in the public access directory (`/public`) for project members only.
-
-## Change project visibility
-
-Prerequisite:
-
-- You must have the Owner role for a project.
-
-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 **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 **(FREE SELF)**
-
-You can restrict the use of visibility levels for users when they create a project or a snippet.
-This is useful to prevent users from publicly exposing their repositories by accident. The
-restricted visibility settings do not apply to administrators.
-
-For details, see [Restricted visibility levels](../user/admin_area/settings/visibility_and_access_controls.md#restrict-visibility-levels).
-
-<!-- ## Troubleshooting
-
-Include any troubleshooting steps that you can foresee. If you know beforehand what issues
-one might have when setting this up, or when something is changed, or on upgrading, it's
-important to describe those, too. Think of things that may go wrong and include them here.
-This is important to minimize requests for support, and to avoid doc comments with
-questions that you know someone might ask.
-
-Each scenario can be a third-level heading, e.g. `### Getting error message X`.
-If you have none to add when creating a doc, leave this section in place
-but commented out to help encourage others to add to it in the future. -->
+<!-- This redirect file can be deleted after <2022-06-18>. -->
+<!-- Redirects that point to other docs in the same project expire in three months. -->
+<!-- Redirects that point to docs in a different project or site (for example, link is not relative and starts with `https:`) expire in one year. -->
+<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/redirects.html -->

doc/user/admin_area/settings/visibility_and_access_controls.md

@@ -87,7 +87,7 @@ Alternatively, projects that are marked for removal can be deleted immediately.
 
 ## Configure project visibility defaults
 
-To set the default [visibility levels for new projects](../../../public_access/public_access.md):
+To set the default [visibility levels for new projects](../../public_access.md):
 
 1. Sign in to GitLab as a user with Administrator access level.
 1. On the top bar, select **Menu > Admin**.
@@ -112,7 +112,7 @@ To set the default visibility levels for new [snippets](../../snippets.md):
 1. Select **Save changes**.
 
 For more details on snippet visibility, read
-[Project visibility](../../../public_access/public_access.md).
+[Project visibility](../../public_access.md).
 
 ## Configure group visibility defaults
 
@@ -146,7 +146,7 @@ To restrict visibility levels for projects, snippets, and selected pages:
 1. Select **Save changes**.
 
 For more details on project visibility, see
-[Project visibility](../../../public_access/public_access.md).
+[Project visibility](../../public_access.md).
 
 ## Configure allowed import sources
 
@@ -162,7 +162,7 @@ You can specify from which hosting sites users can [import their projects](../..
 ## Enable project export
 
 To enable the export of
-[projects and their data](../../../user/project/settings/import_export.md#export-a-project-and-its-data):
+[projects and their data](../../project/settings/import_export.md#export-a-project-and-its-data):
 
 1. Sign in to GitLab as a user with Administrator access level.
 1. On the top bar, select **Menu > Admin**.

doc/user/gitlab_com/index.md

@@ -395,7 +395,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-and-groups)
+[Internal visibility](../public_access.md#internal-projects-and-groups)
 setting [disabled on GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/12388):
 
 - Projects

doc/user/group/index.md

@@ -68,7 +68,7 @@ To create a group:
 1. Enter a name for the group in **Group name**. For a list of words that cannot be used as group names, see
    [reserved names](../reserved_names.md).
 1. Enter a path for the group in **Group URL**, which is used for the [namespace](#namespaces).
-1. Choose the [visibility level](../../public_access/public_access.md).
+1. Choose the [visibility level](../public_access.md).
 1. Personalize your GitLab experience by answering the following questions:
    - What is your role?
    - Who will be using this group?

doc/user/permissions.md

@@ -149,7 +149,7 @@ The following table lists project permissions available for each role:
 | [Projects](project/index.md):<br>View project [Audit Events](../administration/audit_events.md)                                                                            |          |          | ✓ (*10*)  | ✓          | ✓        |
 | [Projects](project/index.md):<br>Add deploy keys                                                                                                                           |          |          |           | ✓          | ✓        |
 | [Projects](project/index.md):<br>Add new team members                                                                                                                      |          |          |           | ✓          | ✓        |
-| [Projects](project/index.md):<br>Change [project features visibility](../public_access/public_access.md) level                                                             |          |          |           | ✓ (*13*)   | ✓        |
+| [Projects](project/index.md):<br>Change [project features visibility](public_access.md) level                                                             |          |          |           | ✓ (*13*)   | ✓        |
 | [Projects](project/index.md):<br>Configure [webhooks](project/integrations/webhooks.md)                                                                                    |          |          |           | ✓          | ✓        |
 | [Projects](project/index.md):<br>Delete [wiki](project/wiki/index.md) pages                                                                                                |          |          | ✓         | ✓          | ✓        |
 | [Projects](project/index.md):<br>Edit comments (posted by any user)                                                                                                        |          |          |           | ✓          | ✓        |
@@ -224,7 +224,7 @@ The following table lists project permissions available for each role:
     supported on GitLab SaaS Premium and above (excluding [trial licenses](https://about.gitlab.com/free-trial/)).
 12. If the [tag is protected](#release-permissions-with-protected-tags), this depends on the access Developers and Maintainers are given.
 13. A Maintainer can't change project features visibility level if
-    [project visibility](../public_access/public_access.md) is set to private.
+    [project visibility](public_access.md) is set to private.
 14. Attached design files are moved together with the issue even if the user doesn't have the
     Developer role.
 15. Guest users can only set metadata (for example, labels, assignees, or milestones)

doc/user/project/import/github.md

@@ -30,7 +30,7 @@ The following aspects of a project are imported:
 
 References to pull requests and issues are preserved (GitLab.com & 8.7+), and
 each imported repository maintains visibility level unless that [visibility
-level is restricted](../../../public_access/public_access.md#restrict-use-of-public-or-internal-projects),
+level is restricted](../../public_access.md#restrict-use-of-public-or-internal-projects),
 in which case it defaults to the default project visibility.
 
 The namespace is a user or group in GitLab, such as `gitlab.com/janedoe` or

doc/user/project/index.md

@@ -11,7 +11,7 @@ your codebase. You can also use projects to track issues, plan work,
 collaborate on code, and continuously build, test, and use
 built-in CI/CD to deploy your app.
 
-Projects can be available [publicly, internally, or privately](../../public_access/public_access.md).
+Projects can be available [publicly, internally, or privately](../public_access.md).
 GitLab does not limit the number of private projects you can create.
 
 ## Project features

doc/user/project/repository/forking_workflow.md

@@ -32,7 +32,7 @@ To fork an existing project in GitLab:
    It must be unique in the namespace.
 1. Optional. Add a **Project description**.
 1. Select the **Visibility level** for your fork. For more information about
-   visibility levels, read [Project and group visibility](../../../public_access/public_access.md).
+   visibility levels, read [Project and group visibility](../../public_access.md).
 1. Select **Fork project**.
 
 GitLab creates your fork, and redirects you to the new fork's page.

doc/user/project/settings/import_export.md

@@ -127,7 +127,7 @@ The following items are imported but changed slightly:
   associated with such merge requests are created in a project during the import/export. Thus, the
   number of branches in the exported project might be bigger than in the original project.
 - If use of the `Internal` visibility level
-  [is restricted](../../../public_access/public_access.md#restrict-use-of-public-or-internal-projects),
+  [is restricted](../../public_access.md#restrict-use-of-public-or-internal-projects),
   all imported projects are given `Private` visibility.
 
 Deploy keys aren't imported. To use deploy keys, you must enable them in your imported project and update protected branches.

doc/user/project/settings/index.md

@@ -242,7 +242,7 @@ documentation, access permissions, and more. To do so from your project,
 go to **Settings** > **General**, and expand the **Visibility, project features, permissions**
 section.
 
-You can now change the [Project visibility](../../../public_access/public_access.md).
+You can now change the [Project visibility](../../public_access.md).
 If you set **Project Visibility** to public, you can limit access to some features
 to **Only Project Members**. In addition, you can select the option to
 [Allow users to request access](../members/index.md#request-access-to-a-project).

doc/user/project/working_with_projects.md

@@ -99,7 +99,7 @@ To create a blank project:
    - In the **Project description (optional)** field, enter the description of your project's dashboard.
    - In the **Project target (optional)** field, select your project's deployment target.
      This information helps GitLab better understand its users and their deployment requirements.
-   - To modify the project's [viewing and access rights](../../public_access/public_access.md) for
+   - To modify the project's [viewing and access rights](../public_access.md) for
    users, change the **Visibility Level**.
    - To create README file so that the Git repository is initialized, has a default branch, and
      can be cloned, select **Initialize repository with a README**.
@@ -132,7 +132,7 @@ To create a project from a built-in template:
      slug as the URL path to the project. To change the slug, first enter the project name,
      then change the slug.
    - In the **Project description (optional)** field, enter the description of your project's dashboard.
-   - To modify the project's [viewing and access rights](../../public_access/public_access.md) for users,
+   - To modify the project's [viewing and access rights](../public_access.md) for users,
       change the **Visibility Level**.
 1. Select **Create project**.
 
@@ -158,7 +158,7 @@ Custom project templates are available at:
      slug as the URL path to the project. To change the slug, first enter the project name,
      then change the slug.
    - The description of your project's dashboard in the **Project description (optional)** field.
-   - To modify the project's [viewing and access rights](../../public_access/public_access.md) for users,
+   - To modify the project's [viewing and access rights](../public_access.md) for users,
       change the **Visibility Level**.
 1. Select **Create project**.
 
@@ -184,7 +184,7 @@ To create a project from the HIPAA Audit Protocol template:
      slug as the URL path to the project. To change the slug, first enter the project name,
      then change the slug.
    - In the **Project description (optional)** field, enter the description of your project's dashboard.
-   - To modify the project's [viewing and access rights](../../public_access/public_access.md) for users,
+   - To modify the project's [viewing and access rights](../public_access.md) for users,
       change the **Visibility Level**.
 1. Select **Create project**.
 
@@ -250,7 +250,7 @@ remote: The private project namespace/myproject was created.
 
 To view your new project, go to `https://gitlab.example.com/namespace/myproject`.
 Your project's visibility is set to **Private** by default. To change project visibility, adjust your
-[project's settings](../../public_access/public_access.md#change-project-visibility).
+[project's settings](../public_access.md#change-project-visibility).
 
 ## Star a project
 

doc/user/public_access.md

+---
+stage: Manage
+group: Workspace
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
+type: reference
+---
+
+# Project and group visibility **(FREE)**
+
+GitLab allows users with the Owner role to set a project's or group's visibility as:
+
+- **Public**
+- **Internal**
+- **Private**
+
+These visibility levels affect who can see the project in the public access directory (`/public`
+for your GitLab instance). For example, <https://gitlab.com/public>.
+You can control the visibility of individual features with
+[project feature settings](permissions.md#project-features).
+
+## Public projects and groups
+
+Public projects can be cloned **without any** authentication over HTTPS.
+
+They are listed in the public access directory (`/public`) for all users.
+
+**Any signed-in user** has the Guest role on the repository.
+
+NOTE:
+By default, `/public` is visible to unauthenticated users. However, if the
+[**Public** visibility level](admin_area/settings/visibility_and_access_controls.md#restrict-visibility-levels)
+is restricted, `/public` is visible only to signed-in users.
+
+## Internal projects and groups
+
+Internal projects can be cloned by any signed-in user except
+[external users](permissions.md#external-users).
+
+They are also listed in the public access directory (`/public`), but only for signed-in users.
+
+Any signed-in users except [external users](permissions.md#external-users) have the
+Guest role on the repository.
+
+NOTE:
+From July 2019, the `Internal` visibility setting is disabled for new projects, groups,
+and snippets on GitLab.com. Existing projects, groups, and snippets using the `Internal`
+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 and groups
+
+Private projects can only be cloned and viewed by project members (except for guests).
+
+They appear in the public access directory (`/public`) for project members only.
+
+## Change project visibility
+
+Prerequisite:
+
+- You must have the Owner role for a project.
+
+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 **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 **(FREE SELF)**
+
+You can restrict the use of visibility levels for users when they create a project or a snippet.
+This is useful to prevent users from publicly exposing their repositories by accident. The
+restricted visibility settings do not apply to administrators.
+
+For details, see [Restricted visibility levels](admin_area/settings/visibility_and_access_controls.md#restrict-visibility-levels).
+
+<!-- ## Troubleshooting
+
+Include any troubleshooting steps that you can foresee. If you know beforehand what issues
+one might have when setting this up, or when something is changed, or on upgrading, it's
+important to describe those, too. Think of things that may go wrong and include them here.
+This is important to minimize requests for support, and to avoid doc comments with
+questions that you know someone might ask.
+
+Each scenario can be a third-level heading, e.g. `### Getting error message X`.
+If you have none to add when creating a doc, leave this section in place
+but commented out to help encourage others to add to it in the future. -->

doc/user/snippets.md

@@ -22,7 +22,7 @@ using the [GitLab Workflow VS Code extension](project/repository/vscode.md).
 GitLab provides two types of snippets:
 
 - **Personal snippets**: Created independent of any project.
-  You can set a [visibility level](../public_access/public_access.md)
+  You can set a [visibility level](public_access.md)
   for your snippet: public, internal, or private.
 - **Project snippets**: Always related to a specific project.
   Project snippets can be visible publicly or to only group members.