> For the complete documentation index, see [llms.txt](https://docs.e6data.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/product-documentation/release-notes-and-updates/21st-august-2023.md).

# 21st August 2023

## Summary

The 21st August 2023 release of e6data includes the following features & enhancements:

* [Separate Query Editor Viewer Role](#separate-query-editor-viewer-role)
* [Query Resume in Query Editor](#query-resume-in-query-editor)
* [Customizing Query Editor View](#customizing-query-history-view)
* [Adding the Ability to Edit Catalogs](#adding-the-ability-to-edit-catalogs)
* [Adding Ability to Provision External Access to Clusters](#adding-ability-to-provision-external-access-to-clusters)

## Usage Notes

No user action is required to access the features in this release.

## Separate Query Editor Viewer Role

For improved security, the QueryEditorViewer role has been separated. This allows Admins to provide Query Editor access to only specified users or groups.

Query Editor access will not be provided to any roles by default, including SuperAdmin & AccessAdmins.

## Query Resume in Query Editor

If a user tries to run a query using a suspended cluster, they will be prompted for consent to resume the cluster prior to executing the query.

## Customizing Query History View

Users can now edit the columns displayed in Query History to suit their requirements. The edited view will be automatically saved and shown in during each session.

## Adding the Ability to Edit Catalogs

Existing catalogs can be edited to select/deselect the schemas that should be used.

## Adding Ability to Provision External Access to Clusters

Users can now enable external access to clusters directly from the e6data Console.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.e6data.com/product-documentation/release-notes-and-updates/21st-august-2023.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.