Table Of Contents ≪ 8.2.2. Common 8.2.4. Authentication Functions ≫

8.2.3. System Management¶

8.2.3.1. Some user codes are not available for use, because they are reserved by system.¶

Following user codes are reserved by the system and cannot be used.

anonymous ： unauthenticated user

system ： execution user in tenant initial setting

im_job ： job net execution user

8.2.3.2. System Administrator can access all screens.¶

System administrator can access all screens and therefore can access screens of general users.

However, since some of these screens do not assume access by system administrator, screen display or update process may fail.

System administrator is supposed to do only those operations that can be accessed from home screen.

Error will occur on the following screens.

Locale Setting (for general users)

When displayed, [HTTP 500 : Servlet Exception] occurs.

Password Setting

Can be displayed. However, error will occur at the time of update.

8.2.3.3. User code of system administrator should not overlap with the user code of general users.¶

If there is an overlap, data mismatch may occur when the system administrator uses several functions for general users.

For example, user code when outputting log may become ambiguous,

or my menu and personal setting may become shared between system administrator and general users.

8.2.3.4. If you click [Return to Home Screen] on system administrator’s authority error screen, you may transition to the home screen of general users.¶

With the limitation [ If you leave the log-in screen with no action for a while, log-in cannot be made. ], transition to authorization error screen will result,if you leave the log-in screen of system administrator with no action for a while.

In this case since the log-in was not made by the system administrator, clicking [Return to Home Screen] on the Authority Error Screen will result in the transition to home screen of general users.

Table Of Contents ≪ 8.2.2. Common 8.2.4. Authentication Functions ≫