Avoiding manual access

I have created an automation that accesses a program as an attended robot via a technical user, triggered by a human via UiPath Assistant. Apart from the running automation, the human shall not have access to the program. I wonder how to ensure that…

If the human Assistant user pauses the running automation, he would have manual access to the system in which the robot is running. Is there a possibility to deny the assistant the opportunity to pause a running automation? Furthermore stopping a runnin automation would also need to close the program in order to avoid manual access.

Does anyone have an idea, how to deal with this situation?

We do not use an orchestrator.


Hello @slink!

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

Hi @slink,
Is user able to log in via this technical user credentials? If yes then I think Orchestrator is the solution here as tasks can be triggered from there eventually based on some user’s action but then robot could use dedicated account which no user have access to.