User Settings

Administrator rights are required to edit this data. The user management allows administrators to have complete control over all user accounts. In addition to assigning roles, exceptions for the limits of the “User with Limits” role can also be defined here for a specific information class. See “Users with Limits”. In addition, the problem “Protection of external data and the request limit” can only be solved through the functionality offered here.

User Table

The user table shows all registered users with their most important properties. The table can be sorted by all columns and provides a clear overview of all relevant user information.

Properties and Table Columns

• ID: The unique internal user ID.
• Nickname: The nickname chosen by the user. This may be used for your identifier instead of the internal user ID to other users.
• Email: The user’s email address, which also serves as the login name. This cannot be changed after registration.
• U: A symbol that indicates whether there is a change proposal for this user. See section Change Proposals.
• L: A symbol that indicates whether there are limit change proposals for this user.
• Most Privileged Role: The highest role assigned to the user. Possible values are:
  • Administrator: Full administrator rights
  • Edit All: Can edit all entities
  • User: Standard user rights
  • User with Limits: Restricted rights with configurable limits
• Enabled: Indicates whether the user can log in. Disabled users can no longer log in.
• Language and Country: The user’s language setting. This determines the language of the application and the display of the date and number format.
• UTC Deviation in Minutes: The time zone deviation from UTC time in minutes. This is used to display time information correctly for the user.
• Violation of External Data/Data Limit: Counter for violations of the protection of external data. If this counter exceeds a configured threshold, the user is automatically blocked.
• Violation of Request Limit: Counter for exceeding the daily request limit. Here too, exceeding a threshold leads to automatic blocking of the user.

Expandable Row

For users with the “User with Limits” role, the configured editing limits can be viewed. Expanding the row displays a detailed view with all configured limits. These limits restrict the number of create, update, and delete operations for specific information objects.

The detailed view shows a table with the following columns:

• Information Object: The name of the object type for which the limit applies (e.g. security, watchlist, account).
• L: A symbol that indicates whether there is a change proposal for this limit.
• Day Limit: The maximum number of create, update, and delete operations per day for this information object.
• To Date: The expiration date of the limit. After this date, the limit will automatically no longer be applied.

Edit User

A user can be edited via the context menu. The following properties can be changed:

• Nickname: The user’s nickname. This must be at least 2 and at most 30 characters long and unique within Grafioschtrader.
• Most Privileged Role: The user’s highest role can be changed. The selection is made from the available roles (User with Limits, User, Edit All, Administrator).
• Enabled: A user can be activated or deactivated via this checkbox. Disabled users can no longer log in.
• UTC Deviation in Minutes: The time zone setting in minutes to UTC time can be manually adjusted if automatic detection does not work correctly. Allowed values are between -720 and +720 minutes.
• Violation of External Data/Data Limit: This counter can be reset to unlock a blocked user. The value can be between 0 and 99.
• Violation of Request Limit: This counter can also be reset to remove the lock. The value can be between 0 and 99.

Manage User Processing Limits

Individual processing limits can be defined for users with the “User with Limits” role. These limits restrict the number of daily create, update, and delete operations for specific information objects. This enables granular control over a user’s activities and is particularly useful for new users or users with limited trust.

Create or Edit Limit

A new limit can be created or an existing one edited via the context menu Create/Edit User Processing Limit. The following properties can be defined:

• Information Object: Selection of the object type for which the limit should apply. The available information objects are loaded from the system and typically include entities such as security, watchlist, account, portfolio, transaction and many more. After creation, the information object can no longer be changed.
• Day Limit: The maximum number of create, update, and delete operations that the user can perform per day for this information object. The value must be between 0 and 999.
• To Date: The date until which this limit is valid. After this date expires, the limit will automatically no longer be applied. This enables time-limited restrictions, for example during a test phase.

The configured limits are displayed in the expandable table row below the respective user. Individual limits can be edited or deleted via the context menu of the limit table.

Change Owner of Entities

In certain cases, it may be necessary to transfer the ownership of entities to another user. This may be the case, for example, when a user leaves the system, when data is to be consolidated, or when an administrator wants to take over test data from a user.

The function Change Owner of Entities can be selected via the context menu. The currently selected user in the table is considered the source user, and a target user must be selected from a list. All entities created by the source user are then assigned to the target user. This affects all types of entities such as securities, watchlists, portfolios, accounts, transactions and more.

Change Proposals

Grafioschtrader has a system for change proposals that is automatically activated when a user violates data or request limits. Any role can be blocked due to these limits. When a violation occurs, the affected user is automatically shown a dialog through which they can make a request to the administrators. Submitting this dialog triggers the change proposal.

Creation of Change Proposals

Change proposals are not created through manual requests, but automatically due to violations:

1. A user exceeds a configured limit (data or request limit)
2. The system detects the violation and increases the corresponding violation counter
3. The user is automatically shown a dialog explaining the violation
4. The user can enter a justification in this dialog and request unlocking or limit increase
5. By submitting the dialog, the change proposal is transmitted to the administrators

Types of Change Proposals

Unlock Request: When a user has been blocked due to too many violations of data or request limits, they are automatically shown a dialog for an unlock request. The user can justify here why the block should be lifted. The administrator can then reset the violation counters and release the user again.

Limit Increase Request: When a user with processing limits reaches the daily limit for a specific information object, a dialog is automatically displayed through which the user can request an increase in their limits. The administrator can review this request and adjust the limit or reject the request.

Display in the User Table

If there are change proposals for a user, these are indicated in the user table by symbols:

• U (column): Indicates that a user change proposal (unlock request) exists
• L (column): Indicates that a limit change proposal exists

Administrators can process these proposals via special functions and decide whether they are approved or rejected. Upon approval, the violation counters are reset or the limits are adjusted accordingly.