Understand workspaces, roles, and privileges in SystemLink to organize your data and tailor SystemLink Web Application to different types of users.

  • Automatic data encapsulation—The process of data being stored in the same workspace as the system that produces it. Along with defining roles and privileges, this process helps keep data organized and ensures users only see the data relevant to them.
  • Workspace—Grouping of systems, data, and other resources that server administrators define to control how users interact with SystemLink. A workspace also contains users assigned to roles. When systems in a workspace produce data, the same workspace automatically stores that data.
  • Default workspace—
    Workspace created when SystemLink installs. The following types of data can exist only in the default workspace:
    • Data from clients using AMQP
    • Data from pre-2020 R1 clients using HTTP
    • OPC UA and Cloud Connector sessions
    • File moving rules
    • Health tag data
  • Role—Set of privileges you want to assign to one or more users. Workspaces usually contain multiple roles. You can use the same role in multiple workspaces.
  • User—Person with access to some part of SystemLink and backed by an ID provider such as LDAP, Active Directory, OpenID Connect, or local Windows account. Users can have multiple roles in multiple workspaces. Users can use the SystemLink Web Application and SystemLink REST APIs to access the systems and data within the workspace they belong to.
  • Privilege—Action a user can do when using a SystemLink application or service.
  • Mapping—Connection you specify between a user and a role.