Blog
Jan 03

Improving Developer Collaboration with Role-based Access Control

Today, enterprises rely on a global team of developers with varied roles & skills to develop applications. When many developers collaborate on large projects, clear access control policies are required for effective collaboration. But traditional development tools have failed to address the need for developer roles and access control. As organizations feel the pressure to create applications faster and more frequently, the lack of governance can result in coding defects, deployment issues, and delayed projects.

WaveMaker provides comprehensive role-based access control (RBAC) features for enterprise application development teams. The RBAC features center on the principle of minimal privilege i.e. to provide the least level of access to perform tasks to the full extent.

Permissions

Permissions manage access control for the various roles in the development process. WaveMaker provides a predefined list of permissions at three levels – platform, project and resources. Refer to the developer RBAC documentation for more on permissions and access control.

Roles

Roles represent a set of permissions that can be assigned to a user. WaveMaker offers different roles for platform and project administration.

Platform administration through product roles
Product roles are for platform administration and are generally assigned to IT users. Product roles offer three predefined access control levels – Super Admin, Enterprise Admin, and Studio User.  You cannot create new product roles. In this way, the platform demarcates itself into compartments accessible only to the authorized users.

Define custom roles for projects
Project roles are for developers and project leaders involved in application development. These roles combine flexibility and control by offering predefined and custom roles. Besides the predefined roles of Project Admin and Default, admins can create new project roles. Most enterprises have several projects with shared project resources. So, the same user can assume different roles in different projects.

Configure and assign roles

Admins can assign product roles to users in the on-boarding section of Launchpad, the administrator portal. They can also create custom project roles such as UI Developer or DevOps by configuring appropriate permissions.

Project administrators can then invite users to projects and assign one of the configured project roles. Roles can also be updated via a project’s User Management settings.

With WaveMaker role-based access control, developers can collaborate better and create applications faster without the risk of project governance issues. Refer to the project user management documentation for more details.

Introducing WaveMaker 10
Role-based access control at platform and project level is a new feature in WaveMaker 10. Learn more

Leave a reply

Your email address will not be published. Required fields are marked *

We use cookies to provide you with a better experience. By using our website you agree to the use of cookies as described in our Privacy Policy.