Robot User retains access after being removed from authenticating AD Account

Using Orchestrator and robot version 19.10 that is linked with Active Directory. We are using active directory groups to grant access to the proper modern folders for process deployment to robots. When a robot user is removed from an active directory group their robot retains access to everything that was granted via the AD group even though the user is no longer in the AD group. Will this issue resolve itself over time with periodic AD polling?

This seems to resolve itself given a little time. The license and/or process availability based on AD permissions don’t always update immediately but do seem to update within a few minutes.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.