This application was developed on OutSystems Developer Cloud (ODC) to centrally manage End-User Roles and Organization Roles for users associated with teams. The solution is inspired by the role management model available in OutSystems Lifetime (OS11), adapted to ODC governance and security concepts.

This module provides centralized governance for End-User Roles and Organization Roles. Teams act as role containers, ensuring consistent and automated role assignment based on team membership and lifecycle state.

The same logic that exists on the Lifetime from OS11.

Example scenario:

A team can aggregate multiple End-User Roles and Organization Roles. These roles are automatically granted or revoked based on user association and team status.

When a team is deactivated, all roles are removed from every associated user. If the team is reactivated, all roles are automatically reassigned.

Team List

This screen allows administrators to search existing teams, create new teams, or edit an existing team by selecting its name. The image below illustrates the Team List interface.

In this screen, you can search for the teams already created, create a new team, or edit the existing team (to do this, it is necessary to click on the team name, in this case, “Team Test).

Add Team

This screen represents the first step in team creation. Administrators must provide a team name. The team is automatically created with the IsActive flag set to True. After saving, additional configuration tabs become available.

This is the first step, where it is necessary to put the team’s name (we will create it with the flag, isActive = True, automatically).

After saving a new team, we will see the tabs (Users, End-User Roles, and Organization Roles).

Users Tab

This tab lists all users associated with the team. Administrators can assign new users or remove existing ones. If the team has no roles configured yet, users will only be associated with the team without receiving any permissions.

At this moment, this user is only associated with the team because the team doesn't have a role.

End-User Roles Tab

This tab allows administrators to assign End-User Roles per application. After selecting the application and role, the permissions are automatically granted to all users associated with the team.

After selecting the stage and clicking on the save button, we will add this Application/End-User Role for the users.

If we go to the ODC Portal, we can see this application associated with the users:

Organization Roles Tab

This tab allows administrators to assign Organization Roles per application. Once saved, all users associated with the team automatically receive the selected roles.

At this moment, all users associated with this team will receive this organization role. If we go to the ODC Portal, we can see this organization role associated.

Now, the users associated with this team can see the XPTO app, available on the ODC Studio, and can test the XPTO app on the browser.

Governance and Best Practices

All developer users must be created with the Organization Scope set to 'No role'. Role assignments should be managed exclusively through this application to ensure centralized governance, consistency, and auditability.