-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide config option to hide Console #7466
Comments
Somewhat related to #7334. If we did this, I think we'd want to handle it for all (or most) apps rather than make Console a special case. Another frequent ask is for the ability to hide the settings app from some users, but that gets into view level security which is even more hairy. In any case, I can see the value in this functionality, but it might require some discussion to figure out the right solution. |
I want use Kibana to illustrate and inform customers. If we can lock down access so everyone gets the same experience all the time. |
I've had various customers ask about this as well. Will this be making it into v5? |
Console will go under devtools in 5.0 if #8171 gets merged today. I don't think the ability to turn devtools sections on/off is a feature yet, is that right @lukasolson? |
Can you not add |
Sorry @lukasolson, I was not aware there was now a Perhaps should add it to the docs page for Console? I'd be happy to adjust the docs if you would like. |
That'd be great. Thanks! |
TIL. Sorry for the confusion guys, I wasn't aware of this option either. |
To help address #7466 add documentation about the `console.enabled` option for those that would like disable console entirely
Quick doc update at #8250 |
Since console can be disabled, I'm going to close this. I also created #9165 to track making dev tools disappear automatically if all individual dev tools are disabled. |
There doesn't seem to be a way to hide the Console in Kibana 5.0.0 alpha 3. It'd be great if there was a config flag in the settings or the kibana.yml to hide the Console from showing up in the sidebar to prevent unintended use (e.g. non-technical users).
The text was updated successfully, but these errors were encountered: