The Need to Extend the Webcon Designer Studio Privilege Model

0

The privilege-granting capabilities for application creation (within Webcon Designer Studio) should be more extensive and flexible.

Let's assume two business units (departments) are using the same Webcon instance. How can proper privileges be granted within Webcon Designer Studio in this scenario? The current model of access rights appears too binary: you can either be a System Administrator with complete access to all resources, or an Application Administrator with control strictly limited to a single application.

In the first scenario, the System Administrator has visibility into all data sources utilized by the other department, which implies access to all their data.

In the second scenario, the Application Administrator is given a "lite" version of Webcon Designer Studio. They cannot even create a new data source, which is the recommended approach by Webcon when utilizing external databases. Or create a new application.

It seems that Webcon developers assumed that the platform would be governed centrally – by a central unit that creates new applications, grants application privileges, configures data sources, assigns licenses, and controls the API.

However, low-code platforms could be leveraged more efficiently. Business departments should be able to develop applications independently, but this requires them to have an appropriately broad level of access rights.

Therefore, it would be highly beneficial to introduce an additional, intermediate layer of privileges.

Perhaps the solution could be a privilege level equivalent to System Administrator scoped to a given database? This way, each business department would have its own dedicated database, and the central System Administrator would only oversee the overall database infrastructure.