Example

To better understand security please follow this example:

Actions are authorized to an specific group of people,

• • Sales representatives in Bangkok

  • Developing team of ‘n’ project

  • Project leaders

This is expressed through classifiers and categories, i.e.:

• • Area

    • • Sales

      • IT

      • Accounting

      • Production

  • Branch

    • • Bangkok

      • Asia

      • Americas

  • Country

    • • Thailand

      • Singapore

      • Japan

  • Position

    • • Team Leader

      • Developer

      • Manager

      • Representative

      • Top manager

  • Projects

    • • N1

      • N2

Actions then are assigned to specific groups, i.e.:

• • Sales representatives in Bangkok

    • • Area: Sales

      • Position: sales representative

      • Branch: Bangkok

      • Country: Thailand

  • Developing team of ‘n’ project

    • • Area: IT

      • Project: ‘n’

  • Project leaders

    • • Position: Project Leader

      • Country: all

      • Area: IT

  • Administrative assistants in Eiffel Region offices

    • • Area: Adminsitrative

      • Position: Assistant

      • Region: Eiffel

As the user doesn’t belong to a system roll, but instead is subscribed to his real-world groups, security combinations have no limitations.

If a classifier (area, country…) is not assigned is ignored, this means new ways of identifying groups can be added in the future without altering the security of previous objects.

Setting up security

All security information can be setup in database, or you can create your own administrative screens to set it up, or... you can use our security manager :) Just browse to task=sec_manager and enjoy it :)

Go to Sec_manager