Defining a custom role for IQ Bot

For various roles within IQ Bot, you can use role-based access control (RBAC) to enable or restrict user access to learning instances, related features, and functionality by defining granular permissions. You can also use RBAC to define custom roles in IQ Bot.

IQ Bot supports two types of role definitions:
  • System roles in Control Room: These roles are built-in and have a pre-defined set of permissions that cannot be customized. To learn more, see IQ Bot roles.
  • Custom roles in Control Room: These roles can be customized and modified to grant granular permissions to an IQ Bot user. If you are an admin, by creating a custom role, you can grant users access to specific learning instances.

If you are a user with the View and Manage Roles permission, you can use the Control Room to create and assign custom roles.

Permission Description
View my learning instances Allows a user to access their own learning instances.
View learning instances from the same role Allows a user to view only learning instances created by the same role.
Note: If multiple users are assigned the same role, then all these users will have access to the same learning instances.
View all learning instances Allows users to view all learning instances created by any user across all roles.
Edit learning instance Allows users to edit learning instances.
Delete learning instance Allows users to delete learning instances.
Send learning instance to production Allows users to move learning instances from staging to production.
Import domain Allows users to import domains into IQ Bot.
Things to remember:
  • Ensure that users with View learning instance from the same role do not have non-IQ Bot roles. Example: When you create a learning instance, all the roles that you have under your name gets assigned to the learning instance. So, if you have AA_Basic role in combination with View learning instance from the same role, then all the users with AA_Basic role have access to IQ Bot. Therefore, users who create learning instances must not be assigned non-IQ Bot roles.
  • It is required that creators of learning instances for a specific department must be assigned a minimum of two roles:
    • A role that allows them to create learning instances
    • A department-specific role with the View learning instance from the same role permission
  • When new learning instances are migrated, existing roles will not be migrated. After the roles are assigned in the target system, they cannot be changed. IQ Bot Automation 360 does not support changing role assignments of learning instances.