Immutable Space features

[kobelb]

Problem

Currently, when creating a Space you're able to choose which which features should be disabled:

As new features are added to Kibana, or plugins are installed, they automatically become available within the Space. It should be noted that when using security and choosing the custom feature privileges option, new features are not automatically available to end-users.

Solution

When creating a Space, the user should be able to choose to make the selected features "immutable" so new features don't automatically become available within the Space.

[elasticmachine]

Pinging @elastic/kibana-security

[jinmu03]

Or add a "there is a new feature" notice in Spaces privileges configuration page allowing administrator to easily disable it or grant read or all privileges to it.

[kobelb]

@jinmu03 we've been discussing this more-so from the security perspective in #35865 and #38301. It's debatable whether or not this is required if we add the "privilege sets"

[legrego]

This issue is quite old, and inactive. Since this was originally written, Kibana has been reorganized around "Solutions", and the Spaces UI has been updated accordingly. While we still expose new features by default, I don't believe this has been an issue for our users in practice.

I'm going to close this issue for now, but feel free to reopen if anyone would like to continue the discussion.