Troubleshooting why a user cannot see library records
The Library is a great place to store your procedures, polices and reference information, however it is typically configured as a global event and this can present some difficulty with some situations. This article aims to help administrators to understand why this occurs and help grant users access to library documents or indeed any other global content.
Understanding global events, duty and security
The library uses a global event to store its data.
Global events allow permanent data to exist irrespective of specific events (such as fires or floods). They are permanently available and therefore do not allow users to go on duty for them, however duty is part of the underlying security model for Crisisworks and users must be on duty for an event to access its data. ,
Crisisworks gets around this by automatically managing a user's access to global event data whenever they go on or off duty to non-global events.
The main reason users typically cannot see library data is when the global event does not contain any positions that the user are competent in.
Changes to the positions for global events may require the user to logout and login again before they can see the global event.
Troubleshooting checklist
Please check these possible areas (you will need to have Crisisworks Administration permissions):
| Check | Notes | |
|---|---|---|
| 1 | Does the global event have at least one position to which the user is competent? | Make sure the correct positions have been added to the event. You can edit the positions for the event, after finding the event via "Manage Events" in the event menu. |
| 2 | Has the user ever gone on duty? | A user must go on duty at least once in order to have the system configure access correctly. A user cannot go on duty directly to a global event, so you will need a live event for the user to go on duty. We recommend that you have a test or play area that is always open so users can join after they log in, once on duty in any event the library menu appears. Alternatively you may create a 'Standby' event or similar to allow users to be able to go on duty for the first time. Administrators can also manage another user's duties by selecting the user and clicking Manage Duties from the user profile. |
| 3 | Does the user/position created actually have access to the reference library? | Step one: View the effective permissions for the user Goto the user's record and select the View Effective Permissions, to view if the user has access to the reference library. If the user does not have access then edit the user profile and give the user access to a position that has access, then click save. Step two: View the effective permissions for the user's position(s) If after following step one the user still does not have access, check the user's position. From the user's profile, click to the user's position(s) and select the View Effective Permissions, to view if users on duty to that position have access to the reference library. If the position does not have access, edit the position and add "Reference officer" or "Reference access".
|