that thing

we do

frends has more features than any other integration software out there. Explore, ideate, and if anything is unclear - hit us up at any time. This library is bound to grow over time.

Role Based User Interface

frends has a fine grained user access management system, which is based on user defined Roles within the FRENDS platform. The roles are then mapped to the identity management system of your choice such as Azure AD.

The frends User Interface is built to support the role based user access management system from the ground up. This means that every action behind a button and every piece of data in every view is configurable to either allow or block access for a specific role.

For example a role configured for a developer:

frends User Management and Roles

User Roles

The User Roles that are defined in frends serve to usually limit the priviliges of an authenticated user for security purposes, but also to support and enforce a DevOps model with dedicated roles for Tester for example.

A customer could for example configure Roles for the following user types:

Role Explanation
Developer The developer can be configured to only be allowed access to the development enviornment and with priviliges to deploy solutions only to the Test enviornment.
Tester The tester can be configured to only be allowed to run unit tests and manually run integrations only in the Test enviornment. Additionally the Tester can be allowed to Tag an integration process as "Approved" once tests are finished.
Administrator The architect can be configured to have full access to all environments, meaning that only the Architect can deploy solutions to Production.
Business Owner The business owner can be configured to only have read access to all production data, but he isn't able to modify or edit anything.

These user roles can be fully customized to suit your development processes and types of stakeholders.

Sometimes the roles are even used within an organization to logically separate for example API development from Automation development between two teams.

Role Based User Interface

frends has a fine grained user access management system, which is based on user defined Roles within the FRENDS platform. The roles are then mapped to the identity management system of your choice such as Azure AD.

The frends User Interface is built to support the role based user access management system from the ground up. This means that every action behind a button and every piece of data in every view is configurable to either allow or block access for a specific role.

For example a role configured for a developer:

frends User Management and Roles

User Roles

The User Roles that are defined in frends serve to usually limit the priviliges of an authenticated user for security purposes, but also to support and enforce a DevOps model with dedicated roles for Tester for example.

A customer could for example configure Roles for the following user types:

Role Explanation
Developer The developer can be configured to only be allowed access to the development enviornment and with priviliges to deploy solutions only to the Test enviornment.
Tester The tester can be configured to only be allowed to run unit tests and manually run integrations only in the Test enviornment. Additionally the Tester can be allowed to Tag an integration process as "Approved" once tests are finished.
Administrator The architect can be configured to have full access to all environments, meaning that only the Architect can deploy solutions to Production.
Business Owner The business owner can be configured to only have read access to all production data, but he isn't able to modify or edit anything.

These user roles can be fully customized to suit your development processes and types of stakeholders.

Sometimes the roles are even used within an organization to logically separate for example API development from Automation development between two teams.