When logging on to a SmartStruxure server or Project Configuration Server, you have to authenticate yourself by using a valid user account. The user account has to belong to the same domain as the server you log on to.
The user account has to be a member of at least one user account group or be mapped through an active directory user account group. To restrict the user, software permissions are added to the user account group or to the individual user account. One or more customized workspaces can be connected to the user account group.
When logging on to the SmartStruxure server that acts as the domain controller, in this example an Enterprise Server, you have access to all SmartStruxure servers in the domain without using additional log on. If you log on to an individual SmartStruxure server, in this example a Automation Server, you have no access to other SmartStruxure servers in the domain.
Building Operation considers a user account valid when:
The user account exists
The user account is not disabled or expired
The user account belongs to a user account group or mapped active directory user group
The user account group belongs to a domain
The user account has defined software permissions, either defined on the individual account or inherited from the user account group
A user account can be a member of one or more user account groups and belongs to a particular domain.
For more information, see User Accounts and User Account Groups .
A Building Operation domain contains user accounts, user account groups, software permissions, workspaces, and one or several SmartStruxure servers. The SmartStruxure server that hosts and administers the domain is called the domain controller.
For more information, see Domains .
Software Permissions are used to control user activities in a software application. For example, you can set up these permissions to manage the type of data and commands the user has permission to within a workspace, panel, or domain. Software permissions comprise path permissions and command permissions.
For more information, see Software Permissions .
Building Operation provides two methods to log on to the system. Either you log on as a Windows User with your Windows Active Directory user account or as Building Operation user with your Building Operation user account.
For more information, see Log On Methods .
The workspace defines the content and layout of WorkStation. The content and layout of the workspace can be adapted to users or user account groups different tasks.
For more information, see Workspace Management .
The automatic logoff function makes it possible for the system to automatically log off a user after a specified time of inactivity.
For more information, see Automatic Logoff .
A guest logon is used when you want the user to get immediate access to Building Operation using WebStation.
For more information, see Guest Logon in WebStation .