Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 35,879
    • Issues 35,879
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,257
    • Merge Requests 1,257
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #1439

Closed
Open
Opened Jul 12, 2016 by Drew Blessing@dblessingMaintainer

Auditor user with read-only access

Resources

FE/BE @timothyandrew | UX @cperessini

Requirements

  • As a system admin, create a user in a special role called Auditor.
  • The user has read access to all projects and groups, and all the components therein (issues, merge requests, etc.). The user cannot create or make any changes to these existing components.
  • This is the view of the access section in the new user menu.
    • There should be a new option to set the user as an Auditor.

Design

Remove the checkbox for Admin user type and add radio buttons for Admin, Auditor and Regular user types.

Since a user cannot be External if they are Admin or Auditor, that checkbox will be disabled unless the user is Regular access-level

Original description

Zendesk ticket: https://gitlab.zendesk.com/agent/tickets/29453

Customer is requesting that we add the option for global read-only users. In this case, the compliance department wants to run tests against the entire GitLab base to ensure users are complying with password, credit card, and other sensitive data policies. The only option currently is to 1) give them admin rights or 2) use the API to add their user to all projects.

cc/ @JobV What do you think?

Assignee
Assign to
8.17
Milestone
8.17 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab#1439