| Table of Contents |
|---|
...
What are invisible permissions?
FOLIO permissions have a concept being either "visible" or "invisible."
Whether a permission is visible or invisible is defined by the developer who creates the permission.
Invisible Visible permissions are generally (though not always):
- Defined in a back-end module, not as part of a user-interface module;
- Extremely granular - they may control one action in one function, for example, fetching a single record type in a single module;
- Not named in a super readable way. They have names like "circulation-rules.storage.get" or"item.record.put".
usually what a FOLIO user thinks of when they think of permissions. Visible permissions are generally (though not always):
- Defined in a front-end UI module;
- Groups of very granular (sometimes visible, sometimes invisible) permissions that are clumped together into one permission with one name;
- Defined with a friendly name that displays (via translation) in the FOLIO UI. They have names like "Settings (Users): Can create, edit and remove patron groups" or "Finance: View Ledger"
Invisible permissions are generally (though not always):
- Defined in a back-end module, not as part of a user-interface module;
- Extremely granular - they may control one action in one function, for example, fetching a single record type in a single module;
- Not named in a super readable way. They have names like "circulation-rules.storage.get" or"item.record.put".
Why would I want to know about invisible permissions?
...
The ability to see invisible permissions is determined user-by-user. The logged-in user must have access to Settings → Developer. In Settings → Developer → Configuration, check the box for 'List 'invisible' permissions in add-perm menus?', and Save your changes.
It's not recommended to You should not leave this setting on permanently – – there are over 4,000 permissions in FOLIO (visible and invisible together), and displaying invisible permissions will significantly slow down the add-perms user interface.
...