# Features / Improvements & Fixes

## HQ

### New features

* LRN UX for HQ IAM. 
  * See & copy the LRN of an IAM resource (User, Group, Service Account, Role).
  * LRN is also an available column in all IAM listing pages. You can enable it in the column selector of the table.
* Environments + metrics columns.
* Tables UX update: **powerful grid**
  * Multi sort
  * Reorder of columns + column selection
  * Filters
  * Preferences are saved for the user
  * CLI
    * Provide shell completion for agent --env flag

### Improvements

* IAM - Updated permissions syntax.
  * **Renaming**. Some services and resources have been renamed. This is to simplify and make the IAM model more consistent. You can find the [latest spec here](/latest/devx/6.0/user-guide/iam/iam-reference.md). You may need to adjust your policy YAML definitions. Reach out to us if you need help.
  * **Prefix/infix wildcard support**. You can now use `*` in a prefix or infix position for resource-id path segments. Use this to express things like *"environments that end in  -dev"* (`*-dev`) or *"topics whose name starts with fraud and ends with analytics"*  (`fraud*analytics`).
* Improved Global SQL studio UX
  * Topic navigator IDE experience.
  * See latest topic messages by default, ordered by time, with latest messages 1st.
* Dark mode for sign-in page

### Fixes

* User Profile page now correctly save changes.

## Agent

### New features

* Expose Agent dashboard metrics via API.

### Improvements

* Improved Agent-level navigation bar.

### Fixes

*


---

# Agent Instructions: 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:

```
GET https://docs.lenses.io/latest/devx/6.0/changelog/lenses-hq/version-6.0.0-alpha.17/features-improvements-and-fixes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.