Governed access to RPA bots

A method comprising:

• receiving, for a robotic process automation (RPA) bot, an onboarding request for creating an RPA bot ID;
• creating the RPA bot ID, in response to validation of the onboarding request for approvals;
• associating a directory service account with the RPA bot ID, the directory service account being a privileged account available for bot employee type, wherein the associating the directory service account comprises creating the directory service account for the RPA bot ID in a predefined subdivisional organizational unit dedicatedly created for the bot employee type, the directory service account in the subdivisional organizational unit being tagged as the privileged account;
• linking a target account with the RPA bot ID to provision authorized privileged access of the target account to the RPA bot;
• providing an application programming interface (API) for the RPA bot for reconciling the access to the target account;
• and
• granting authorized privileged access to the RPA bot to the target account, based on the associating, the linking, and the reconciling, wherein the granting authorized privileged access comprises performing an audit to review access policies associated with the RPA bot to determine whether to grant access to the RPA bot.

A non-transitory computer readable medium including machine readable instructions that are executable by a processor to:

• receive, for a robotic process automation (RPA) bot, an onboarding request for creating an RPA bot ID;
• create the RPA bot ID, in response to validation of the onboarding request for approvals;
• associate a directory service account with the RPA bot ID, the directory service account being a privileged account available for bot employee type, wherein the processor is to create the directory service account for the RPA bot ID in a predefined subdivisional organizational unit dedicatedly created for the bot employee type, the directory service account in the subdivisional organizational unit being tagged as the privileged account;
• link a target account with the RPA bot ID to provision authorized privileged access of the target account to the RPA bot;
• provide an application programming interface (API) for the RPA bot for reconciling the access to the target account;
• and
• grant authorized privileged access to the RPA bot to the target account, based on the associating, the linking, and the reconciling, wherein the processor is to perform an audit to review access policies associated with the RPA bot to determine whether to grant authorized privileged access to the RPA bot.