Skip to main content

We’ve created a new very limited role for some of our BOT customers as a means for allowing them to see what is running as the BOT userID that runs their particular automation. 

Their role permissions are very limited and we’ve included a test user (person on our team that doesn’t use AA and had no access) however this user is not able to see activity that they should be able to see and we’ve confirmed this several times meaning I can see a BOT while Active in the In Progress area but this test user cannot. 

Hoping someone has seen this issue and found a resolution or has any ideas of what I might need to look at? 

Thanks! 

If a user doesn’t have access to viewing everyone’s active bots, they can only see their own. This means if you have a bot runner using their ID, they cannot log in at the same time and see that process, because you’re now logged in twice as the same user. There is no way to give someone access to viewing someone else’s activity without giving them access to everyone’s activity.

https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/control-room/control-room-api/cloud-dashboard-permissions.html

So, IF I understand correctly there’s no way to limit or restrict someone’s “view” to only a particular BOT userID meaning because this customers automation runs in our production environment as BotUser02 for instance but we also have 01 and 03 I can’t limit the users in this new role to only see what is running currently (if anything) as the 02 account? It’s either they see everything or they see nothing aside from “their own” which in this case would never exist. 

That's correct. We have no facility for user A to only see user B's bots in the activity view. 

 

While I understand that I guess we assumed that IF we provided The View Content permission(s) only within the BOT’s section of Edit Role and limited that to just the BOT’s that are being run by the afore mentioned user so why even provide those settings IF they’re not going to limit or provide access per the setting? 



 

​@eeyore2016 That only limits the ability for that user to see/run/check in/etc. those files in Public. It does not affect what appears in the activity view.

If user A does not have access to the /bots/user B folder, then user B runs their bot on a bot runner, user A will still see the run in the activity view (if one of their roles contains “View everyone’s activity” permissions) but will not be able to view the folder the automation is contained in nor any bots in that folder.

Copy that….I took those settings for a different (and incorrect) purpose. 

The goal here is to allow customers of a particular piece of automation to be able to identify or help identify IF their particular BOT is just waiting it’s turn in line meaning there’s another process being ran by this particular BOT user in production OR if there’s truly an issue that they should contact us about for deeper review. 

Are you (or anyone) aware of any way to accomplish this goal? 

Reply


Terms & ConditionsCookie settings