# Create a case manually

Supported in:
You can manually create a case to enter specific data. This is useful when you
need to ingest information on an alert; for example, information that was reported
from sources that aren't integrated with your detection pipeline (for example,
alerts reported from non-cyber channels).

1. On the **Cases** page, click add **Add a Case \> Create Manual Case**.
2. In the **Case** step, configure the following case details:
   - **Case Title**: Enter a title for the new case.
   - **Creation reason**: Optional. Enter the reason for creating the case.
   - **Environment**: Select the specific environment being monitored. If your organization has only one environment, it is selected automatically.
   - **Assign to** : Assign the case to a specific role or user. Select **(Assign to me)** to assign the case to yourself.
   - **Priority**: Set the priority level for the case.
   - **Mark as important** : Click the **Mark as important** toggle on if the case should be flagged as important.
3. Optional: Under **Tags**, select any existing tags, create new tags, or leave blank.
4. Optional: Under **Playbooks** , configure case-level automation:
   - **Attach playbooks automatically**: Enable the toggle to allow matching system triggers to attach playbooks automatically.
   - **Attach case playbooks manually**: Select up to 3 case-scoped playbooks from the menu to run across the case container. This field is enabled once an environment is selected.
5. To create the case without an alert, click **Create case** . Otherwise, click **Next** (or click the **Alert** step header) to add alert information.
6. Optional: In the **Alert** step, configure alert details:
   - **Alert Name**: Enter a name for the security alert. Leaving this blank creates the case without an alert.
   - **Occurrence Time**: Select the date and time the alert occurred. If left empty, the current time is used.
   - **SLA**: Specify a date and time by which the SOC team should resolve the case.
   - **Entities** : Add existing entities or create new ones.

     > [!NOTE]
     > **Note:** Adding entities requires both an Alert Name and an Environment.

   - **Attach alert playbooks manually** : Select up to 3 alert-scoped playbooks to execute on the alert.

     > [!NOTE]
     > **Note:** Attaching alert playbooks requires both an Alert Name and an Environment.

7. Click **Create case** .


   A confirmation notification appears with a link to open the new case.

> [!NOTE]
> **Note:** Service Level Agreements (SLAs) are calculated only for cases that contain an alert. If you create a case without an alert, no SLA is calculated.

**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/)