RBAC on bot schedules

Access is deny all and allow by exception based on roles and domains as defined in RBAC.

Review the following validation checks for scheduling a bot:
  • Ensure that the user who is scheduling a bot has the required permissions to perform the following actions:
    Note: For scheduled deployments, the validation checks are performed when creating the schedule and every time that schedule is triggered.
    • Can run the bot.
    • Is able to access the run-as users (Bot Runners) that can be added to the schedule.
    • Can access the available device pools.
  • Ensure that the bot input variables are within the allowed size limit.
  • If a request has high-priority, ensure that the user scheduling the bot has permission to run high-priority bots.
The RBAC on bot schedules permission is further divided into the following sub permissions:
Schedule my bots to run
Only those users that create new schedules.
Edit my scheduled activity
Only those users that edit their schedules.
Delete my scheduled activity
Only those users that delete their schedules.
View and manage ALL scheduled activity
Only those users that manage (edit or delete) all the existing schedules created by any user.

Administrators assign various permutation and combinations of these accesses to different sets of users and roles based on the business requirements.