Skip to main content

Control Room Administration - CUSTOM ROLE SUMMARY

 

The following summarizes custom roles that are based on Solution Patterns.  A role design like this can be used to define the specific role settings required to support different patterns.

If the Control Room folder structure is defined by business functions/areas, these roles could also be defined at a Business Unit/Function level as well - ex. CUSTOM_RUN_UNATTENDED_SCHEDULE_FINANCE for users managing scheduled automations in Finance, etc.

NOTE: The ‘CUSTOM’ prefix is simply to differentate these roles from the ‘standard/system’ roles available out-of-the-box as part of the Platform.

 

Roles for Automation Consumers

Sample Role Name

Description

Supported Patterns

CUSTOM_RUN_

UNATTENDED_ONDEMAND

Users who run unattended automations on-demand from Control Room.

CUSTOM_RUN_

UNATTENDED_SCHEDULE

Users who schedule unattended automations.

CUSTOM_RUN_

UNATTENDED_API

Users who run unattended automations on-demand via API.

CUSTOM_RUN_

ATTENDED_ONDEMAND

Users who run attended automations on-demand from Control Room.

  • Run Local On Demand

  • Run Local On Demand - CoPilot Desktop

  • Run Local On Demand - CoPilot Desktop - WLM

CUSTOM_RUN_

ATTENDED_TRIGGER

Users who run attended automations via event trigger.

  • Run Local via Event Trigger

CUSTOM_RUN_WLM

Users who run workload management automations on a WLM queue.

  • Run Remote via API - WLM

  • Run Remote On Demand - WLM

  • Run Remote via Schedule - WLM

  • Run Local via Event Trigger - WLM
Roles for Automation Runners

CUSTOM_

UNATTENDEDRUNNER_

WLM

 Run As Users with unattended bot runner licenses, that will consume work items from WLM queues.

  • Run Remote via API - WLM

  • Run Remote On Demand - WLM

  • Run Remote via Schedule - WLM

  • Run Local via Event Trigger - WLM

  • Run Local On Demand - WLM

  • Run Local On Demand - CoPilot Desktop - WLM

 

Go To Top

 

 

HUMAN ROLES

 

Consumers of Unattended Automation

 

CUSTOM_RUN_UNATTENDED_ONDEMAND: Run Automations on-demand from Control Room

 

 

Some users need access to login to the Control Room and run ‘unattended’ automations on a set of licenses (Run-As Users) and Devices.

As the role will also dictate WHICH Automations they can run (Control Room folders), larger organizations/programs will want to have more granular roles that limit the folders containing Automations they can access- ex.

RUN_UNATTENDED_ONDEMAND_BUSUNITA, RUN_UNATTENDED_ONDEMAND_BUSUNITB, RUN_UNATTENDED_ONDEMAND_BUSUNITC

 

 

Features

Run-As

Bots

  • (1) or more “Bot Runners” - aka Run-As Users with Unattended Runner licenses

  • Folders with specific automations

    • Folders with reusable Automations, called/dependencies of use case automations

 

 

 


CUSTOM_RUN_UNATTENDED_SCHEDULE: Run Automations by scheduling in the Control Room

 

 

 

Some users need access to login to the Control Room and schedule ‘unattended’ automations on a set of licenses (Run-As Users) and Devices.

As the role will also dictate WHICH Automations they can run (Control Room folders), larger organizations/programs will want to have more granular roles that limit the folders containing Automations they can access - ex.

RUN_UNATTENDED_SCHEDULE_BUSUNITA, RUN_UNATTENDED_SCHEDULE_BUSUNITB, RUN_UNATTENDED_SCHEDULE__BUSUNITC

 

Features

Run-As

Bots

 

 

 

  • (1) or more “Bot Runners” - aka Run-As Users with Unattended Runner licenses

  • Folders with specific automations

  • Folders with reusable Automations, called/dependencies of use case automations


 

 

 

CUSTOM_RUN_UNATTENDED_API: Run Automations by calling Control Room APIs

 

 

Features

Run-As

Bots

 

 

 

  • (1) or more “Bot Runners” - aka Run-As Users with Unattended Runner licenses

  • Folders with specific automations

 

Go To Top

 

Consumers of Attended Automation

CUSTOM_RUN_ATTENDED_ONDEMAND: Run attended Automations on-demand

 

 

Some users are assigned an ‘attended runner' license, and need access to login to the Control Room and run ‘attended’ automations on their own device (ex. laptop/PC).

As the role will also dictate WHICH Automations they can run (Control Room folders), larger organizations/programs will want to have more granular roles that limit the folders containing Automationsthey can access - ex.

RUN_ATTENDED_ONDEMAND_BUSUNITA, RUN_ATTENDED_ONDEMAND_BUSUNITB, RUN_ATTENDED_ONDEMAND_BUSUNITC

 

Features

Run-As

Bots

 

  • (1) or more business users with Attended Runner licenses

  • Folders with specific automations

  • Folders with reusable Automations, called/dependencies of use case automations

 

 

 

CUSTOM_RUN_ATTENDED_TRIGGER: Run Attended Automations via event trigger

 

 

 

Some users are assigned an ‘attended runner' license, and event triggers will initiate execution of the automation on on their own device (ex. laptop/PC).

As the role will also dictate WHICH Automations they can run (Control Room folders), larger organizations/programs will want to have more granular roles that limit the folders containing Automationsthey can access - ex.

RUN_ATTENDED_TRIGGER_BUSUNITA, RUN_ATTENDED_TRIGGER_BUSUNITB, RUN_ATTENDED_TRIGGER_BUSUNITC

 

 

Features

Run-As

Bots

 

  • (1) or more Attended “Bot Runners” - aka business users assigned Attended Runner licenses

  • Folders with specific automations

  • Folders with reusable Automations, called/dependencies of use case automations

 

 

 

Run Workload Management (WLM) Automation

CUSTOM_RUN_WLM: Run Automations that consume Work Items from Queues (WLM)

 

CONTENT COMING SOON!

 

Go To Top

 

AUTOMATION RUNNER ROLES

 

CUSTOM_UNATTENDEDRUNNER_WLM: Run As Users representing Bot Runners to execute Work Items from Queues (WLM)

 

CONTENT COMING SOON!

 

CUSTOM_UNATTENDEDRUNNER_TRIGGER: Run unattended Automations via event trigger

 

CONTENT COMING SOON!

Terms & ConditionsCookie settings