System Operators

System Operators are internal Sirius users who manage the platform, not customer plants.

Unlike standard users:

• they do not have Roles or Zones
• they have a Level
• they see an extra Configurator section in the side menu, marked by the purple theme

Levels

Each System Operator has one of the following fixed levels:

• Restricted: view only
• Technician: limited configuration
• Administrator: full control

Operators list

Operators are displayed as cards showing:

• Username
• First and Last name
• Level
• Status (Active, Disabled, Blocked): indicates whether the user can access the system.
  • Active: the user is enabled and can log in.
  • Disabled: the user is disabled and cannot log in.
  • Blocked: the user is blocked for security reasons or by an administrator’s decision.
    This status is used to temporarily prevent access, for example after suspicious activity or an administrative action.

• E-mail

Search and filters

At the top of the page you can quickly find users and narrow down the list:

• Search: Filter users…
• Status filters: Active, Blocked, Disabled
• Levels filter: Filter by levels
• Status or alphabetical order: Status order button. By severity: Blocked, Active, Disabled

Create a System Operator

To create a new operator:

1. Click Add
2. Enter Username, First name, Last name, and Email
3. Select the Level
4. Set the login credentials

System Operator details

Opening an operator shows several tabs.

Tab: Profile

Includes:

• Personal information (Username, First name, Last name, E-mail)
• Assigned Level
• Preferences (Language, Appearance, Timezone, Date format)

Each section can be edited using the edit (pencil) icon.

Tab: Security

This tab includes:

• Two-Factor Authentication (2FA) status
• configured Credentials
• available security actions

Two-Factor Authentication (2FA)

For System Operators, 2FA is always enabled and mandatory.
It cannot be disabled.

Available action:

• Reset 2FA forces the operator to set up 2FA again at the next login.

Credentials

Each System Operator has one or more login credentials.

For each credential you can:

• Reset Password
• delete it

Special Identity Provider

System Operators are linked to a special internal Identity Provider that is separate from the one used for regular users.

This ensures:

• Access to the Configurator is always possible, even if external LDAP/AD servers are unavailable
• Independent password policies for system operators
• Complete isolation from customer authentication systems

Tab: Sessions

Shows the operator’s active sessions.

Tab: Activity

Shows the operator’s activity history.

Impersonation (not implemented)

In the future, a System Operator will be able to impersonate a Role and a Zone to view the system as an end user.

Frequently Asked Questions

What is the difference between Users and System Operators?

Users are customer users who work on plants.
System Operators are Sirius users who manage the platform.

Why don’t System Operators have Roles and Zones?

Because they do not operate on customer plants.
Their privileges are defined by their Level (Restricted, Technician, Administrator).

Why is 2FA mandatory?

System Operators have access to critical system functions.
2FA is mandatory to ensure adequate security.

Can I disable 2FA?

No. 2FA is always enabled for all System Operators.

What happens when I reset a password?

The system temporarily sets the password equal to the username. The operator must change it at the first login.

What is Impersonation for?

It will allow viewing the system as an end user (Role + Zones). The feature is planned but not yet available.

Why do System Operators use a special Identity Provider?

System Operators need guaranteed access to the platform's Configurator section. Using a separate Identity Provider ensures they can always log in, even if external LDAP/AD servers are unavailable.

Do password policies apply to System Operators?

Yes. System Operators must follow password policies (minimum/maximum length, character requirements), but these are managed separately from regular user policies.