Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Create permission for view all Inventory/Settings

CSP Request Details

None

CSP Rejection Details

None

CSP Approved

None

Description

Purpose: To provide a separate permission for view only of all Settings pages for Inventory. When given this permission the the user can view the settings pages, but not do any edit. Edit rights would be assigned as separate permissions, while some of the settings has tremendous effect on the given tenants configuration e.g. the permission which allows the user to adjust the HRID settings.

Scenarios:

  1. Scenario

    • Login to FOLIO Snapshot

    • Given the Settings module

    • When enabled

    • Then a logical permission should be provided called "Settings (Inventory): Display list of settings pages"

  2. Scenario

    • Given User A has been given the permission "Settings (Inventory): Display list of settings pages"

    • When User A accesses FOLIO

    • Then:

      • The Settings app should be visible in the top navigation bar

      • The Settings > Inventory menu with submenus can all be viewed

  3. Scenario

    • Given User A has been given the permission "Settings (Inventory): Display list of settings pages" as part of a custom permission set

    • When User A accesses FOLIO

    • Then User A should have all rights normally conferred by this permission (see scenario 2) plus whatever additional rights conferred by the users custom permission set.

Environment

None

Potential Workaround

None

Attachments

4

Checklist

hide

TestRail: Results

Activity

Show:

Charlotte Whitt November 8, 2019 at 1:58 PM

Manual test in FOLIO Snapshot, version permissions (mod-permissions-5.9.0-SNAPSHOT.67), using Chrome.

All is perfect. Thank you so much

I'll close the ticket as done.

Charlotte Whitt November 4, 2019 at 12:11 PM

and - the user should not see the action buttons if the given user has only view rights, and no action rights.
So my requirements are aligned with what describe, and the UX line which refer to.

and - where do you see permissions not following the pattern outlined by the POs and UX?

Cate Boerema November 4, 2019 at 9:26 AM

Direction from UX is if you don't have permissions to do something, that option should be hidden (not disabled) UNLESS there is an override capability available (e.g. for Change due date or Renew loans)

Ann-Marie Breaux November 1, 2019 at 4:20 PM

Hi My understanding of the general rule is that if someone does not have permission to do something, the fact that thing can be done should be as hidden as possible. So if they do not have permission to take any actions, they should not see the buttons or the column.

could you confirm?

Anna Melnyk November 1, 2019 at 3:32 PM

Hi, . The question is to hide '"actions" column, if I understand you right, if user does not have permissions and hide button 'New', and across the app column 'actions' exists, just buttons 'add', 'edit', 'delete' is just hiding. What is the final decision: just to hide buttons, or remove column 'actions'?

Done

Details

Assignee

Reporter

Tester Assignee

Priority

Story Points

Sprint

Development Team

Vega

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created October 15, 2019 at 10:02 AM
Updated October 27, 2023 at 2:09 AM
Resolved November 8, 2019 at 1:58 PM
TestRail: Cases
TestRail: Runs