# Kibana 9.3.1 Disabling message "New! Connect AutoOps to this self-managed cluster" **URL:** \ **Category:** Kibana\ **Tags:** autoops\ **Created:** [April 1, 2026, 7:02pm UTC](https://discuss.elastic.co/t/kibana-9-3-1-disabling-message-new-connect-autoops-to-this-self-managed-cluster/385736 "2026-04-01T19:02:43Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![kbujold\_wr](https://avatars.discourse-cdn.com/v4/letter/k/9fc29f/32.png) [@kbujold\_wr](https://discuss.elastic.co/u/kbujold_wr)\ **Post date:** [April 1, 2026, 7:02pm UTC](https://discuss.elastic.co/t/kibana-9-3-1-disabling-message-new-connect-autoops-to-this-self-managed-cluster/385736/1 "2026-04-01T19:02:44Z")
We would like to not present this message to our users. Is there a way this disable this? ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/4/24547b3cfa1810f7f4c5aae2c392974d82ce918c.png) ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [April 3, 2026, 10:37am UTC](https://discuss.elastic.co/t/kibana-9-3-1-disabling-message-new-connect-autoops-to-this-self-managed-cluster/385736/2 "2026-04-03T10:37:54Z")
You can hide **Stack Management** from the users by **hiding it using Spaces** : 1. Go to **Stack Management \> Kibana \> Spaces** 2. Open the relevant space 3. Disable the management features you do not want visible in that space Would that help? Do your users still need to see Stack Management? Otherwise, you can hide all announcements from the **Advanced Settings** : - **Global Settings** if you want to apply it everywhere - or **Space Settings** if you want it only for a specific space Like: ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/9/1954c0e91912aa5af6792126049c270ac43d3e0e.png) ---
**Author:** ![kbujold\_wr](https://avatars.discourse-cdn.com/v4/letter/k/9fc29f/32.png) [@kbujold\_wr](https://discuss.elastic.co/u/kbujold_wr)\ **Post date:** [April 7, 2026, 8:46pm UTC](https://discuss.elastic.co/t/kibana-9-3-1-disabling-message-new-connect-autoops-to-this-self-managed-cluster/385736/3 "2026-04-07T20:46:40Z")
> [@dadoonet](#): > > Global Settings No in Advance Settings setting the Space Settings “Hide announcements” to false does not disable this message. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [April 7, 2026, 9:02pm UTC](https://discuss.elastic.co/t/kibana-9-3-1-disabling-message-new-connect-autoops-to-this-self-managed-cluster/385736/4 "2026-04-07T21:02:12Z")
@val do you know why? ---
**Author:** ![kbujold\_wr](https://avatars.discourse-cdn.com/v4/letter/k/9fc29f/32.png) [@kbujold\_wr](https://discuss.elastic.co/u/kbujold_wr)\ **Post date:** [April 9, 2026, 1:09am UTC](https://discuss.elastic.co/t/kibana-9-3-1-disabling-message-new-connect-autoops-to-this-self-managed-cluster/385736/5 "2026-04-09T01:09:26Z")
Its also displayed on this page ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/7/e7ad849c1e8ffbb7a6c18d8ac3674bf6b2db0b68.png) ---
**Author:** ![willemdh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/willemdh/32/16922_2.png) [@willemdh](https://discuss.elastic.co/u/willemdh)\ **Post date:** [April 13, 2026, 6:57pm UTC](https://discuss.elastic.co/t/kibana-9-3-1-disabling-message-new-connect-autoops-to-this-self-managed-cluster/385736/6 "2026-04-13T18:57:24Z")
+1 for this question. Please @elastic all the popups and new feeds and publicity for beta and unwanted features are not really helpful and only distract and result in a lot of wasted time and questions from end users. Just recently I tried configuring `uiSettings.globalOverrides.hideAnnouncements` and `uiSettings.globalOverrides.hideAnnouncements` for an Elastic ECE deployment, but adding anyone of these in Users and Settings results in a Kibana no longer starting (9.3.2) ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/9/0975e4bd0cec3881a4df697372bc1690b97d9faf.png) ---
**Author:** ![val](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/val/32/138203_2.png) [@val](https://discuss.elastic.co/u/val)\ **Post date:** [April 14, 2026, 9:37am UTC](https://discuss.elastic.co/t/kibana-9-3-1-disabling-message-new-connect-autoops-to-this-self-managed-cluster/385736/7 "2026-04-14T09:37:41Z")
I owe you a 1000 apologies (or beers) for the slow response here, totally my fault. I went to the Kibana team and they shared that this popup shows up for self-managed (not air-gapped) clusters that don't already have AutoOps enabled, but that it isn't handled by the "Hide announcements" global setting. I've created this tracking issue > > > Relates to https://github.com/elastic/kibana/pull/246132 and https://github.com/…elastic/kibana/pull/236400 > > The new Cloud Connect promotion banners should be configurable to not appear for any users of a given Kibana environment. Right now, when X is clicked the banner disappears only for the user who clicked in that specific browser. > > Maybe this announcement could/should also be handled by the "Hide announcements" global setting. > > The \[reasons\](https://discuss.elastic.co/t/kibana-9-3-1-disabling-message-new-connect-autoops-to-this-self-managed-cluster/385736) brought forward were > \> the popups and new feeds and publicity for beta and unwanted features are not really helpful and only distract and result in a lot of wasted time and questions from end users. > > And > > \> We would like to not present this message to our users. Is there a way this disable this? ---
**Author:** ![willemdh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/willemdh/32/16922_2.png) [@willemdh](https://discuss.elastic.co/u/willemdh)\ **Post date:** [April 14, 2026, 5:23pm UTC](https://discuss.elastic.co/t/kibana-9-3-1-disabling-message-new-connect-autoops-to-this-self-managed-cluster/385736/8 "2026-04-14T17:23:10Z")
But the hideAnnouncement makes my Kibana 9.3.2 unable to start @val ---
**Author:** ![val](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/val/32/138203_2.png) [@val](https://discuss.elastic.co/u/val)\ **Post date:** [April 14, 2026, 6:21pm UTC](https://discuss.elastic.co/t/kibana-9-3-1-disabling-message-new-connect-autoops-to-this-self-managed-cluster/385736/9 "2026-04-14T18:21:34Z")
@willemdh I would definitely investigate this so if you can share more (HAR and/or browser console logs, etc), that would probably help pinpoint the issue. ---
**Author:** ![willemdh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/willemdh/32/16922_2.png) [@willemdh](https://discuss.elastic.co/u/willemdh)\ **Post date:** [April 14, 2026, 6:43pm UTC](https://discuss.elastic.co/t/kibana-9-3-1-disabling-message-new-connect-autoops-to-this-self-managed-cluster/385736/10 "2026-04-14T18:43:31Z")
Tx @val This is in ECE deployment Kibana Users and Settings. The setting is never applied an reverted automatically after clicking Save again. Not sure if a har would help here.. ---
**Author:** ![willemdh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/willemdh/32/16922_2.png) [@willemdh](https://discuss.elastic.co/u/willemdh)\ **Post date:** [April 14, 2026, 6:52pm UTC](https://discuss.elastic.co/t/kibana-9-3-1-disabling-message-new-connect-autoops-to-this-self-managed-cluster/385736/11 "2026-04-14T18:52:05Z")
![image](https://us1.discourse-cdn.com/elastic/original/3X/5/d/5daa6df6461028cb6a22282385a1d8642690df79.png) I was able to retrieve the error ---
**Author:** ![val](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/val/32/138203_2.png) [@val](https://discuss.elastic.co/u/val)\ **Post date:** [April 14, 2026, 7:34pm UTC](https://discuss.elastic.co/t/kibana-9-3-1-disabling-message-new-connect-autoops-to-this-self-managed-cluster/385736/12 "2026-04-14T19:34:01Z")
Thank you that helps. This is unrelated to the issue, though, it's a different bug that will require its own investigation, I'll take it with the ECE team, but from the first look of it, it looks like these two settings where [added recently](https://www.elastic.co/docs/release-notes/cloud-hosted#january-2026) to the allowlist for Kibana settings in ECH and might come soon to ECE (probably with the Kibana 9.4 stack pack) ---
**Author:** ![willemdh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/willemdh/32/16922_2.png) [@willemdh](https://discuss.elastic.co/u/willemdh)\ **Post date:** [April 15, 2026, 6:08am UTC](https://discuss.elastic.co/t/kibana-9-3-1-disabling-message-new-connect-autoops-to-this-self-managed-cluster/385736/13 "2026-04-15T06:08:18Z")
Thanks for this info. A bit unfortunate though that the documentation shows the ECE icon already and no mention of what version. This made me loose quite a bit of time again. ---
**Author:** ![val](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/val/32/138203_2.png) [@val](https://discuss.elastic.co/u/val)\ **Post date:** [April 15, 2026, 6:36am UTC](https://discuss.elastic.co/t/kibana-9-3-1-disabling-message-new-connect-autoops-to-this-self-managed-cluster/385736/14 "2026-04-15T06:36:49Z")
Can you point me at the page you're talking about so we can fix that? ---
**Author:** ![willemdh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/willemdh/32/16922_2.png) [@willemdh](https://discuss.elastic.co/u/willemdh)\ **Post date:** [April 16, 2026, 10:10am UTC](https://discuss.elastic.co/t/kibana-9-3-1-disabling-message-new-connect-autoops-to-this-self-managed-cluster/385736/15 "2026-04-16T10:10:01Z")
> [@willemdh](#): > > uiSettings.globalOverrides.hideAnnouncements > **[General settings in Kibana | Kibana](https://www.elastic.co/docs/reference/kibana/configuration-reference/general-settings)** ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/f/efb91cd4baeb4ea86555a2b308a119fa466f1896.png) Also please read [How to add xpack.encryptedSavedObjects.encryptionKey for Kibana deployments in ECE without breaking Fleet - #4 by willemdh](https://discuss.elastic.co/t/how-to-add-xpack-encryptedsavedobjects-encryptionkey-for-kibana-deployments-in-ece-without-breaking-fleet/385196/4) There the docs doesn't mention that encrypted saved objects is not supported. ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/f/2f5853048296ab34f039cbefbfd4b92b39843506.png) Best regards, Willem