---
title: Configure Graph
description: When a user saves a graph workspace in Kibana, it is stored in the .kibana index along with other saved objects like visualizations and dashboards. By...
url: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/explore-analyze/visualize/graph/graph-configuration
products:
  - Kibana
---

# Configure Graph
When a user saves a graph workspace in Kibana, it is stored in the `.kibana` index along with other saved objects like visualizations and dashboards. By default, both the configuration and data are saved for the workspace:
<definitions>
  <definition term="configuration">
    The selected data view, fields, colors, icons, and settings.
  </definition>
  <definition term="data">
    The visualized content (the vertices and connections displayed in the workspace).
  </definition>
</definitions>

The data in a saved workspace is like a report—it is a saved snapshot that potentially summarizes millions of raw documents. Once saved, these summaries are no longer controlled by security policies. Because the original documents might be deleted after a workspace is saved, there’s no practical basis for checking permissions for the data in a saved workspace.
For this reason, you can configure the save policy for graph workspaces to ensure appropriate handling of your data. You can allow all users to save only the configuration information for a graph, require all users to explicitly include the workspace data, or completely disable the ability to save a workspace.
For example, to disable the save option entirely, set `xpack.graph.savePolicy` to `none` in [`kibana.yml`](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/deploy-manage/stack-settings):
```yaml
xpack.graph.savePolicy: none
```

The supported save policies are:
<definitions>
  <definition term="none">
    Neither the configuration or data can be saved.
  </definition>
  <definition term="config">
    Only the configuration is saved.
  </definition>
  <definition term="configAndData">
    Both configuration and data are saved. This is the default policy.
  </definition>
  <definition term="configAndDataWithConsent">
    Only the configuration is saved unless the user explicitly selects the include data option.
  </definition>
</definitions>


## Use Security to grant access

You can also use security to grant read only or all access to different roles. When security is used to grant read only access, the following  indicator in Kibana is displayed. For more information on granting access to Kibana, see [Granting access to Kibana](https://docs-v3-preview.elastic.dev/elastic/elasticsearch/tree/main/reference/elasticsearch/roles).
![Example of Graph's read only access indicator in Kibana's header](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/explore-analyze/images/kibana-graph-read-only-badge.png)


## Disable drilldown configuration

By default, users can configure *drilldown* URLs to display additional information about a selected vertex in a new browser window. For example, you could configure a drilldown URL to perform a web search for the selected vertex term.
To prevent users from adding drilldown URLs,  set `xpack.graph.canEditDrillDownUrls` to `false` in [`kibana.yml`](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/deploy-manage/stack-settings):
```yaml
xpack.graph.canEditDrillDownUrls: false
```