> 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/2026-march-22.md).

# March 22, 2026

Release notes

## ![](https://633303660-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMkiDTkdEK7CdyQX8KZZH%2Fuploads%2FyZbQZPuzHB6PbZKmN51t%2FSola-AI-Icon_.svg?alt=media\&token=fa9db6b1-f24b-4794-b41f-13c6173bdc4e) Sola AI&#x20;

### Voice chat with Sola AI

Talk to Sola without typing and get responses read aloud.<br>

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMkiDTkdEK7CdyQX8KZZH%2Fuploads%2Fe84sfKysLX6TYxlyxg1P%2FVoice%20mode%20.mp4?alt=media&token=a67c20c3-efbb-4c10-a575-9e610b60f147>" %}

<p align="center">Chat with Sola AI</p>
{% endembed %}

### Manage alert Slack notifications with Sola AI&#x20;

Sola AI can now create and edit Slack notifications for alert rules. Choose which channels or DMs to notify when a rule triggers or new evidence is discovered.

Send a test notification directly from the chat to confirm everything is set up correctly.

## Alerts

### Improved alert rule editing&#x20;

Fingerprint, grouping, and alert scope settings on existing [alert rules](https://docs.sola.security/workspace/projects/alerts.md#managing-alert-rules) can now be edited. Modifying these fields will deprecate existing triggered alerts and recalculate the rule to generate new alerts based on the updated configuration.

## Canvases

### Canvas widget focus mode&#x20;

Select any widget on your [canvas](#canvases) and run AI prompts that apply changes directly to it, without touching the rest of your canvas.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMkiDTkdEK7CdyQX8KZZH%2Fuploads%2FM62FRbRej6jS6AQaIa9Y%2FFocus%20mode.mp4?alt=media&token=56c35672-de2a-4d3f-9a14-17fb95a8d9b9>" %}

<p align="center">Canvas focus mode</p>
{% endembed %}

## Integrations

### Data Sources

***New*****: JumpCloud**

Unified directory and device management data including managed users, group memberships, device inventory, and system attributes.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMkiDTkdEK7CdyQX8KZZH%2Fuploads%2FNjqX5xIjDbwmXam6nA4A%2FJumpCloud%20data%20source.mp4?alt=media&token=3c2cebcc-52cc-4f8a-b445-9af5d3f7a299>" %}

***Improved*****: Okta service account connection**

Okta can now be connected using a service account for a more secure, least-privilege setup.

***Improved*****: Table-level sync status**

Previously, a single failed data source entity would mark an entire table as out of sync with no data. Now, only the problematic entities are skipped while the rest of your data continues syncing normally. A new Partial Sync status makes this visible, and you can drill into any table to see exactly which entities failed and why.

## New Templates

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

* [Azure Security Posture Rule Set](https://sola.security/app/azure-security-posture/)
* [GitHub and Google Workspace - App Monitoring](https://sola.security/app/github-app-oauth-app-security/)

## 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/2026-march-22.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.
