> For the complete documentation index, see [llms.txt](https://docs.sola.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sola.security/getting-started/release-notes/2025-december-31.md).

# December 31, 2025

Release notes

Happy new year! :tada:

## Pricing and plans

Choose the plan that fits your team with new pricing tiers designed to scale with your security needs.&#x20;

Upgrade instantly through self-service options, manage your subscription flexibly, and get clear visibility into feature entitlements and usage limits across Free, Individual, Team, and Enterprise plans.

## Workflows

### Manual workflow actions

Build and edit workflows without AI assistance. New hover actions let you manually create, duplicate, delete, and configure workflow blocks, attach and delete edges, giving you complete control over your automation logic.&#x20;

<figure><img src="https://633303660-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMkiDTkdEK7CdyQX8KZZH%2Fuploads%2FzyD1L0nWwzr4kbTpXamJ%2FBuild%20workflows%20manually%20with%20full%20control.svg?alt=media&amp;token=d33dfb32-3f06-4db6-8e54-e12074ce84f1" alt="Build workflows manually with full control"><figcaption><p>Build workflows manually with full control</p></figcaption></figure>

### Workflows Send Email block action

Workflows can now send automated, customizable emails, including output from previous workflow steps, making it easier to share reports and results with stakeholders.

<figure><img src="https://633303660-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMkiDTkdEK7CdyQX8KZZH%2Fuploads%2FbHkn4WVZTGyjaGpRcprf%2FSend%20automated%20emails%20from%20your%20workflows.svg?alt=media&amp;token=f5c23e71-2bdc-4dd8-846e-d3fce9c5604c" alt=""><figcaption><p>Send automated emails from your workflows</p></figcaption></figure>

### Enable/disable workflows

Control which workflows are actively running with a simple toggle. Temporarily disable workflows for testing or maintenance, then turn them back on when ready.

<figure><img src="https://633303660-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMkiDTkdEK7CdyQX8KZZH%2Fuploads%2FszeIf0VY2SlOuqAbgljH%2FEnable%20and%20disable%20workflows.svg?alt=media&amp;token=88ebf7e8-ac4d-4d37-b169-e059b2c4d087" alt="Enable and disable workflows"><figcaption><p>Enable and disable workflows</p></figcaption></figure>

## Integrations

<figure><img src="https://633303660-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMkiDTkdEK7CdyQX8KZZH%2Fuploads%2F5xv0kySshaHnCWptYs6a%2Fhibob_banner.svg?alt=media&amp;token=03cf9979-6e77-4dde-9cdd-5dd9609b5cde" alt=""><figcaption></figcaption></figure>

### Data Sources

#### Data Sources

***New*****: HiBob**

Connect HiBob to bring employee context into your security workflows. Use data such as departments, titles, and employment status to strengthen identity reviews, validate access, and improve overall organizational visibility.

## New Templates

Now available in [Templates](https://docs.sola.security/getting-started/templates.md):

* [GitHub - React CVE-2025-55182 Analyzer](https://sola.security/app/github-react-cve-2025-55182-analyzer/)

{% embed url="<https://sola.security/blog/shai-hulud-supply-chain-attack-nov-24/>" %}

## Notes and reminders

Stay tuned for more coming soon! 🚀

—

*The Sola Team*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sola.security/getting-started/release-notes/2025-december-31.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
