Introduction and “how-to” guide to the Ferris Security and Access Rights Management.


Ferris takes a multi-layered and integrative approach to security and access rights management, protecting systems, networks, users and data alike.

While the security architecture of Ferris stands alone and operates well in isolation, it is built to integrate with enterprise security systems based on LDAP and Active Directory.

It supports Single Sign On (SSO) through open protocols such as Auth0 and SAML.

This user guide focuses on the application internal - user controlled - aspects of the seurity functions.


Ferris applies the established notion of Users, Roles and Permissions and linking them to the application elements such as Menues, Views and Pages.

This approach enables the breaking of the application into granular elements and organizing them into groups of like access control areas. The ultimate benefit is the implementation of user rights on a strict “need-to-know” basis.

Security Components

The following sections describe how the security components work and how to set them up for your purpose.

If you want to follow the instructions and examples, you first need to connect to your Ferris demo instance.

The Security menu is found on left hand navigation of Ferris. Click on the Security menu to expand it and display all security relevant menu items.

Ferris Security Navigation

  • List Users: Setup individual users and assign one or more roles to them. If Ferris is integrated with a company own Single Sign On, here is where all users can be viewed. Each user may be deactivated manually.
  • List Roles: Setup and maintain individual roles and assign them viewing, editing, executing and other rights pertinent to the character and scope of the role. Roles can be integrated and inheritet with the company Active Directory.

For Security Administrators only These menu items can only be seen and accessed with the prerequisite Administrator rights as granted in the User section.

NOTE that it is considered a good practice that security related tasks are provided to only a few dedicated Security Leads within the organization. For that purpose, setting up a dedicated Security Lead role is advised.*


Understanding the meaning, role and setup of Users within Ferris.


Introduction of the Roles concept, including the meaning and application of permissions.


Introduction to the Ferris concept of Permissions.


Statistics lists the number of successful as well as failed login counts by user.

Last modified November 24, 2023: update (f4bc5ea)