Kibana Spaces: Partitioning Dashboards and Saved Objects for Team‑Specific Workflows

Why Your Team Needs a Logical Namespace in Kibana

When a single Kibana cluster hosts dashboards for marketing, finance, and operations, the UI can become a maze. Users often click through dozens of unrelated visualizations, and accidental edits become a risk. The problem is not data isolation—index‑level security handles that—but visibility and discoverability. Kibana Spaces solve this by grouping saved objects into logical namespaces that appear as separate “spaces” in the UI.

What Are Kibana Spaces?

A Space is a lightweight container that scopes dashboards, visualizations, searches, and index patterns. Each space gets a unique URL prefix (e.g., /s/marketing/), and the Kibana UI shows a space selector allowing users to switch contexts. Spaces do not provide a security boundary; they only hide objects you don’t want to expose. Security still relies on Elastic Security roles that grant or deny access to spaces.

When to Use Spaces – Practical Use Cases

• Team‑Specific Dashboards: Marketing has a Campaign Performance dashboard, Finance has Financial Health, and each team should not see the other’s dashboards.
• Environment Segmentation: Separate Dev and Prod dashboards in the same cluster to avoid accidental edits in production.
• Feature Roll‑Out: A new monitoring dashboard can live in a Beta space until the feature is fully released.
• Temporary Projects: Create a space for a short‑term audit or compliance review and delete it afterward.

Setting Up a Space – Step‑by‑Step Example

Below is a concrete workflow for creating a Marketing space, adding a dashboard, and verifying isolation. All actions are performed through the Kibana web UI; no CLI is required.

1. Navigate to Stack Management → Spaces.
   • Click Create space and fill in:
     • Name: Marketing
     • URL prefix: marketing
     • Description: Dashboards for marketing analytics.
   • Save the space.
2. Switch to the new space using the space selector in the top‑left corner.
3. Create a dashboard:
   • Open Dashboard → Create new dashboard.
   • Add a few visualizations (e.g., a bar chart on clicks).
   • Save with the name Marketing Campaign Overview.
4. Verify isolation:
   • Log out and log in as a user without Marketing privileges.
   • Open the space selector; the Marketing space should be missing.
   • Navigate to /s/marketing/ directly – you should see an access denied page.
5. Assign permissions:
   • In Stack Management → Security → Roles, create a role marketing_reader.
     • Under Kibana spaces add marketing with read privilege.
     • Optionally add read on specific index patterns.
   • Create a user alice and bind the role.
   • Log in as alice to confirm she sees only the Marketing space and its dashboard.

Exporting & Importing Between Spaces

When you need to move a dashboard from Marketing to a new Beta space, use Stack Management’s Saved Objects feature. The process preserves visualizations and searches, but you must ensure dependencies are included.

1. Export from Marketing:
   • Go to Stack Management → Saved Objects.
   • Filter by Space: Marketing and select the dashboard.
   • Click Export → choose Export as JSON and download the file.
2. Import into Beta:
   • Switch to the Beta space via the selector.
   • Open Saved Objects → Import, upload the JSON file.
   • When prompted, map any missing index patterns to existing ones or create new ones.
   • Confirm the import; the dashboard should appear in Beta.
3. Verify dependencies:
   • Open the imported dashboard; if any visualizations show “Data source not found”, you need to recreate or map the missing index pattern.
   • Check that the search objects referenced by the dashboard are present in Beta; otherwise, re‑create them.

Limitations & Trade‑Offs

• Not a security boundary: Spaces only hide objects; they do not prevent a privileged user from accessing underlying indices. Combine with index‑level security for sensitive data.
• Dependency gaps: Exporting a dashboard does not automatically bring in the underlying index patterns or saved searches. Manual mapping is required.
• Plugin compatibility: Some third‑party Kibana plugins do not respect space prefixes. Test in a non‑production space before rolling out.
• Version differences: Role names and privilege scopes can change between Kibana releases. Always review the release notes for your version.

Practical Checklist Before Going Live

Step	What to Verify
Space creation	URL prefix is unique and non‑conflicting.
Role binding	Users see only allowed spaces; others cannot access via direct URL.
Export/Import	All dependent objects exist in target space; visualizations render correctly.
Security overlap	Index‑level security matches space visibility for sensitive data.
Plugin behavior	Custom apps respect space boundaries in the test environment.

Actionable Takeaway

Use Kibana Spaces when you need to give teams a clean, isolated view of dashboards and searches without spinning up separate clusters. Remember that spaces are a UI convenience, not a security boundary. Pair them with Elastic Security roles, verify dependencies on export/import, and test any custom plugins in a non‑production space before deployment. Once set up, the space selector becomes a powerful navigation tool that keeps your Kibana cluster tidy and your users productive.