Skip to content
Snippets Groups Projects
Select Git revision
  • ag-test
  • rs-test
  • master default protected
  • test-me-pa
  • mksionek-master-patch-52381
  • new-branch-10
  • test-conflicts
  • test-suggestions
  • alejandro-test
  • patch-25
  • winh-test-image-doscussion
  • stg-lfs-image-test-2
  • stg-lfs-image-test
  • test42016
  • issue_42016
  • issue-32709
  • add-codeowners
  • ClemMakesApps-master-patch-62759
  • bvl-staging-test
  • bvl-merge-base-api
  • v9.2.0-rc6 protected
  • v9.2.0-rc5 protected
  • v9.2.0-rc4 protected
  • v9.2.0-rc3 protected
  • v9.1.4 protected
  • v9.2.0-rc2 protected
  • v9.2.0-rc1 protected
  • v9.1.3 protected
  • v8.17.6 protected
  • v9.0.7 protected
  • v9.1.2 protected
  • v9.1.1 protected
  • v9.2.0.pre protected
  • v9.1.0 protected
  • v9.1.0-rc7 protected
  • v9.1.0-rc6 protected
  • v9.0.6 protected
  • v9.1.0-rc5 protected
  • v9.1.0-rc4 protected
  • v9.1.0-rc3 protected
40 results

permissions.md

Blame
  • Code owners
    Assign users and groups as approvers for specific file changes. Learn more.
    permissions.md 4.07 KiB

    Permissions

    Users have different abilities depending on the access level they have in a particular group or project.

    If a user is both in a project group and in the project itself, the highest permission level is used.

    If a user is a GitLab administrator they receive all permissions.

    Project

    Action Guest Reporter Developer Master Owner
    Create new issue
    Leave comments
    Pull project code
    Download project
    Create code snippets
    Create new merge request
    Create new branches
    Push to non-protected branches
    Force push to non-protected branches
    Remove non-protected branches
    Add tags
    Write a wiki
    Manage issue tracker
    Manage labels
    Create new milestones
    Add new team members
    Push to protected branches
    Enable/disable branch protection
    Turn on/off prot. branch push for devs
    Rewrite/remove git tags
    Edit project
    Add deploy keys to project
    Configure project hooks
    Switch visibility level
    Transfer project to another namespace
    Remove project
    Force push to protected branches
    Remove protected branches

    Group

    In order for a group to appear as public and be browsable, it must contain at least one public project.

    Any user can remove themselves from a group, unless they are the last Owner of the group.

    Action Guest Reporter Developer Master Owner
    Browse group
    Edit group
    Create project in group
    Manage group members
    Remove group