BP-2480: Release notes (2026-04-13)

docs/analyze-data/explore/cypher-search.mdx

@@ -141,6 +141,24 @@ BloodHound allows you to import and export queries for easy sharing and backup.
 * **Import queries from JSON files**: Easily add new queries by dragging and dropping JSON files or compressed JSON files into the UI. BloodHound validates the files for correct syntax and notifies you of any errors.
 * **Export a saved query to a JSON file**: Share or back up your queries by exporting them in JSON format. Export is available for saved queries only. You cannot export prebuilt queries directly.
 
+### Disable Query Timeout
+
+For queries that may require more time to execute, you can now [disable](/analyze-data/explore/cypher-search#disable-query-timeout) the default query timeout on a per-query basis.
+
+This gives you more control over long-running queries and allows you to retrieve results that may take longer to compute without being prematurely terminated by the timeout.
+
+<Note>
+  This option is not visible by default and requires a database configuration change.
+</Note>
+
+  <Frame>
+    <img
+      src="/images/release_notes/9_0_0/disable-query-timeout.png"
+      alt="Screenshot of the Cypher query timeout bypass option in the query editor"
+      style={{ width:"70%" }}
+    />
+  </Frame>
+
 ## Write Custom Queries
 
 One of the most overlooked features of BloodHound is the ability to enter raw Cypher queries directly into the user interface. Likely, a lot of that has to do with the fact that it's not a very emphasized feature and requires learning Cypher. However, with some work, using raw Cypher queries can let you manipulate and examine BloodHound data in custom ways to help you further understand your network or identify interesting relationships.

docs/analyze-data/explore/search.mdx

@@ -55,9 +55,9 @@ For example, if you want to find a user named "bob", type "bob" in the search bo
 
 ### Filter by node type
 
-You can also constrain your search to particular _built-in_ node types (AZ/AD) by prepending your search with the appropriate node label.
+You can also constrain your search to particular node types by prepending your search with the appropriate node label.
 
-<Note>Support for filtering by OpenGraph node types is coming at a later date.</Note>
+<Tip>This works for both built-in node types (AD/AZ) and OpenGraph node types.</Tip>
 
 For example, use the following search query to find group nodes that contain the word "admin":
 
@@ -211,7 +211,7 @@ Use the graph visualization options at the bottom of the **Explore** page to cus
 
         - **Expand**—Maximize the graph view to fill the screen for better visibility
 
-        - **Columns**—Search, add and remove columns, reset column size, reset defaults, and pin columns in the table layout
+        - **Columns**—Search, add/remove, sort, reorder, reset column size, reset defaults, and pin columns in the table layout
       </Tab>
     </Tabs>
 

docs/analyze-data/posture-page.mdx

@@ -18,6 +18,52 @@ Filter the view by domain, privilege zone, and time range to assess your overall
   />
 </Frame>
 
+## Filters
+
+You can filter the posture view by environment, privilege zone, hygiene, and time range to assess your overall risk and compare trends over time. 
+
+Use these filters to focus on specific areas of interest or to track the impact of remediation efforts. For example, you can filter by a specific environment to see how posture has changed in that environment over time, or filter by hygiene findings to track trends in tier-agnostic risks.
+
+### Environment
+
+The environment filter allows you to view posture trends for a specific platform, such as an Active Directory domain or Azure tenant. 
+
+This can help you understand how posture is changing within that environment and identify areas that may require additional attention.
+
+You can also filter on severity levels to focus on trends in high-risk Attack Paths. For example, you can filter to show only **CRITICAL** Attack Paths to see how the most severe risks are changing over time.
+
+### Date range
+
+The date range filter allows you to compare posture trends between analysis runs. For example, you can compare the current state of your environment to a previous point in time to see how your risk posture has changed.
+
+Choose from preset ranges or set a custom range to compare specific analysis runs. Custom date ranges include a time picker, so you can set exact start and end times.
+
+<Tip>
+  For meaningful trend comparisons, use the same filter scope and similar date ranges across reviews. Custom date ranges include a time picker, so you can set exact start and end times.
+</Tip>
+
+#### Custom Range
+
+Use a custom time range when you need tighter control over posture trend boundaries for the **Attack Paths** table and posture charts.
+
+The time picker disables future hour selections when the end date is set to today, and manual future end time entries are blocked with an inline validation error.
+
+  <Frame>
+    <img
+      src="/images/release_notes/9_0_0/time-validation.png"
+      alt="Screenshot showing the custom range validation improvements, including disabled future hour selections and inline validation error for manual future end time entries"
+      style={{ width: "70%" }}
+    />
+  </Frame>
+
+After you confirm a valid custom range, posture trend and completeness charts render through the selected end date.
+
+### Chart scale
+
+The chart scale filter allows you to adjust the scale of the posture graphs to better visualize trends. For example, if you have a large number of findings, you may want to use a logarithmic scale to better see changes over time.
+
+The linear scale shows consistent ranges clearly, while the logarithmic scale highlights outliers and wide variations in the data.
+
 ## Attack Paths
 
 The **Attack Paths** table displays the Attack Paths with active findings during the selected date range. Each Attack Path shows:

docs/collect-data/enterprise-collection/data-retention.mdx

@@ -12,6 +12,8 @@ BloodHound Enterprise (BHE) will perform data reconciliation. That is, BHE will
 
 [HasSession](/resources/edges/has-session) edges are generated to indicate patterns of behavior rather than session active at any exact moment. For this reason, HasSession edges are only reconciled based on their retention/time-to-live expiring, rather than reconciling upon follow-on collections no longer seeing the active session.
 
+If you need to refresh session data immediately, an administrator can delete **HasSession** edges from **Database Management** before recollecting session data instead of waiting for the retention window to expire.
+
 ## Data retention
 
 BloodHound Enterprise (BHE) implements data retention, i.e., a time-to-live where data that has not been collected and ingested for a certain period will get deleted from BHE. This retention period is configurable and is by default:

docs/docs.json

@@ -832,14 +832,15 @@
                 "group": "Release Notes",
                 "pages": [
                   "resources/release-notes/summary",
+                  "resources/release-notes/2026-04-13",
                   "resources/release-notes/2026-03-23",
-                  "resources/release-notes/2026-03-04",
                   {
                     "group": "Archive",
                     "pages": [
                       {
                         "group": "2026",
                         "pages": [
+                          "resources/release-notes/2026-03-04",
                           "resources/release-notes/2026-02-11",
                           "resources/release-notes/2026-01-22"
                         ]

docs/manage-bloodhound/auth/environment-targeted-access-control.mdx

@@ -36,7 +36,7 @@ After you save ETAC settings, scoped users see only the data and navigation opti
     />
   </Frame>
 
-- On the **Privilege Zones** page, a _Permission Denied!_ message can appear for ETAC users even when they have authorized environment access, depending on their role permissions and ETAC scope. When access is allowed, users can view objects from their authorized environments only; available actions still depend on role permissions.
+- On the **Zone Builder** page, a _Permission Denied!_ message can appear for ETAC users even when they have authorized environment access, depending on their role permissions and ETAC scope. When access is allowed, users can view objects from their authorized environments only; available actions still depend on role permissions.
 
 - Access to all other pages is unaffected, but the baseline [permissions](/manage-bloodhound/auth/users-and-roles#user-role-definitions) of the assigned role still apply.
 
@@ -72,7 +72,7 @@ Use the create or edit user workflow to configure ETAC for an eligible role and
     - **Attack Paths**: The user sees no data and cannot use filters.
     - **Explore**: The user can open the page, but sees a _Role-based access filtering applied_ message and cannot see data.
     - **Posture**: The user can open the page, but cannot see data or use filters.
-    - **Privilege Zones**: The user can open the page, but may receive a _Permission Denied!_ message. Users can view objects from their authorized environments only; available actions still depend on role permissions.
+    - **Zone Builder**: The user can open the page, but may receive a _Permission Denied!_ message. Users can view objects from their authorized environments only; available actions still depend on role permissions.
 
   </Step>
   <Step title="Select environments manually">

docs/opengraph/developer/api.mdx

@@ -19,4 +19,4 @@ description: "Information on how to use the OpenGraph API"
 | `GET`    | [/api/v2/custom-nodes/\{kind_name\}](/reference/custom-node-management/get-custom-node) | Get configuration for a specific node type.                                          |
 | `PUT`    | [/api/v2/custom-nodes/\{kind_name\}](/reference/custom-node-management/update-custom-node) | Update the configuration of an existing node type.                                   |
 | `DELETE` | [/api/v2/custom-nodes/\{kind_name\}](/reference/custom-node-management/delete-custom-node) | Delete a custom node type.                                                           |
-| `POST`   | [/api/v2/clear-database](/reference/database/delete-your-bloodhound-data)             | Clears all elements of the database including Base Node Types and Custom Node Types. |
+| `POST`   | [/api/v2/clear-database](/reference/database/delete-your-bloodhound-data)             | Delete selected BloodHound data, including targeted graph data such as HasSession edges. |

docs/opengraph/faq.mdx

@@ -24,9 +24,12 @@ You can remove generic data by using one of the following three (3) options:
     - All Data
     - Active Directory Data
     - Azure Data
+    - HasSession edges
     - … X Data (there will be 0 or more checkboxes here that allow you to delete any data that had been ingested with a `source_kind` provided)
     - Sourceless Data (checking this box will delete all entities that do not have a kind that can be found in the `source_kinds` table.  You can observe the `source_kinds` your BloodHound instance is currently aware of by calling `GET api/v2/graphs/source_kinds`.)
 
+   Use the **HasSession edges** option when you need to refresh time-sensitive session data without deleting the rest of the collected graph.
+
 3. API: `Clear-Database`
     - See the [OpenGraph API Page](/opengraph/api) for more information
 
@@ -36,8 +39,6 @@ Yes! BloodHound supports **Search** and **Pathfinding** for [_structured_](/open
 
 For [_generic_](/opengraph/extensions/manage#generic-graphs) graphs, only **Search** is supported.
 
-Filtering by OpenGraph node types in **Search** is not yet supported.
-
 <Note>
 All forms of OpenGraph data support Cypher querying in general.
 </Note>