Signal Nodes

Note

Signal nodes require configuration before use. Your account must have signal sets defined by a library administrator. If signal nodes are unavailable, see Signal Sets Configuration or contact your administrator.

Signal nodes represent process steps and/or specific elements of an investigation type.

A signal set is a collection of related signals that together represent a complete process workflow (for example, a “Fraud Investigation” signal set might include signals for “Account Review”, “Transaction Analysis”, and “Documentation”).

Only one node for each signal can be in a case.

Note

Signal nodes are added differently than other nodes. They’re added via the signal tray in the top right.

Signal Sets

Signal sets are collections of signals to be used in a given process. They can be owned by either the library or a specific group. If owned by a specific group, it cannot be used by other groups.

Signal sets can also be disabled to prevent use in new cases. For more information about disabling signal sets, see Configuration: Signal Sets.

Active vs. Inactive

Signal nodes can be active or inactive. An inactive node indicates that the process step has been started, but the signal looked for has not been found yet.

This allows you to associate negative evidence (something not found) to a process step.

Signals can be toggled between active and inactive either via the left panel or via pressing Spacebar while the node is selected. Nodes are visually indicated as inactive by graying out the normally colorful node.

Tip

Signals allow you to track whether a process step was completed.

For example, if you are investigating an unauthorized account access, you may have a standard process that includes checking for failed login attempts.

You can create a signal for Failed Logins within your Unauthorized Access signal set, and attach screenshots of your internal tooling to that signal node.

If your investigation finds no Failed Logins, you can set the signal node to inactive, indicating that the process step was started, but no positive evidence of a failed login was found.