Skip to content

Commit b98194a

Browse files
florent-leborgneflorent-leborgne
committed
tests
1 parent 34e9aa4 commit b98194a

File tree

2 files changed

+181
-0
lines changed

2 files changed

+181
-0
lines changed

‎deploy-manage/manage-spaces-new.md‎

Lines changed: 180 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,180 @@
1+
---
2+
mapped_pages:
3+
- https://www.elastic.co/guide/en/kibana/current/xpack-spaces.html
4+
- https://www.elastic.co/guide/en/serverless/current/spaces.html
5+
applies_to:
6+
serverless: ga
7+
deployment:
8+
ess: ga
9+
self: ga
10+
ece: ga
11+
eck: ga
12+
products:
13+
- id: kibana
14+
- id: cloud-serverless
15+
---
16+
17+
# Spaces [xpack-spaces]
18+
19+
**Spaces** let you organize your content and users according to your needs.
20+
21+
- Each space has its own saved objects.
22+
- Users can access only the spaces that they have been granted access to. This access is based on user roles, and a given role can have different permissions per space.
23+
- {applies_to}`stack: ga 9.0` **Only**. Each space has its own solution-oriented navigation, called solution view.
24+
25+
{{kib}} creates a default space for you. When you create more spaces, users are asked to choose a space when they log in, and can change their current space at any time from the top menu.
26+
27+
:::{image} /deploy-manage/images/kibana-change-space.png
28+
:alt: Change current space menu
29+
:screenshot:
30+
:::
31+
32+
You can find the **Spaces** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
33+
34+
For more info on working with spaces, check out:
35+
- [Create a space](#spaces-managing)
36+
- [Define access to a space](#spaces-control-user-access)
37+
- [Move saved objects between spaces](#spaces-moving-objects)
38+
- [Configure a space-level landing page](#spaces-default-route)
39+
- [Delete a space](#_delete_a_space)
40+
41+
Check out [Using Spaces with Fleet](/deploy-manage/manage-spaces-fleet.md) for info on using spaces with {{fleet}} in a space-aware data model.
42+
43+
## Required permissions [_required_privileges_3]
44+
45+
:::::{tab-set}
46+
:group: stack-serverless
47+
48+
::::{tab-item} Elastic {{serverless-short}}
49+
:sync: serverless
50+
`Admin` role or equivalent
51+
::::
52+
53+
::::{tab-item} Elastic 9.0+
54+
:sync: stack
55+
`kibana_admin` or equivalent
56+
::::
57+
58+
:::::
59+
60+
61+
## Create a space [spaces-managing]
62+
63+
The maximum number of spaces that you can have differs by deployment type:
64+
65+
:::::{tab-set}
66+
:group: stack-serverless
67+
68+
::::{tab-item} Elastic {{serverless-short}}
69+
:sync: serverless
70+
Maximum of 100 spaces.
71+
::::
72+
73+
::::{tab-item} Elastic 9.0+
74+
:sync: stack
75+
Controlled by the `xpack.spaces.maxSpaces` setting. Default is 1000. View the [full list of Space settings](kibana://reference/configuration-reference/spaces-settings.md).
76+
::::
77+
78+
:::::
79+
80+
To create a space:
81+
82+
:::::{tab-set}
83+
:group: stack-serverless
84+
85+
::::{tab-item} Elastic {{serverless-short}}
86+
:sync: serverless
87+
88+
1. Click **Create space** or select the space you want to edit.
89+
2. Provide:
90+
91+
* A meaningful name and description for the space.
92+
* A URL identifier. The URL identifier is a short text string that becomes part of the {{kib}} URL. {{kib}} suggests a URL identifier based on the name of your space, but you can customize the identifier to your liking. You cannot change the space identifier later.
93+
94+
3. Customize the avatar of the space to your liking.
95+
4. Save the space.
96+
::::
97+
98+
::::{tab-item} Elastic 9.0+
99+
:sync: stack
100+
101+
1. Select **Create space** and provide a name, description, and URL identifier.
102+
The URL identifier is a short text string that becomes part of the {{kib}} URL when you are inside that space. {{kib}} suggests a URL identifier based on the name of your space, but you can customize the identifier to your liking. You cannot change the space identifier once you create the space.
103+
104+
2. Select a **Solution view**. This setting controls the navigation that all users of the space will get:
105+
* **Search**: A light navigation menu focused on analytics and Search use cases. Features specific to Observability and Security are hidden.
106+
* **Observability**: A light navigation menu focused on analytics and Observability use cases. Features specific to Search and Security are hidden.
107+
* **Security**: A light navigation menu focused on analytics and Security use cases. Features specific to Observability and Search are hidden.
108+
* **Classic**: All features from all solutions are visible by default using the classic, multilayered navigation menus. You can customize which features are visible individually.
109+
110+
3. If you selected the **Classic** solution view, you can customize the **Feature visibility** as you need it to be for that space.
111+
112+
:::{note}
113+
Even when disabled in this menu, some Management features can remain visible to some users depending on their privileges. Additionally, controlling feature visibility is not a security feature. To secure access to specific features on a per-user basis, you must configure [{{kib}} Security](elasticsearch://reference/elasticsearch/roles.md).
114+
:::
115+
116+
4. Customize the avatar of the space to your liking.
117+
5. Save your new space by selecting **Create space**.
118+
::::
119+
120+
:::::
121+
122+
You can edit all of the space settings you just defined at any time, except for the URL identifier.
123+
124+
Elastic also allows you to manage spaces using APIs:
125+
126+
127+
* {applies_to}`serverless:` [Spaces API](https://www.elastic.co/docs/api/doc/serverless/operation/operation-get-spaces-space)
128+
* {applies_to}`stack: ga 9.0` [Spaces API](https://www.elastic.co/docs/api/doc/kibana/operation/operation-post-spaces-copy-saved-objects)
129+
130+
131+
## Define access to a space [spaces-control-user-access]
132+
133+
Users can access spaces based on the roles that they have.
134+
135+
* Certain reserved roles can view and access all spaces by default. You can’t prevent those roles from accessing a space. Instead, you can grant different roles to your users.
136+
* When creating or editing a role, you can define which existing spaces that role can access, and with which permissions. Role management differs between {{stack}} deployments and serverless projects.
137+
- {applies_to}`serverless:` check [Custom roles](/deploy-manage/users-roles/cloud-organization/user-roles.md).
138+
- {applies_to}`stack: ga 9.0` check [Creating or editing a role](/deploy-manage/users-roles/cluster-or-deployment-auth/defining-roles.md).
139+
140+
141+
If you're managing an {{stack}} deployment, then you can also assign roles and define permissions for a space from the **Permissions** tab of the space settings.
142+
143+
When a role is assigned to *All Spaces*, you can’t remove its access from the space settings. You must instead edit the role to give it more granular access to individual spaces.
144+
145+
146+
## Move saved objects between spaces [spaces-moving-objects]
147+
148+
To move saved objects between spaces, you can [copy objects](/explore-analyze/find-and-organize/saved-objects.md#managing-saved-objects-copy-to-space), or [export and import objects](/explore-analyze/find-and-organize/saved-objects.md#managing-saved-objects-export-objects).
149+
150+
151+
## Configure a space-level landing page [spaces-default-route]
152+
153+
:::::{tab-set}
154+
:group: stack-serverless
155+
156+
::::{tab-item} Elastic {{serverless-short}}
157+
:sync: serverless
158+
This is not available on Elastic Serverless.
159+
::::
160+
161+
::::{tab-item} Elastic 9.0+
162+
:sync: stack
163+
You can create a custom experience for users by configuring the {{kib}} landing page on a per-space basis. The landing page can route users to a specific dashboard, application, or saved object as they enter each space.
164+
165+
To configure the landing page, use the default route setting in the [{{kib}} advanced settings](kibana://reference/advanced-settings.md#kibana-general-settings). For example, you might set the default route to `/app/dashboards`.
166+
167+
You can access the **Advanced Settings** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
168+
169+
:::{image} /deploy-manage/images/kibana-spaces-configure-landing-page.png
170+
:alt: Configure space-level landing page
171+
:screenshot:
172+
:::
173+
::::
174+
175+
:::::
176+
177+
178+
## Delete a space [_delete_a_space]
179+
180+
Deleting a space permanently removes the space and all of its contents. Find the space on the **Spaces** overview page and click the trash icon in the Actions column. You can’t delete the default space, but you can customize it to your liking.

‎deploy-manage/toc.yml‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -622,6 +622,7 @@ toc:
622622
- file: users-roles/cluster-or-deployment-auth/authorization-plugins.md
623623
- file: users-roles/cluster-or-deployment-auth/controlling-access-at-document-field-level.md
624624
- file: users-roles/cluster-or-deployment-auth/submitting-requests-on-behalf-of-other-users.md
625+
- file: manage-spaces-new.md
625626
- file: manage-spaces.md
626627
children:
627628
- file: manage-spaces-fleet.md

0 commit comments

Comments
 (0)