🚨 Talos User Management
While GCXONE manages the account identity, Talos handles the behavioral settings of how an operator interacts with alarms.
🛰️ How the Systems Sync
Talos uses your GCXONE user account as the base for its sessions. However, once a user enters the Talos interface, their permissions are governed by Talos Roles and User Types.
| Aspect | GCXONE Responsibility | Talos Responsibility |
|---|---|---|
| Identity | Email and MFA. | Leverages the GCXONE session. |
| Platform Access | Permissions to see Configuration. | Not applicable. |
| Workflow | Not applicable. | Permissions to view, process, or close alarms. |
| Behavior | Not applicable. | Automatic redirection and auto-assign rules. |
🎭 Creating Workflow Roles
To define how operators handle incident response:
- In GCXONE, navigate to Talos Workflow app.
- Select Company → Settings → Users.
- Click Add Role.
- Define the privilege level (e.g., "Full Operator" vs "View Only").
- Create a User Type: Every role needs a User Type that defines behavioral rules (like "Auto-redirect to next alarm").
📂 Alarm Distribution Groups
Talos allows you to organize sites into groups that are assigned to specific operator teams.
- Navigate to Configuration → Alarm Groups.
- Click Add New.
- Assign Sites: Choose which locations belong to this monitoring group.
- Assign Operators: Select which team members are responsible for these sites.
Load Balancing
Use Alarm Groups to balance workloads. For example, assign your "High Priority" group to your most senior operators.
🛠️ Troubleshooting Access
- Login Loops: If an operator can see GCXONE but gets a "Permission Denied" in Talos, ensure they have been assigned a Talos Role in the
Company → Userssettings. - Missing Alarms: Verify the operator is part of the correct Alarm Group for the site in question.