Munis Program Session Timeout Not Working
Description of Issue
- Munis program timeout for active sessions is not working as needed
Context
- Munis
- System Configuration Settings
- Roles & Permissions
- Administration
Cause
- Need to define a timeout threshold for user roles
- Users time out too soon and need more time to complete work
- Users need to be forced out of Munis programs if idle for too long
- User role defined timeout conflicts with System Settings idle program warning message timing
Resolution
- Ensure users have the correct level of access
- Munis > System Administration > Security > User Attributes
- Search User Id
- Accept
- Effective Permissions and review System Administration module Permission "Timeout programs after an idle time of"
- This is the combination of all assigned roles granting this permission.
- The highest time out of all assigned roles will display as the defined time threshold
- A single role with "Disabled" will overwrite any defined time.
- Ensure System settings are defined to warn users in time to take action before timeout.
- Munis > System Administration > General Administration > System Settings
- Select the System Settings tab
- Update and define the Prior to timeout, show a timeout alert for:Â
- No Alert
- Select time to trigger idle warning with count down clock until timeout threshold reached
Additional Information
- Munis takes the User's assigned total of role permissions for timeout threshold and then applies the system setting warning on top of it.
- Example
- User has overall timeout threshold of 30 minutes
- System Settings warn at 5 minutes
- User opens a Munis program, at 25 minutes user receives warning of program timeout with countdown of 5 minutes.