| Table of Contents |
|---|
What are invisible permissions?
FOLIO permissions have a concept being either "visible" or "invisible."
...
- 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?
Ideally, when you're working in the FOLIO UI, you never have to worry about invisible permissions, because the development process did the work of defining the visible permissions such that they include all the permissions you need to do your work.
However, because FOLIO is in active development, it does happen that you might need to assign an invisible permission to a user in order to troubleshoot a potential bug, or accomplish a workflow piece that can be handled no other way in FOLIO.
How can I see invisible permissions in the FOLIO UI?
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.
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.
How should I configure FOLIO to use invisible permissions with user accounts, if I need them to be able to be assigned to multiple staff while waiting for a fix to be released?
It is possible for one account (say, a systems administrator with access to developer settings) to assign individual permissions to multiple FOLIO users, however, if other users in the system don't also have the ability to see invisible permissions, the systems administrator's changes could potentially be overwritten.
...