Station indivdual timeout options

Product Suggestions
,
1

Hey Tulip Team,

in our production site we have different use cases like tablets which are used by multiple user accounts (which needs a automatic Timeout set) and we have devices where a machine user should be logged in all the times.
Enabling setting station timeout options individual for certain stations would be a great feature to have!

Best regards,
Marek

Different Auto-Logout Behavior in DEV vs. PROD Instances
2

Agreed, perhaps a general timeout option with exception configuration for “special” stations.

3

I’ve also come across a scenario wherein it would be valuable to bypass the automatic timeout/logout depending on the app being run, regardless of station.

This might also need to be restricted based on the user (e.g. only supervisor or superuser), but that could be managed with user permissions for the relevant app.

1 Like
4

Has there been any progress on this? Setting timeouts by station (or station groups) would be incredibly useful for us when deploying things like dedicated dashboard stations/apps. The timeout makes these scenarios functionally impossible at the moment.

5

Does using the web interface shared dashboards mitigate this at all?

6

Hi @Dan,

There are no current plans to have timeouts by station or station group at this point in time. We will look to pick up this work in the coming months if we have bandwidth.

Thanks,

Jake

1 Like
7

Hi Jake,

This is quite disappointing, to put it mildly. Without this (or a substantially similar functionality), none of your GxP customers that require automatic user timeout for compliance are able to build functional dashboard apps. The browser based dashboard functionality is extremely limited, and is not an adequate substitute for dashboard apps in Tulip’s current state.

The only potential way around the limitation, as far as I can see, is to use a mouse jiggler or similar - which is going to violate most corporate infosec policies.

What is the relative prioritization of this issue at this point, from Tulip’s perspective?

8

Tagging @jakerigos for visibility.

9

Still a big need on our side too — shared tablets vs. dedicated stations require very different timeout behaviors. A single global setting creates real issues. Configurable timeouts by station/station group would make deployments much smoother. Any update if this is on the roadmap?

2 Likes
10

Hi @Dan,

Understood, this is helpful for us to understand. We can look to add it to the roadmap but there are a few key considerations here:

  • Is it acceptable to only have this on the station group level? My main concern is that station by station configuration becomes incredibly difficult to maintain/set up.
  • Is the core target by app? Device type? Station group? Understanding the intent would allow us to focus and scope this down.

Sincerely,
Jake

11

@jakerigos

Station Group level would work best for our purposes, as timeout exceptions are generally going to apply to classes of station (e.g. stations that are used exclusively for Dashboards). If we ever had a one-off scenario, it would be acceptable to set up a dedicated station group to cover it.

I agree - station by station is a little too granular to manage at scale, and would be prone to error.

2 Likes