--- title: "Work incidents | Darwinium" slug: "working-as-a-fraud-operator" description: "Work incidents in Darwinium as a fraud operator, reviewing assigned cases and recording investigation outcomes." updated: 2026-10-16T02:27:25Z published: 2026-05-04T05:17:37Z canonical: "docs.darwinium.com/working-as-a-fraud-operator" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.darwinium.com/llms.txt > Use this file to discover all available pages before exploring further. # Work incidents This guide walks through how fraud operators can review and take action on incidents using the **Darwinium Incident Manager**. It includes annotated screenshots to help you get up and running quickly. --- ![image.png](https://cdn.document360.io/db6f7316-640d-4099-b5a1-b01b4dbd17fc/Images/Documentation/image%28225%29.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A34%3A55Z&se=2026-11-23T00%3A34%3A55Z&sr=b&sp=r&sig=1kCIf4cTKhcnrgUzeYdKLTID5gQ6%2FT1wemq5CAoS5UI%3D) ## ๐Ÿš€ Getting Started When you log in to the Incident Manager view, you'll see your **Personal Queue** on the left. This contains all incidents assigned to you. ### Step 1: Take a New Incident Click the **"Take"** button at the top of the queue to assign yourself the next available incident. ![Take button and personal queue](attachment:file-DCo4Y1jK98QhWRgMrm2vTj) - Once assigned, the incident will appear in your personal queue (e.g. INC-34). - The label (e.g. "Blue Queue") indicates the source queue. --- ## ๐Ÿ” Step 2: Review the Incident After taking an incident, youโ€™ll be shown a detailed view like this: ![Main incident view with annotations](attachment:file-DCo4Y1jK98QhWRgMrm2vTj) ### Key Sections - **Incident Tabs**: Toggle between core, all, or related events. - **Incident Rule Details**: Shows the rule and signal that triggered the alert. - **Incident Visualization**: Geolocation, timeline chart, and other widgets to help you understand behavior. - **Events Table**: Shows detailed event data. Default columns include any attributes used in the detection rule. Columns can be customized using the same controls found in the Investigations or Journey views. - **Right Panel**: Shows event metadata when a row is clicked. > ๐Ÿ’ก Tip: You can pause/resume the timer to track time worked on the case. --- ## ๐Ÿงช Step 3: Investigate Events - Select events using the checkboxes in the table. - Right-click any selected event to take granular actions: ![Event context menu](attachment:file-5biBWFnviLfG1bbT7yjZNb) ### Available Actions: - **Show raw data** - **Close with alternative close action** (set attributes, labels, or event types) - **Color**: Visually tag specific cells or values - **Copy / Export**: Useful for external analysis or evidence collection > You can exclude certain events from bulk actions this way. --- ## โœ… Step 4: Take Action Once reviewed, either **close** or **escalate** the incident. ### Option A: Close the Incident Click **Close Incident** and choose an action to apply to all events. ![Screenshot 2025-06-12 at 5.30.34 PM.png](https://cdn.document360.io/db6f7316-640d-4099-b5a1-b01b4dbd17fc/Images/Documentation/Screenshot%202025-06-12%20at%205.30.34%E2%80%AFPM.png?sv=2026-02-06&spr=https&st=2026-11-22T23%3A34%3A55Z&se=2026-11-23T00%3A34%3A55Z&sr=b&sp=r&sig=DF3rpHtjZU9ZnjTifCq6IDyHQTfVu2awv1cRQ9N5XlA%3D) Available close actions are configured by your queue administrator per [Configuring Queues](/v1/docs/configuring-queues) These actions will apply to all events unless excluded manually. ### Option B: Re-assign the Incident Click **Re-assign** to escalate the incident to another operator or queue. The incident remains open and visible to the receiving team. --- ## ๐Ÿงพ Additional Notes - **Time Tracking**: Automatically starts on open. Pausing is optional. Used for SLA and performance reporting. - **Rule Context**: The rule that triggered the incident is always visible, including the feature threshold and signal name. - **Event Table Defaults**: Columns shown include all attributes referenced in the detection rule condition by default. - **Custom Views**: Table layout and widgets can be configured per user and persist across sessions.