Skip to main content

 

Managing the Applications Lifecycle

 

OutSystems

Control Who Creates Applications

OutSystems permission model allows you to limit the creation of new applications in an environment to some users, such as IT architects.

In this example we want to:

  • Allow junior developers to see and work only on the applications of their respective teams but without being able to create new applications.

  • Allow architects to create applications for their teams.

To do this, configure the junior developers:

  1. Create a new role that has the permission level Access to Environment.

  2. Create IT users for all junior developers with this new role set as the default role. This defines base permissions that only allow all junior developers to log in to an environment without granting access to any application.

  3. Create another role called Junior Developer that has the permission level Change and Deploy and set the permission Create Applications to OFF.

  4. Add the junior developers to their respective teams with the role Junior Developer. This allows junior developers to make changes to the existing applications in their teams but does not allow them to create new applications.

Then, configure the architects:

  1. Create a new role called Architect that has the permission level Change and Deploy Applications and set the permission Create Applications to ON.

  2. Add the architects to their respective teams with the role Architect.

This allows architects to create new applications directly in their teams through LifeTime. The new applications will be automatically added to the corresponding team. Therefore, the junior developers that have the permission level Change and Deploy Applications for the team can use Service Studio to create modules in the new application.

  • Was this article helpful?