> ## Documentation Index
> Fetch the complete documentation index at: https://docs.honeycomb.io/llms.txt
> Use this file to discover all available pages before exploring further.

# What Restricted Users Can Do

> Find out what you can read, create, and edit in Honeycomb when your team restricts datasets you don't have access to

EntBeta

> [!NOTE]
>
> Dataset restrictions are in public [beta](https://docs.honeycomb.io/troubleshoot/product-lifecycle/release-stages.md#beta) on the [Honeycomb Enterprise plan](https://www.honeycomb.io/pricing/).

When a Team Owner restricts a dataset, only Team Owners and members of a user group with access can read its data.
If you can't read a dataset, Honeycomb shows it as locked or leaves its data out, so you know the data exists and what to ask for.
To get access, ask a Team Owner to add you to a user group that can read it.
To learn how restrictions work, visit [What are dataset restrictions?](https://docs.honeycomb.io/configure/teams/dataset-restrictions).

## What restricted users can read

When someone can't read a dataset, Honeycomb leaves its data out, or shows a locked state that names the dataset.
To get access, ask a Team Owner.

| Area | What happens |
| - | - |
| Dataset list | Restricted datasets appear locked. You can't open or query them. |
| Query Builder | Restricted datasets can't be selected. Field names and value suggestions come only from datasets you can read. |
| Environment-wide queries | The query runs on the datasets you can read. A banner shows how many datasets the query used and which it left out. If you can't read any dataset in the query, the query doesn't run. |
| Query results and Query History | Honeycomb checks your access when results load in Honeycomb. Results that include data you can't read appear locked. |
| Traces | Spans from restricted datasets appear as placeholders that keep the span's name, service, and timing but hide its fields. Select a placeholder to find out which dataset it comes from. |
| Service Map | The full map appears. Services and connections that include restricted data are marked. You can select them, but their span details aren't available. If you can't read any dataset in the environment, a restricted page appears instead of the map. |
| Boards | Panels that query a restricted dataset show a placeholder and don't run. Environment-wide panels show how many datasets they left out. Board filters on fields you can't read appear as **Hidden filter** and are kept when you save the board. SLO panels for SLOs you can't open appear locked, without their numbers or burn alert status. |
| BubbleUp | BubbleUp stays within the datasets the original query could read. |
| Triggers | Triggers that use data you can't read appear locked in the triggers list, without their query or status. You can't open them. |
| SLOs and burn alerts | SLOs that use data you can't read appear locked in the SLO list. You can't open them or their burn alerts. |
| Anomaly detection | Anomalies over datasets you can't read appear locked in the anomalies list, with their service, dataset, and status. You can't open them. |
| Calculated fields | Fields that exist only in restricted datasets aren't available to you. |
| API keys | You can't view an environment's API keys unless you can read every dataset in that environment. You can't view team-wide keys or the **API Keys** tab in Team Settings unless you can read every dataset on the team. |
| Activity Log | You can't query the Activity Log environment unless you can read every restricted dataset in your team's other environments, including S3 Archive environments. This applies in the Honeycomb UI and Honeycomb MCP, whatever your role. It doesn't apply to the Honeycomb API. |
| Honeycomb MCP and Canvas | Query, trace, and schema tools use only data you can read, and note when they left restricted data out. Agent conversations that used data you can't read appear locked. |
| Canvas investigations and Findings | You can open them even when they draw on data you can't read. Charts and query results in them stay locked, but their text can include restricted data. To learn more, visit [Limits and known limitations](https://docs.honeycomb.io/configure/teams/dataset-restrictions#limits-and-known-limitations). |

## What restricted users can create and edit

Restrictions also limit some changes, so people can't change resources built on data they can't read.

| Resource | What a restricted user can do |
| - | - |
| Dataset and environment restrictions, and user groups | Only Team Owners can change them. |
| Triggers | You can't create or edit a Trigger on a dataset you can't read. You can't create or edit an environment-wide Trigger unless you can read every dataset in the environment. You can't open, test, or delete a Trigger that uses data you can't read. |
| SLOs | You can't create, open, edit, or delete an SLO, or reset its budget, unless you can read every dataset it uses. This also applies through Honeycomb MCP. |
| Burn alerts | You can't create, edit, test, or delete a burn alert on an SLO you can't open. You can't add your own email address as a recipient of its burn alerts. |
| Boards | You can create, edit, and delete boards, change their settings and filters, and add query panels. You can't add a panel for an SLO you can't open. You can move or remove a locked SLO panel. |
| Calculated fields | You can't create or edit a calculated field on a dataset you can't read. You can create and edit environment calculated fields, but only with fields from datasets you can read. You can delete calculated fields. |
| Anomaly detection | You can't change the settings of an anomaly over a dataset you can't read. |
| Markers, query annotations, and saved queries | Restrictions don't limit these. |
| Dataset settings | You can't open the settings page of a dataset you can't read. |

## Next steps

To learn more about how your team controls access, visit these pages:

* [What are dataset restrictions?](https://docs.honeycomb.io/configure/teams/dataset-restrictions)
* [Manage Team Permissions](https://docs.honeycomb.io/configure/teams/manage-permissions.md)
