Packages RBAC for bot developer

As a Bot Creator (RPA developer) or Citizen Developer, you can create bots based on the packages that are available to you.

You can use only those package-defined actions, triggers, variables, and customized packages for which you have access. Your access to these packages are set by the administrator based on user roles. If you do not have access to a package, you cannot view that package on the Actions palette.

RBAC on packages applies when you create or edit bots in your private workspace. You cannot run bots with restricted packages directly. However, you can use a cloned bot as a sub bot in another main bot and run this bot in a public or private workspace.

When a bot contains packages (or packages that you cannot access), keep in mind these considerations:

You cannot perform these bot actions:
- Run a bot: Either a new bot or a checked-out bot with changes
- Check in a bot
If you try to perform these actions, an error message is displayed that the bot contains packages that are restricted.
While editing variables, you cannot use variable property options related to restricted packages.
An error message is displayed that the variable is related to a package that is restricted.
You cannot run a bot with triggers:
- From the Bot editor, when you run a bot with a trigger that contains a restricted package, see an error message is displayed that the bot with triggers contains a restricted package.
- When a trigger event is configured for a user and a device, and the trigger event occurs on the device, access to the bot package is verified. If the bot contains a restricted package, the bot fails, and an audit log entry is recorded.

Automation 360