Skip to content

Latest commit

 

History

History
137 lines (89 loc) · 6.8 KB

manage-spaces.md

File metadata and controls

137 lines (89 loc) · 6.8 KB
applies_to mapped_pages
stack serverless
ga
ga

Spaces [xpack-spaces]

Spaces let you organize your content and users according to your needs.

  • Each space has its own saved objects.
  • Users can only access 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.
  • In {{stack}} deployments on version 8.16 and later, each space has its own navigation, called solution view.

{{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.

:::{image} /deploy-manage/images/kibana-change-space.png :alt: Change current space menu :screenshot: :::

To go to Spaces, find Stack Management in the navigation menu or use the global search bar.

Required permissions [_required_privileges_3]

  • Serverless projects: Admin role or equivalent
  • {{stack}} deployments: kibana_admin or equivalent

Create a space [spaces-managing]

The maximum number of spaces that you can have differs by deployment type:

  • Serverless projects: Maximum of 100 spaces.
  • {{stack}} deployments: Controlled by the xpack.spaces.maxSpaces setting. Default is 1000. View the full list of Space settings.

To create a space:

:::::{tab-set} :group: stack-serverless

::::{tab-item} {{serverless-short}} :sync: serverless

  1. Click Create space or select the space you want to edit.

  2. Provide:

    • A meaningful name and description for the space.
    • 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.

  3. Customize the avatar of the space to your liking.

  4. Save the space. ::::

::::{tab-item} {{stack}} :sync: stack

  1. Select Create space and provide a name, description, and URL identifier. 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.

  2. Select a Solution view. This setting controls the navigation that all users of the space will get:

    • Search: A light navigation menu focused on analytics and Search use cases. Features specific to Observability and Security are hidden.
    • Observability: A light navigation menu focused on analytics and Observability use cases. Features specific to Search and Security are hidden.
    • Security: A light navigation menu focused on analytics and Security use cases. Features specific to Observability and Search are hidden.
    • Classic: All features from all solutions are visible by default using the classic, multilayered navigation menus. You can customize which features are visible individually.

  3. If you selected the Classic solution view, you can customize the Feature visibility as you need it to be for that space.

    :::{note} 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. :::

  4. Customize the avatar of the space to your liking.

  5. Save your new space by selecting Create space. ::::

:::::

You can edit all of the space settings you just defined at any time, except for the URL identifier.

Elastic also allows you to manage spaces using APIs:

Define access to a space [spaces-control-user-access]

stack: ga
serverless:
  elasticsearch: ga
  security: ga
  observability: unavailable

Users can access spaces based on the roles that they have.

  • 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.
  • 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.

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.

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.

Delete a space [_delete_a_space]

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.

Move saved objects between spaces [spaces-moving-objects]

To move saved objects between spaces, you can copy objects, or export and import objects.

Configure a space-level landing page [spaces-default-route]

stack: ga
serverless: unavailable

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.

To configure the landing page, use the default route setting in Stack Management > {{kib}} > Advanced settings. For example, you might set the default route to /app/dashboards.

:::{image} /deploy-manage/images/kibana-spaces-configure-landing-page.png :alt: Configure space-level landing page :screenshot: :::