Hi Nagesh,

I hope you're doing well.

To solve that issue you need to access your LifeTime and define IT Roles for each user. 

LifeTime is the centralized console for managing your OutSystems environments, applications, IT users, and security, covering the full application life cycle from development to deployment. 

Users created in Lifetime exist across all environments and each user has one role, can have application-specific permissions, and can belong to multiple teams.

Lifetime users are not end users!

A user can have application-specific, team and infrastructure-level permissions. Team permissions override infrastructure permissions. Applications-specific permissions override team and infrastructure permissions.

Please read the OutSystems documentation - Create and Assign Roles.

If you do that you can solve your issue.

Let me know if suits your needs.

Kind regards,

FC

Hello Nagesh,

Have you taken a look at Teams within Lifetime? You can use them to fine-tune developer permissions and restrict them to specific applications in an environment.

Note that if your developers have access to the environment database, they might also have access to the OutSystems metadata model, and this means they can bypass Service Studio/Center and fiddle with module versions directly in the database.