IQ Bot user personas and roles

Learn about the users that contribute to IQ Bot and the associated roles and licenses. IQ Bot users and roles are defined in the Control Room.

IQ Bot user personas

A persona refers to the type of tasks that a user performs and the product areas with which a user interacts. To learn more about how each user contributes to IQ Bot, see IQ Bot process overview.

User type Description Roles, permissions, and licenses Access to product areas Related links
Bot builder Builds RPA bots to support IQ Bot functions such as training the Classifier and pre-processing documents Bot developer role + Bot creator license Automation 360 Build RPA bots for IQ Bot
Data engineer Creates learning instances, trains bots, and sends bots to production IQ Bot Admin or IQ Bot services roles Following tabs in Automation 360 IQ Bot
  • Dashboard
  • Learning Instances
  • Bots
  • Domains
  • Administration (IQ Bot Admin only)
Using Automation 360 IQ Bot On-Premises

Using Automation 360 IQ Bot Cloud

Admin Uploads custom domains and migrates learning instances between IQ Bot environments IQ Bot Admin role or a custom role with the migration utility permission Following tabs in Automation 360 IQ Bot
  • Dashboard
  • Learning Instances
  • Bots
  • Domains
  • Administration
Custom domains in IQ Bot

Migrate learning instances

Pseudo-user Runs the RPA bots to upload, pre-process, classify, and extract data from documents in IQ Bot Unattended Bot Runner license + view learning instance permission Automation 360 and IQ Bot
Validator Manually corrects fields in documents that IQ Bot could not process Validator role Only the learning instances to which permission is granted Use the IQ Bot Validator

IQ Bot roles

A role determines the areas in IQ Bot to which you have access. Roles are assigned in the Control Room and are of two types, predefined system roles and custom roles. If your user type is Admin, you can create custom roles.
  • System roles: These roles are built in and have a predefined set of permissions that cannot be customized.
  • Custom roles: These roles can be customized and modified to grant granular permissions to an IQ Bot user. An admin can configure the scope of a role with organization-wide permissions to manage all organizational resources or more narrowly to be limited to department-level resources. For more information, see Defining a custom role for IQ Bot.
The following table describes the permissions and access areas applicable to each system role:
System role IQ Bot permissions Access to tabs
AAE_IQ Bot Admin Access to all IQ Bot features and can migrate learning instances between environments
  • Dashboard
  • Learning Instances
  • Bots
  • Domains
  • Administration Migration utility
AAE_IQ Bot Services All permissions related to learning instances
  • Dashboard
  • Learning instances
  • Bots
AAE_IQ Bot Validator Can launch the Validator for granted learning instances Learning instances