Uploaded image for project: 'Stripes'
  1. Stripes
  2. STRIPES-468

We need permissions for each module's settings

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: P3
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:

      Description

      At present, if the user has the settings.enabled permisson, then the Settings link is enabled – quite rightly – but then clicking on that link offers settings for each module, even when the user does not have permissions to use any of the module's settings.

      We can fix this:

      • Each module should define an additional permission, settings.NAME.enabled, and the <Settings> component should display the module's permissions only if this is defined.
      • Each settings.NAME.enabled permission should include settings.enabled as a sub-permission.
      • Each permission for a specific part of the settings (e.g. settings.usergroups.all in the ui-users module) should include the relevant module-wide settings permission (in this case settings.users.enabled).

      Then users will see only those settings areas that they have permission to use some part of.

        TestRail: Results

          Attachments

            Issue Links

            blocks

            New Feature - New feature requests STCOR-72 stripes-core's Settings menu should only display a module's entry if relevant permission exists

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICIRC-21 Permission Set for Loan Policy CRUD

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIT-38 Permission Set for Loan Type CRUD

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIT-39 Permission Set for Material Type CRUD

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIU-130 Permission Set for Patron Group CRUD

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            is blocked by

            New Feature - New feature requests UID-8 Add permission for developer settings

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            relates to

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. LIBAPP-151 Permissions: Can Create, Edit and Remove Permission Sets

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Task - A task that needs to be done. FOLIO-763 Top-to-bottom understanding of permissions

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests STRIPES-469 Add permission-guards for each settings page

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

              Activity

                People

                Assignee:
                mike Mike Taylor
                Reporter:
                mike Mike Taylor
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 2 hours
                    2h

                      TestRail: Runs

                        TestRail: Cases