TDV's authorization settings are based on a design model centered on objects such as groups, users, and resources.
Please implement function-based authorization settings for roles such as manager, data catalog, workbench, data source creation, view creation, etc., taking into account the various roles of administrator, developer, and power user?
At the moment, if a user is granted "access tool" privileges, they have access to both Studio and WebUI, so we are unable to restrict access to the WebUI for end users.