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