Owl supports RBAC configuration with both core roles and custom roles. Core roles include the following:
ROLE_PUBLIC: Access to see dataset scores but no dataset interaction when dataset security is enabled.
ROLE_OWL_CHECK: Users or AD Groups mapped to this role will have the ability to run an owl check when Owl Check Security is enabled.
ROLE_DATASET_MANAGER: Manage Dataset to Role Mappings
ROLE_OWL_ROLE_MANAGER: Manage Roles and User Mappings to Roles & Datasets
ROLE_USER_MANAGER: Manage Users and User Mappings to Roles & Datasets
ROLE_CONNECTION_MANAGER: Manage Connection to Role Mappings
ROLE_ADMIN: Access to the administration pages (Create connections, roles, users, AD, etc.)
Custom roles can be added via the Role Management page by navigating to the Admin Console and clicking on the Roles Icon. Custom roles can also be added 'on the fly' during the Active Directory Role Mapping step.
It is these custom roles that will determine the users that have access to datasets (including profile/rules/data preview/scoring), and database connections
Additional information regarding setting up Dataset and Connection security can be found in those documents respectively.