Persistent Orchestrator Login for Monitoring purposes

We are installing a few wall mounted displays in the office with the goal of showing the Orchestrator Monitoring views for operational support. (Being able to monitor alerts of running jobs without the need to keep the Orchestrator open on local workstations.)

The global setting for security purposes is that an active Orchestrator login session times out after a few minutes.
The monitoring profile, which will contain a read only role, will automatically inherit this timeout.
How can we easily bypass this session timeout for specific profiles? So to keep the wall-display logged in, while our local sessions still timeout for security purposes.

Using 3rd party scripts to keep the session active is less desirable, due to other security restrictions.

Any thoughts are welcome…


Hello @Jeroen_van_Loon!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

  5. Meet us and our users on our Community Slack and ask your question there.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly