The browser session timeout and automatic data refreshing in views are configured separately. The session setting determines how long a user can be inactive before being logged out. The refresh setting retrieves up-to-date data for selected views.
You need administrator permissions to change these settings. Open Settings from the browser navigation, select the tab with the same name and open the Session and page refresh settings section. In its table, the Session length and Page refreshing links open their respective settings windows. The settings apply across the service.
Session timeout
The timeout is based on inactivity, not the total time elapsed since login. The default in the production service is 30 minutes if no separate time limit has been saved.
- Open the Session length link.
- Select a time limit: Default (30min), Short (10min), Long (1h) or Never log out.
- Select Save at the bottom of the window.
- Reopen the setting and check the saved selection.
Never log out saves a time limit of approximately one year. It does not remove the timeout entirely.
In the current implementation, the Users field does not limit who the timeout applies to. Whether you select users in the field or leave it empty, the browser timeout uses the shared time limit. Do not use this field to define exceptions for individual users.
Once the session expires, the user must log in again to continue. Save unfinished changes in good time: the timeout does not save the form. Login instructions are provided in the article Logging in and resetting your password.
Enabling automatic refreshing
Automatic refreshing is initially disabled on all supported pages. Enabling it and choosing a refresh interval are done separately for each page. Entering a number of seconds alone does not enable refreshing.
- Open the Page refreshing link.
- Select the checkboxes in the Page column for the pages where you want automatic refreshing.
- Enter an interval for each page in the Refresh frequency (30-120) Seconds column. The allowed interval is 30–120 seconds. For example, 60 means refreshing approximately once a minute, unless refreshing is paused.
- Select Save and reopen the setting to check the checkboxes and intervals.
- Reopen the view to be refreshed so that it reads the saved settings.
The form requires a valid number of seconds for the Dashboard, Tasks page and Service requests page rows even when refreshing is disabled for them. Fill in these fields if empty values prevent saving. For the Work management and Report pages rows, an interval is required only when the checkbox is selected. The intervals for these two pages are not retained in the setting if you clear the checkboxes and save; set the intervals again the next time you enable refreshing.
Clear a page's checkbox and save when you want to stop automatic refreshing for that page. The setting is read when the view is opened, so a view that is already open will not apply the change immediately.
What does refreshing update?
- Dashboard: the task and service request lists, if they are included in the view. Other parts of the Dashboard are not included in this refresh.
- Tasks page: the initialized Kanban board. The setting does not refresh the page's table or map view.
- Service requests page: the initialized Kanban board. The setting does not refresh the page's table or map view.
- Work management: the data in the service request and task lists, calendar and Gantt view, using the current filters and limits. Tasks are retrieved for the time range already loaded. Refreshing does not itself extend the time range or remove filters. Filters and limits are explained in the article Work management views and filters.
- Report pages: the chart data on the visible report page. A report whose filter panel is open is skipped during that refresh cycle.
An open editing window or other separate action window pauses the refresh countdown. Dragging in Work management also pauses it. The countdown resumes from the remaining time after the window is closed or dragging ends. An open report filter panel prevents that chart from refreshing, but does not prevent other charts from refreshing.
Data refreshing retrieves up-to-date data for the view. It does not replace the form's own save button. Save your changes before leaving the view.
Check that refreshing works
Open a supported view for which refreshing has been enabled. The circular refresh countdown shows the remaining seconds: on the Dashboard, it appears in the task and service request list headers; on other supported pages, it appears in the toolbar at the top.
Close any action windows and the report filter panel, and finish any dragging. Wait for one countdown cycle and check that a known, saved change appears in the view. The countdown being visible alone does not show that all parts of the page are refreshing: check the result in a list or chart listed above.
If the data looks outdated, check whether refreshing is enabled for the page, the refresh interval and the view's filters and limits. Reopen the view after changing the settings. If a user is logged out earlier than expected, check the shared Session length setting; the Users field does not give them a separate time limit.
Mobile app locking is separate
PIN and biometric locking in the Android and iOS mobile apps are separate from the browser session timeout setting. These page refresh settings do not configure mobile data refreshing either. Instructions for enabling mobile locking are provided in the article PIN lock, biometrics and multi-factor authentication.