Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
Core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 933
    • Issues 933
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Development
  • Core
  • Issues
  • #831

Closed
Open
Opened Mar 28, 2019 by mattwire@mattwireDeveloper

Add permissions for edit (reserved) option groups

Currently you require "Administer CiviCRM" permission to edit option groups. But then you can edit ALL option groups including reserved ones that may break the system.

I propose adding the following two permissions:

  • Edit Option Groups
  • Edit Reserved Option Groups

This is similar to permissions for tags/groups etc.

We could also add a tabbed interface to option groups so that reserved/non-reserved are on separate tabs (And the reserved view could be hidden if you don't have permission?).

Use cases:

A counselling organisation manages a number of venues. Those venues change regularly and they update the option group that specifies those venues as required. They have no interest in any other option groups and certainly don't want to change reserved ones.

A "Teams" organisation has a set of attributes that they associate with teams. These need to be updated occasionally to add new attributes. The attributes are configured as option groups.

Edited Mar 28, 2019 by mattwire
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dev/core#831