be765767ee
* update spaces images * add Spaces FC section * Updates for kibana authorization section * update plugin development guide * start adding docs * remove unused description field from Feature Registry interface * Update role management API documentation * Apply suggestions from code review Thanks, Gail! Co-Authored-By: legrego <lgregorydev@gmail.com> * Update docs/api/role-management/put.asciidoc * update kibana privileges section intro * relocate link to Role Management API * update PUT role docs to align with ES * indicate that base and feature privileges cannot be used at the same time * restructure kibana privileges section * add UI and API examples to Kibana Privileges section * Apply suggestions from code review Co-Authored-By: legrego <lgregorydev@gmail.com> * address PR feedback * Apply suggestions from code review Co-Authored-By: legrego <lgregorydev@gmail.com> * Apply suggestions from code review Co-Authored-By: legrego <lgregorydev@gmail.com> * address pr feedback * Update docs/api/role-management/put.asciidoc Co-Authored-By: gchaps <33642766+gchaps@users.noreply.github.com> * Update docs/security/index.asciidoc Co-Authored-By: gchaps <33642766+gchaps@users.noreply.github.com> * address PR feedback * fix merge from master * Update docs/spaces/managing-spaces.asciidoc Co-Authored-By: gchaps <33642766+gchaps@users.noreply.github.com>
35 lines
1.6 KiB
Plaintext
35 lines
1.6 KiB
Plaintext
[role="xpack"]
|
||
[[spaces-managing]]
|
||
=== Managing spaces
|
||
You can manage spaces from the **Management > Spaces** page. Here you can create, edit, and delete your spaces.
|
||
|
||
[NOTE]
|
||
{kib} has an <<spaces-api, experimental API>> if you want to create your spaces programatically.
|
||
|
||
[role="screenshot"]
|
||
image::spaces/images/space-management.png["Space Management"]
|
||
|
||
==== Creating and updating spaces
|
||
You can create as many spaces as you like, but each space must have a unique space identifier. The space identifier is a short string of text that is part of the {kib} URL when you are inside that space. {kib} automatically suggests a space identifier based on the name of your space, but you are free to customize this to your liking.
|
||
|
||
[NOTE]
|
||
You cannot change the space identifier once the space is created.
|
||
|
||
[role="screenshot"]
|
||
image::spaces/images/edit-space.png["Updating a space"]
|
||
|
||
==== Controlling feature visibility
|
||
You can control which {kib} features are visible in each space. For example, you can hide “Dev Tools” in your “Executive” space, if users of that space don’t need this feature.
|
||
|
||
[role="screenshot"]
|
||
image::spaces/images/edit-space-feature-visibility.png["Controlling features visiblity"]
|
||
|
||
|
||
NOTE: This is not considered a security feature. If you wish to secure access to specific features on a per-user basis, then you need to configure <<xpack-security-authorization, Kibana Security>>.
|
||
|
||
==== Deleting spaces
|
||
Deleting a space is a destructive operation, which cannot be undone. When you delete a space, all of the saved objects that belong to that space are also deleted.
|
||
|
||
[role="screenshot"]
|
||
image::spaces/images/delete-space.png["Deleting a space"]
|