# 2024.1.1

### Access Intelligence

#### Enhancements

* **EAC-30780**: For improved readability, dashboards now use a 2-column view when the *Duration* is one year.

#### Bug Fixes

* **EAC-30415**: Added an internal setting to optionally hide risk levels for query results, for improved performance when searching across large environments.

### Access Reviews

#### Enhancements

* **EAC-30805** Sign-off on rejected rows can now trigger Jira ticket creation using [orchestration actions](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications/destinations/jira.md).
* **EAC-30593**: Added support for sorting Certification results based on the contents of the *Summary Entities* column.

### Veza Integrations

#### Enhancements

* **EAC-30501 AWS**: The local user for AWS database discovery no longer needs to have the same username as the AWS IAM user configured for the AWS integration. Administrators can specify any `Redshift DB User`, `RDS MySQL DB User`, or `RDS PostgreSQL DB User` when configuring an AWS integration.
* **EAC-30162 Okta**: Added an option for authenticating with Okta using OAuth 2.0 client credentials (private keys), as an alternative to API tokens.
* **FR-1673 Salesforce**: Salesforce users now have the `department` attribute.

### Veza Platform

#### Enhancements

* **EAC-30199**: Access Intelligence: Non-root teams can now access the **Overview** page and **Analysis** section, restricted to integrations in the team scope.


---

# 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.veza.com/4yItIzMvkpAvMVFAamTf/release-notes/release-notes/archive/2024.1.1.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.