Permissions Updates

Task Description

Permissions may change during an upgrade. Most of the time, permission changes will be documented in the release notes. Follow best practices set out in permission set creation principles.

As part of post-upgrade tasks, only permissions necessary to maintain current functionality should be updated. New functionality should be implemented with the assistance of Five Colleges FOLIO committees.

One of the most frequent post upgrade issues is developers failing to correctly assign base or immutable, invisible(II) permission sets to visible, immutable (VI) permission sets. This will likely be uncovered during acceptance testing. It is a candidate for a ticket but also easy to locally fix.

Repair VI permission Set

1. Gather report from user. The user should see an error indicating the missing CRUD level permission

2. Use the Permissions inspector - enable -invisible permissions - to identify which II permission contains the missing base permission

3. In Developer → Configuration enable invisible permissions

4. Create a new permission set, indicating the purpose of the set in the title, and the missing II and VI permission the set is meant to correct in the description. Under no circumstances mix VI and II permissions in a set.

5. Add the identified II permission to the permission set.

6. Add the set to the relevant permission set