Security

Overview

The security of the application is managed by permissions. Permissions are used to define the actions that the user group can perform in the application. Permissions are used to control the visibility of components, the behavior of components, and the behavior of the application. Permissions are defined in the app modules. Each component, action, and route can have a permission. If the user does not have the required permission, the component, action, or route will not be rendered or executed.

Permissions are assigned to roles. Roles are assigned to user groups. To receive a permission, the user must be a member of a user group that has a role with the permission.

(Add a diagram to show the relationship between permissions, roles, and user groups)

Permissions

Permissions are defined in the app modules. Each component, action, and route can have a permission. If the user does not have the required permission, the component, action, or route will not be rendered or executed.

Example:

permissions:
  - name: "System/Countries/Read"
    description: "Read countries"
    roles: # Assign roles to the permission
      - "Administrator"
      - "Operator"

Organization Contacts

Organization contacts are used to link application users to employees or other entities in the organization. Organization contacts are used to define the relationship between the user and the organization. For example, the user can be an employee, a customer, or a supplier.