---
title: "November 2026"
slug: "november-2026"
updated: 2026-11-11T11:49:41Z
published: 2026-11-11T11:49:41Z
canonical: "docs.databee.buzz/november-2026"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.databee.buzz/llms.txt
> Use this file to discover all available pages before exploring further.

# November 2026

## New Features

- A new **Nectar Usage** sub-tab under **Access Management** shows AI token usage (Nectar Units) for tenants with the Controls entitlement: the units used and remaining over the contract term, and a table of users with a Controls Builder or Controls Analyst seat showing the total units each has consumed, sorted by usage from highest to lowest.
- Each selected control in step 3 of the Controls first-time setup now has an **Add control details** button that opens a window where you can set why the control matters, the risks it addresses, its owner, and your roles and responsibilities, and save them with **Save Details**.
- Metrics can now be saved in a draft state, both when created from within the controls step and when created directly.

## Feature Enhancements

- You can now clone a workspace from its detail page. The clone is given a unique name.
- Library widgets on the Workspace detail page can be refreshed on demand. While a metric is refreshing, its card shows **Recalculating** in place of the last updated time and the refresh button shows a spinning icon; the normal display returns when the refresh completes.
- When you choose a sub-metric for a metric, the list now shows each sub-metric's current reading, its unit, and the number of metrics that already use it.
- Metric and sub-metric cards on the list view now show the current reading and when it was recorded, along with who created the metric.
- A unit can now be set on a sub-metric when you create or edit it, replacing the unit previously set with the threshold. The **Unit** list offers default options and a **Custom** option for free-form text.
- A **Delete** button is now available on the sub-metric detail page.
- When you create a metric, all controls are now listed for selection, matching the list on the Controls page.
- A control now shows as green when all of its metrics are green and red when any are red, and the "not accessible" indicator is removed from the control card.
- Metrics and sub-metrics are now visible to everyone by default and are restricted only when sharing rules are applied. Sharing is managed on sub-metrics, and a metric is available to a user only when they have access to all the sub-metrics it uses. Lists of metrics and sub-metrics are filtered to the ones you can access.
- When a Workspace includes a private metric that you do not have access to, the widget keeps its layout and title and shows a message with the metric creator's name and email so you can request access.
- Controls permissions are tightened: creating, editing, and deleting metrics, sub-metrics, and controls requires the manage metrics permission, and the create and edit pages are hidden from users who do not have it.
- Existing connectors are now shown as clickable cards with more detail about where each connector came from and what it connects to, and connectors that do not have credentials set up correctly are not shown.
- The Controls metric builder chat can now be stopped while a query is running. If you send an updated message in the same chat, it runs with your new request and keeps any connector or credentials you already selected.
- Metrics now generate data only while they are live: data collection is not started for draft metrics, starts when a metric moves from draft to live, and stops when a live metric is moved back to draft.
- Ask DataBee can now answer questions about the Controls metrics and sub-metrics you have access to and describe the state of a workspace, including its metrics and insights, for example which controls need the most attention or which metrics changed most in the last week.
- When ServiceNow is selected in Exposure Management remediation routing, administrators can now choose a default ServiceNow connection for the whole tenant (or choose **No default (choose when sending)**). In the **Compile remediation work** window, the connection that will receive the work is shown, and with more than one connection you can change it for that dispatch. If no ServiceNow connection is available, email is selected instead.
- The **Fixes** tab is now available on the Exposure Management application details page.
- The **Effective points** column is removed from the Exposure Management **Scoring settings** page.
- The expanded CVE details on the Exposure Management Findings tab no longer show the status ID under OCSF Status or the "exactly as the scanner sent it" text under Scanner Status.
- The Exposure Management onboarding checklist no longer requires line-of-business applications, and the **Scoring settings** tab remains available when onboarding is skipped.
- The data lake tables that store Exposure Management routing settings and dispatches now include ServiceNow-related columns, and the business owner copy column is removed from routing settings.
- Tenants on a trial with the Controls entitlement now see a trial tracker embedded in the trial dashboard. The tracker adds step notes and how-to links, tracks the steps you have left, includes a survey, and is the default landing page for trial tenants, with a way back to it from anywhere in the product.
- The **Users** page under **Access Management** now shows your tenant's user quota and, for tenants with the Controls entitlement, the quota for each seat type, with a warning when you reach 90% of a limit. A seat column is added when the Controls entitlement is enabled. Adding a user is blocked when the user limit is reached, and assigning the Controls Builder, Controls Analyst, or Controls Viewer role is blocked when all seats of that type are in use.
- For tenants on a trial, the **Data Feeds** page is hidden and selecting **Data** in the top navigation opens **Connectors**. Tenants not on a trial continue to open **Data Feeds**.
- The Controls Posture page now loads only the frameworks and controls selected in your compliance configuration and shows real data in place of placeholder values: status, compliance percentage, trend, metrics, refresh cadence, and last evaluated time for each control, plus compliance, assessment, metric, evaluation, and tool lineage details in the framework summary and drawer. The Control Portfolio table can be searched and filtered.
- A framework that has selected controls can no longer be unchecked during framework selection, and the reason is shown.
- The Exposure Management exposure score table is clearer. **Volume** is renamed **Volume factor**, the multiplier is shown after the exploitation chip, and the points always add up to the subtotal shown. When the score reaches the 100-point cap, a **Subtotal** row and "capped at 100" are shown, and the footer is a single line with the full explanation under **How is this calculated?**.
- Saving changes to Exposure Management scoring settings now recalculates application scores right away instead of waiting for the next scheduled run.
- Exposure Management scoring rules now include application rules in the score explanation.
- When the Controls metric builder chat cannot complete a sub-metric, for example because the system cannot be found, has no public API documentation, cannot be reached, or the connection details are incorrect, it now tells you which steps succeeded, which step failed and why in plain language, and what to try next, including contacting DataBee support if the problem persists.
- The **Roles** list when creating or editing a user is now in alphabetical order.
- The **Nectar Used** values on the Nectar Usage page are now plain numbers instead of links that opened an empty side panel.
- Tickets that Exposure Management creates in ServiceNow now include device details for each finding: device hostname, operating system and version, when the device was last patched, when the finding was first seen, whether the vulnerability is on the CISA Known Exploited Vulnerabilities list, and its due date.
- For tenants on a trial that do not have a support portal, the **Support** link and the **Get help** link on the trial dashboard now open an external support form instead of an email message. Other tenants without a support portal continue to open an email to support.
- Follow-up questions suggested by Ask DataBee are now worded from your point of view, as questions you can send as they are, instead of questions the assistant is asking you.
- The metric details page now has a **Refresh** button for live metrics. While the metric is refreshing, the page shows **Recalculating** in place of the last updated time and the button shows a spinning icon, and the reading is reloaded when the refresh finishes.
- When you define a control in the Controls setup, a **Use Existing** button next to **Add New Metric** lets you pick from the metrics you can already see, excluding metrics already linked to that control.
- The Controls setup wizard is easier to follow: the current step is highlighted in the progress bar, the step 2 footer now reads, for example, "1 Control across 1 framework" with correct plurals, framework cards line up their text, and a hint ("Select at least one control to continue.") explains why **Continue** is disabled.
- The next evaluation time shown for a sub-metric now includes the time as well as the date, in your preferred time zone and date format.
- When a metric is not active, its details page now shows the message "This metric is not active and is not being evaluated." instead of requesting a reading.
- **Test Connection** now shows clearer error messages. When a ServiceNow instance cannot be authenticated, the message explains that the instance may be disabled or the integration credentials may no longer be valid, and asks you to verify that the instance is active in ServiceNow and try again.
- When you add a connector in the Controls metric builder chat and the system offers more than one authentication option of the same type, you can now choose between the options and enter the credentials for the one you select.
- Control status in the Controls portfolio is now calculated consistently: a control is **MET** when every metric is met, **AT RISK** when at least one metric is at risk, **NOT MET** when at least one metric is not met, and **NOT ASSESSABLE** when none of its metrics can be assessed. Controls with an unrecognized status no longer prevent the Controls Posture page from loading.
- When no Controls report has been published yet, the Controls Posture page now shows a "No posture report has been published yet" page. Users with the manage metrics permission are taken to Controls setup instead, and users who can only view reports are told that their role can view reports but cannot generate them.
- When you set the warning and alert values in the **Thresholds** window, the values must now be in a valid order. For "Higher is better" the alert value must be lower than the warning value, and for "Lower is better" it must be higher. An error message is shown and **Save Thresholds** is disabled until the order is corrected.
- For percentage metrics, the **Warning** and **Alert** fields in the **Thresholds** window are now labeled with **(%)**, and thresholds shown on the metric details page include the % sign. The metric trend graph for a percentage metric also now extends beyond 100 when the readings or thresholds are higher than 100.
- Units of measure are now shown consistently for metrics and sub-metrics: metric and sub-metric cards, the sub-metric list used when you create a metric, trend graph threshold labels, and the "passes when" and "warns below" text in the Controls setup now include the unit, for example "17 employees" or "86.4%".
- In step 3 of the Controls first-time setup, the control details button now reads **Edit control details** and shows how many of the four optional fields are filled, for example "2 of 4 filled".
- When you create a new sub-metric for a metric of the **Value** type, the name and description of the metric are now filled in for you and can be edited. Sub-metrics for the numerator and denominator of a **Percentage** metric start with blank fields.
- The **Tags** column is no longer shown in the Workspaces list view.
- The Controls metric builder chat no longer asks for or proposes a refresh schedule when it builds a sub-metric.
- Exposure Management now appears as soon as the first page of applications has loaded, instead of showing a loading screen until every page of applications, the overview, and work orders are loaded. Queue and application details that are requested more than once at the same time are now loaded only once.

## Bug Fixes

- Fixed an issue where an existing user could not be added to a second tenant. Users from your organization's identity provider can now be added to more than one tenant on the cluster, while locally managed accounts still cannot be reused on tenants that use the identity provider.
- Fixed an issue where the Data Catalog icon appeared even when no data lake was configured. It is now shown only when a data lake is configured.
- Fixed the confirmation message when deleting a workspace, which referred to insights and metrics that are not available. It now asks "Are you sure you want to delete this workspace?".
- Fixed an issue where the Exposure Management **Scanner status** badge in an application's Findings tab and Status Layers panel was colored from DataBee's own status instead of the status reported by the scanner. The scanner's status is now shown as reported, without a status color.
- Fixed an issue where metric and sub-metric trend graphs showed a different number of data points depending on the selected time range. Trend graphs now use a consistent interval for each time range.
- Fixed an error in the Controls metric builder chat that could occur when the assistant attempted several actions at the same time.
- Fixed an issue where resuming a Controls metric builder chat or sending a new message first showed messages from your previous message.
- Fixed an issue where the connector edit page did not show the credential fields, so authentication details could not be updated. Credentials are now returned to the page and can be edited, with secrets obfuscated.
- Fixed an issue where changing a connector's name also changed its secret location, which could break sub-metrics that reference the connector. The secret location no longer changes when a connector is renamed.
- Fixed an issue where tickets sent to ServiceNow from Exposure Management were created as service catalog tasks and did not appear under Incidents. They are now created as incidents.
- Fixed an issue where the **Send** button in the **Compile remediation work** window changed to "Sending..." whenever a field was changed. It now shows "Sending..." only while the work is actually being sent.
- Fixed an issue where the selected tab in the Exposure Management application drawer turned white and its text became unreadable when the pointer moved outside the tab.
- Fixed Dark Mode styling for the ServiceNow connection list in the **Compile remediation work** window and for the Exposure Management onboarding page.
- Fixed an issue where long Ask DataBee responses, such as markdown text, lists, or tables, extended beyond the response card on first display. Text now wraps within the card and wide tables scroll within it.
- Improved how Ask DataBee chooses which assistant answers a question, so that general platform questions and questions that mention OCSF class names are routed correctly.
- Fixed an issue on the **User Not Found** page where selecting the first seen date before the page had finished loading reloaded the same page instead of opening the entity details for that date.
- Fixed an issue where the default ServiceNow connection selected in Exposure Management **Remediation Routing Settings** was not saved or shown after you saved the settings.
- Fixed an issue where cloning a workspace with a very long name returned an error. The copy's name is now shortened as needed so that it fits.
- Fixed an issue where Ask DataBee told Controls Analyst users that the names of configured frameworks were not visible to them. The assistant now takes your role into account and shows the framework names.
- Fixed an issue where the Controls Posture page showed controls from only one framework when controls were configured in two frameworks.
- Fixed an issue where metric and sub-metric readings and trends were returned empty even when data existed.
- Fixed an issue where the text in the **Unit** list on the **Describe your sub-metric** screen was larger than the text in the **Name** and **Description** fields.
- Fixed an issue where uploading an image to a Workspace failed with a generic error when the image was too large. The maximum image size is now 1 MB, and an image that is larger shows a message stating the limit before it is uploaded.
- Fixed an issue where the Controls metric builder chat showed a daily schedule for a proposed sub-metric that had no schedule. It now shows **Not scheduled**.
- Fixed an issue where **Test Connection** failed for data feeds that use OAuth2 client credentials authentication, such as the ServiceNow CMDB feed, because required authentication settings were not applied.
- Fixed an issue where the status of a User Access Review remediation ticket showed **Not Required** while the ticket was still being created. It now shows **In Progress**.
- Fixed an issue where a Workspace exported with **Export PDF** could have widgets running off the page or split across page breaks. Widgets now keep their arrangement and fit the page, charts are redrawn for the printed layout, and the **Global time range** control is left out of the PDF.
- Fixed an issue where the Exposure Management page was slow to open for tenants with many applications because it waited for all data to load before it was displayed.