Maintenance of users with group assignment

Add user

Open the "Users" desktop:
Build.One Documentation > User, Groups and Rights Administration > image2021-11-18_9-47-59.png

To add a new user, launch the create dialog from the grid fab button:
Build.One Documentation > User, Groups and Rights Administration > image2021-11-18_9-49-30.png

Example of a new user:
Build.One Documentation > User, Groups and Rights Administration > image2021-11-18_9-55-33.png

Update user

To update a user, simply adjust the data directly in the desktop grid.
The grid is editable and changes can be committed using the "Save" button in the grid panel header.

Delete user

To delete an existing user, select the user in the grid and click the "Delete" button in the grid panel header.

User group maintenance

Create a new user group

The groups are maintained in the "Security" desktop, the "Security Groups" tab:
Build.One Documentation > User, Groups and Rights Administration > image2021-11-18_10-3-13.png

Clicking the add button in the left-side grid's fab button will launch the group create dialog:
Build.One Documentation > User, Groups and Rights Administration > image2021-11-18_10-5-5.png

The name of the group needs to be added to this dialog.
If the group should inherit the security settings of another group, the "Parent Group" should be used.

Deleting a user group

To delete a user group, select the desired group in the desktop and click on the "Delete" button in the grid panel header.

Managing users of a group

In the "Security Groups" tab there is a secondary grid on the lower-right, which display the users which are part of the currently selected group from the main grid.

To add users, launch the create dialog for the association from the grid's fab button.
Build.One Documentation > User, Groups and Rights Administration > image2021-11-18_10-16-13.png

To remove users from a group, simply delete them using the grid's panel header "Delete" button.

Assignment of rights

The security assignments can be maintained from the "Security" desktop's "Security Assignments" tab:
Build.One Documentation > User, Groups and Rights Administration > image2021-11-18_10-22-44.png

The security assignments themselves are split into multiple categories, named realms, which have different behaviour.
Each realm will also have different security "items", depending on the nature of the realm itself.
It's possible to select a user (will apply only to a user), a group (will apply to all users that are part of the group) or to leave the fields unassigned (will apply to everyone).
An assignment can either be restrictive or permissive.

Of note are the following realms:

SMF - Smart Menu Function
This maintains the access to any menu function/action within the application.
The items will be actual menu functions defined and used in menus.
SOM - Smart Object Master
This maintains the access to the application screens.
The items will be repository screens.
SOT - Smart Security Object Token
This maintains access to backend/server entities, such as business entities and tasks.
The items will be invokable methods of server entities.
These can be maintained from the "Security" desktop "Security Objects" tab.
SST - Smart Security Token
This maintains provides access information for custom tokens.
The items will be custom tokens defined in the "Security" desktop "Security Tokens" tab.
These tokens are meant to customize access to any custom logic both client and server-side.