Roles

Roles allow admin users to create and manage new roles by assigning specific Metadata and Data permissions based on the License Type applied to each role.

View Roles

The Roles tab displays a comprehensive list of all the roles currently in OvalEdge. This tab is exclusively visible and accessible to the Users & Roles Admin role in OvalEdge (“oe.user&role.admin”). In addition to the Role Name, various additional details are presented, including:

• Role Name: Describes the name of the role.

• Role Description: Describes the purpose of the role.

• License Type: Specifies the allowed association with users of similar or lower license types.

• User Associated: Describes the number of users assigned to a particular role.

• Default Role: Designates a role with predefined Meta and Data permissions for validated and crawled connectors.

• Default Meta Permissions: Reveals Metadata permissions, typically set as Meta Read-Only by default.

• Default Data Permissions: Highlights Data permissions, usually set as Data No-Access by default.

• Default Admin: Indicates default administrative privileges.

• Default Permissions: Displays default Metadata and Data Permissions.

• Source: Shows the source through which the role was created in OvalEdge.

• Created Date: Presents the timestamp of role creation.

• Last Updated Date: Shows the timestamp of the role's last update in OvalEdge.

• Delete Role: Click on the Delete Icon to delete the specific role.

Add Roles

Creating a new role in OvalEdge is a task exclusively reserved for the Users & Roles Admin, and it can be accomplished through various methods:

• OvalEdge’s Roles Tab

• Advanced Tools > Load Metadata from Files

• Advanced Tools > OvalEdge APIs (Method: POST API: /api/security/role/add)

• Roles created and present in Active Directories (like Okta, Azure AD)

To create a role, certain mandatory fields need to be filled:

• Role Name: The role name must be unique, regardless of the user license type.

• Selecting a Role’s User License Type: This defines the role/roles that can be associated with a user. For instance, if the user is a Viewer, only the Viewer license type role can be tagged, and if the user is an Author, roles of both Author and Viewer license types can be tagged based on organizational needs.

• Selecting Users: This defines the user associated with a role.

• Description of a Role: A brief description outlining the role's purpose or function.

Edit Roles

Existing roles in OvalEdge offer flexibility for sorting, filtering, and searching based on various criteria. Roles can be sorted using Role Names, Created Date, and Last Updated Date. Searching can be done using Role Name and Role Description. Additionally, specific fields like the Role’s User License Type and the Source through which the role was created can be used for filtering.

Inline editing allows modification of the role’s Name, Description, User License Type, Metadata, and Data Permissions. The Roles Tab also facilitates additional operations, enhancing the role management process.

Save Default

If an organization wants specific roles, with defined metadata and data permissions, to have consistent permissions across all objects from various data sources cataloged in OvalEdge, they can achieve this by enabling the "Default role" checkbox for a role and clicking save. This action ensures that the specified role automatically receives the pre-defined permissions on objects during the crawling and cataloging process. This approach minimizes the necessity of separately defining permissions for each object, providing a more streamlined and efficient permission management system.

Declare a Role as Default Admin

If an organization wants specific roles to function as administrators for all data objects cataloged in OvalEdge across various data sources, they can achieve this by selecting the "Default Admin" and "Default role" checkboxes. Upon clicking save, the chosen roles will be designated administrators for all future data objects crawled by default. This configuration streamlines administrative control over data objects, ensuring that the specified roles automatically possess administrative privileges without requiring manual adjustments.

Apply Default Roles

If an organization wants changes made to a role's metadata or data permissions to be reflected across all crawled data objects, they can select the specific role and click "Apply Default Roles." This action initiates a job that consistently applies the modified role settings across all data objects crawled, ensuring uniformity in metadata and data permissions throughout the system.

Delete Single Role/Delete Roles in Bulk

Actions such as deleting roles in the Roles Tab can be performed in-line or through the 9 dots menu. The OE_ADMIN role is set as the default admin, and deletion of this role is not permitted.

Deletion can also be carried out through Load Metadata from Files or by utilizing Roles Templates (with or without data templates), specifying the Input Action as "Delete." OvalEdge APIs provide another method for role deletion using the endpoint (/api/security/roles/delete, Method: POST).