We’ve updated how Foodworks handles inactivity to improve security and consistency.
Previous behaviour
Previously, the inactivity timeout only applied if Foodworks was left open and unused in your browser. If you closed your browser or tab, you would remain logged in until your authentication token expired.
What’s changed
The inactivity timeout will now automatically log you out after your organisation’s selected inactivity period, even if you’ve closed your browser or tab.
For example, if your inactivity timeout is set to 3 hours, closing the browser will result in automatic logout after 3 hours with no activity on your computer.
Why this change?
Better account security — sessions won’t remain active unless you opt in for them to remain active.
Consistent behaviour — closing your browser now counts towards inactivity.
What you might notice
If you’re used to opening Foodworks and finding yourself already logged in, you may now be asked to log in more often.
This depends on your organisation’s inactivity timeout setting.
What you can do
If you find you’re being logged out too quickly, you can change your inactivity timeout in your Organisation settings to a duration that suits your workflow.
Comments
Article is closed for comments.