mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 09:19:04 -04:00
# Backport This will backport the following commits from `main` to `8.12`: - [Clarify spaces documentation (#173866)](https://github.com/elastic/kibana/pull/173866) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Larry Gregory","email":"larry.gregory@elastic.co"},"sourceCommit":{"committedDate":"2023-12-21T19:33:53Z","message":"Clarify spaces documentation (#173866)\n\nClarifies language for securing access to spaces.","sha":"d76e059173f8e20047b238a47dc61c93335dbb88","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","docs","backport:all-open","v8.13.0"],"number":173866,"url":"https://github.com/elastic/kibana/pull/173866","mergeCommit":{"message":"Clarify spaces documentation (#173866)\n\nClarifies language for securing access to spaces.","sha":"d76e059173f8e20047b238a47dc61c93335dbb88"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/173866","number":173866,"mergeCommit":{"message":"Clarify spaces documentation (#173866)\n\nClarifies language for securing access to spaces.","sha":"d76e059173f8e20047b238a47dc61c93335dbb88"}}]}] BACKPORT--> Co-authored-by: Larry Gregory <larry.gregory@elastic.co>
This commit is contained in:
parent
a599b3168e
commit
2bef2a5152
1 changed files with 1 additions and 1 deletions
|
@ -11,7 +11,7 @@ This guide introduces you to three of {kib}'s security features: spaces, roles,
|
|||
[float]
|
||||
=== Spaces
|
||||
|
||||
Do you have multiple teams or tenants using {kib}? Do you want a “playground” to experiment with new visualizations or rules? If so, then <<xpack-spaces,{kib} Spaces>> can help.
|
||||
Do you have multiple teams using {kib}? Do you want a “playground” to experiment with new visualizations or rules? If so, then <<xpack-spaces,{kib} Spaces>> can help.
|
||||
|
||||
Think of a space as another instance of {kib}. A space allows you to organize your <<dashboard, dashboards>>, <<alerting-getting-started, rules>>, <<xpack-ml, machine learning jobs>>, and much more into their own categories. For example, you might have a Marketing space for your marketeers to track the results of their campaigns, and an Engineering space for your developers to {apm-guide-ref}/apm-overview.html[monitor application performance].
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue