# Now available: Search Guard FLX 1.1.0

**URL:** <https://forum.search-guard.com/t/now-available-search-guard-flx-1-1-0/2378>\
**Category:** Announcements\
**Created:** [December 9, 2022, 8:45am UTC](https://forum.search-guard.com/t/now-available-search-guard-flx-1-1-0/2378 "2022-12-09T08:45:20Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![searchguard](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/searchguard/32/1830_2.png) [@searchguard](https://forum.search-guard.com/u/searchguard)\
**Post date:** [December 9, 2022, 8:45am UTC](https://forum.search-guard.com/t/now-available-search-guard-flx-1-1-0/2378/1 "2022-12-09T08:45:20Z")

</div>

Today, we are happy to announce the first minor update release of Search Guard FLX. Search Guard FLX 1.1.0 brings a number of enhancements for Signals and many bugfixes:

**[Unacknowledgeable actions](https://docs.search-guard.com/latest/elasticsearch-alerting-throttling#unacklowledgabe-actions)**

In some cases, you might want certain actions of a watch to execute every time - even if the watch got acknowledged before. Signals now supports a new boolean attribute for actions: `ack_enabled`. By default, the attribute is `true`. If you set the attribute to `false`, this action will be no longer acknowledged when you acknowledge a watch. You can also not directly acknowledge the action.

**[Landing page for acknowledging actions](https://docs.search-guard.com/latest/elasticsearch-alerting-throttling#kibana-deeplinks-for-acknowledging-actions)**

You can now add a direct link for acknowledging an action to any notification sent by Signals. You just have to add the expression `{{ack_watch_link}}` or `{{ack_action_link}}` to any notification message template used in Signals actions. `{{ack_watch_link}}` lets you acknowledge the whole watch; `{{ack_action_link}}` lets you acknowledge just the action which triggered the notification.

**Bugfixes**

The release contains bugfixes regarding:

- DLS
- Privilege issues with index `.search_guard_resource_owner_service`
- sgctl set and sgctl migrate
- Multi-Tenancy
- The configuration `sg_auth_token_service`
- And many more

You can find the full changelogs here:

- [**Search Guard FLX 1.1.0 changelogs**](https://docs.search-guard.com/latest/changelog-searchguard-flx-1_1_0)

You can find all versions here:

[Search Guard Version Matrix](https://docs.search-guard.com/latest/search-guard-versions)

As always, we appreciate your feedback, questions, and feature requests here on the forum.

By the way, the GA version of Search Guard FLX for ES 8 is following soon.

Many greetings from the Search Guard team

Search Guard (®) is an Elasticsearch plugin that offers encryption, authentication, and authorization.

Coded with love in Berlin, Denmark, Sweden, Italy, Ukraine and the US.

Search Guard is a trademark of floragunn GmbH, registered in the U.S. and in other countries.

Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries.

---

_[View the full topic](https://forum.search-guard.com/t/now-available-search-guard-flx-1-1-0/2378)._