Skip to content

GitLab Next

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 43,084
    • Issues 43,084
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,380
    • Merge requests 1,380
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

GitLab 15.0 has launched! Please visit Breaking changes in 15.0 and 15.0 Removals to see which breaking changes may impact your workflow.

  • GitLab.org
  • GitLabGitLab
  • Issues
  • #12388
Closed
Open
Created Jun 24, 2019 by Joshua Lambert@joshlambertMaintainer

Disable `Internal` visibility setting on GitLab.com

Problem statement

The Internal project visibility can be misleading to users, especially on a public shared service like GitLab.com. Internal seems to convey some type of security, but on GitLab.com means anyone can access it, because sign ups are open.

Proposed solution

Disable the Internal visibility setting on GitLab.com by restricting this visibility setting in the admin panel.

Tested behavior

When enabled on an existing instance:

  • New projects, groups, and snippets cannot be created with an Internal visibility setting. This option is greyed out:

image

  • Existing projects, groups, and snippets with a visibility setting of Internal remain Internal. The visibility on these objects can only be modified to Public or Private.

  • Attempting to create via the API fails with "message": {"visibility_level": ["internal has been restricted by your GitLab administrator"].

  • Admins can create projects, groups, and snippets with any visibility level, including Internal, via the UI or API.

Edited Jun 26, 2019 by Jeremy Watson (ex-GitLab)
Assignee
Assign to
Time tracking