# Week 41, 2023

Come, gather, and read about all of Oort’s goodness we’re releasing to you this week!

### ✅ Mark Individual Observations as Interesting

In [last week’s release](https://oort.io/blog/release-notes-week-40-2023), we introduced the concept of “observations” that make up our Checks. For any check, there may be multiple observations made by Oort and you can view these within the User Profile’s Checks tab.

Typically, you’re able to “Resolve” the check for a user if you mark the check as normal behavior. However, given that there may now be multiple observations, you may wish to make some as normal behavior and others as not. With this release, you can give feedback for each observation to either “Mark as interesting” or “Mark as normal behavior”. The check will only be resolved if you mark all observations as normal.<br>

<figure><img src="https://582105988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqPSBzsjxd7KYg9DNVZ4l%2Fuploads%2FrejDkODT8hzJwvIgGy0S%2FsVAby2ivEc2AQjFftGcUy0iWlHI64ECKnxmvHY8pripiL5tiwkixZdAkfI1_XNAvM-98JIKMjPkMnDHvx0-EwIxBUTCsYkat4ftnBAzj-LcnLwxaVrZ3xmHyiMQHw-g9un6hqXpU_EeL.png?alt=media&#x26;token=74a576a4-c2e9-4af9-909b-d3b9aeb3915b" alt=""><figcaption></figcaption></figure>

<br>

### 🎯Access More Detail on User Activities

The Activity Tab in the User 360 profiles is one of the best places in the dashboard to investigate a user. In this table, you can scroll through a history of all events associated with that user, with each row displaying the most pertinent information for the event. Clicking into the row will give you access to the full, raw data behind the event.

With this release, we’ve beefed up the context you see within the “Target” column of the table. This means that you can better identify the target application, group and other factors without clicking to view the raw data. <br>

<figure><img src="https://582105988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqPSBzsjxd7KYg9DNVZ4l%2Fuploads%2FO2RQ9IrHvUxQi1rpWTih%2F8VnaZ_T7U_CQDU2EdtgA52MRSRwTd_AVepS-tkXVLStB6DKisswLB_BE_-25GKyToYCJIRM1pjs-cnN1TEx_HZvfcnt2aJU10XdiYBPCBaOf9MmYHC330jmFuXl2xK4DeqEOuv_LbDL9.png?alt=media&#x26;token=e2e28ce0-5525-46da-8b4a-c45fae7e6fa8" alt=""><figcaption></figcaption></figure>

<br>

### ⚙️Added Collection for Duo Advanced

We’ve added the Endpoints data type to our Duo integration. These endpoints refer to “the laptops, desktops, tablets, mobile phones, and other devices where your end users access Duo protected applications and services, as well as 2FA Devices, which are the enrolled phones and other mobile devices where users approve Duo authentication requests.” These are all incredibly helpful data points to associate with your identities, and provide even greater visibility.&#x20;

Duo Advanced customers will be able to access this data type. In Oort, this will be disabled by default, but you can enable it by going to Integrations - Duo - Edit Settings - Advanced Settings.&#x20;

<br>

<figure><img src="https://582105988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqPSBzsjxd7KYg9DNVZ4l%2Fuploads%2Fb1X4CIB0bAtaP6hpD0gM%2FWcnc4VYg_9-ajoIddNfBKhGCLBmSCr-cX82DRs55tBDAM6RZ5ULW5zHzoSBMaMR5yGJajkO_v7qAWUDFeeZp_z4JHCPMWu91umEmDE8kPDTMBPiayxSufhFlQsGnoX8XKn6CRCNzRSn-.png?alt=media&#x26;token=6addc30d-4d76-4f1a-b61e-ecb60d38577c" alt=""><figcaption></figcaption></figure>

<br>

**Bug Fixes and Minor Improvements**&#x20;

**Exclamation Points in Webhook URLs.** Exclamation points are now supported for the URL field in the Webhook settings. Go to Integrations - Webhooks to learn more.&#x20;

**Risky Sign In.** The default ignore list for risky sign ins has been updated.

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.oort.io/release-notes/2023/week-41-2023.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.