Dear Community
I'm happy to inform you that the solution as previously shared, and including also 15 and 30 minutes, will be included in the Alma May 2025 Release.
Thanks,
Uri Beladev
Platform Product Management team

Dear Mr Beladev,
many thanks for looking into this. 150 minutes would be a great improvement - but I wonder if one should not offer another, longer, option, e.g. 480 minutes.
Use case: a colleague is working on a tricky cataloguing problem at her desk. Then, she is learns that the colleague who had a 3-hours-shift at the issue desk has suddenly fallen ill and has to cover immediately, since there is already a queue. After the shift, and probably a lunch break, she wants to return to the problem.

Sometimes a session expires much faster than in 60 minutes which would be even quite long ... So the suggestions of ExLibris seem to be very promising. Let us see if the promise can be kept ...

I would suggest going as far as 8 hours. Ideally, I would like to be able to select the timeout setting per user. Frontline student assistant staff may need shorter timeouts (15 to 30 minutes) whereas technical service staff would benefit from an extended timeout (8 hours). It would be OK if the timeout configurations were associated per role (manager has longer timeout than student assistant staff).

Definitely would like this useful, configurable capability.

We too very much need local configuration for timeout.

+1

Yes, please allow timeout to be configurable.

Itai, can you explain the security issue?

We should have the option to disable timeouts completely. I am in and out of Alma all the time and often need to work on queries across a period of days. I suspect I'm not the only user who doesn't log out of their Windows session during the work week.

Manu Schwendener, There are not two settings. Unchangeable aspects of the software are not "settings." We want Alma to stay open longer.

Text from the first of the two links at the idea you linked to on 5 March at 3:08: "Answer
Session timeout is set to 60 minutes, at which time the session will expire and staff are required to sign in again. This is not configurable."

There are 2 settings, see https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/42834474-alma-automatically-logs-off-too-frequently-for-our

Duplicate with https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/42837597-extend-alma-timeout

Allow us (me) to configure how long Alma may be idle before timing out. The current setting is far too short. Sometimes I will be in the middle of working and have to step away to assist a team member and when I return to my desk, I've lost my search/progress or just plain have to start over.

Allow us (me) to configure how long Alma may be idle before timing out. The current setting is far too short. Sometimes I will be in the middle of working and have to step away to assist a team member and when I return to my desk, I've lost my search/progress or just plain have to start over.

I am agreed.

Absolutely! I also vote for this!

+1

Definitely in favor of the enhancement to make timeout configurable! There are many situations within a library where interruptions happen and starting over from scratch after having made significant progress on a task is a waste of time.

I too vote for this enhancement. I'm new to Alma and this is absolutely a necessity.