> For the complete documentation index, see [llms.txt](https://docs.veza.com/4yItIzMvkpAvMVFAamTf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veza.com/4yItIzMvkpAvMVFAamTf/release-notes/release-notes/archive/2023.6.12.md). # 2023.6.12 Changes in Veza release v2023.6.12 ### Integrations #### New Features * **Veza integration (Early Access)**: Administrators can now configure a Veza integration for search and access review of Veza user roles and team assignments. Adding the integration from the *Integrations* page in the *Integrations* section will create Access Graph entities for the Veza domain, teams, roles, and users. Saved queries are now available to identify deactivated and inactive Veza users and empty Veza teams. #### Bug Fixes * Open Authorization API: Improved performance when parsing large custom provider payloads. * GitHub integration: Added logic to avoid "API rate limit exceeded" errors during extraction. ### Search and Insights #### Enhancements * **Permissions filters for Workflows, Graph, and Query Builder**: All Veza search interfaces now use the same permissions filter to constrain results based on their effective or system-level permissions. Attribute filters are no longer used to filter individual permissions. * **Unified Saved Queries and Rules**: The *Saved Queries* page now includes a tab for creating and managing *Rules* based on their underlying saved queries. You can use this view to see whether a query has rules associated with it, add rules, and review the condition and severity of any active rules. #### Bug Fixes * Fixed an issue preventing users from updating saved query filters on attributes with boolean values. ### Workflows #### Bug Fixes * Fixed an issue with webhook notification batching when using Smart Actions to update many results simultaneously. * Fixed an issue preventing some columns from being included in PDF exports. * The certification status banner is now collapsed by default on mobile or tablet. The expanded or collapsed state is now stored in the browser and applies to all certifications. * Users with the “Access Reviewer” role can no longer mark a certification *Completed* when all rows have a decision and they are the final user to sign-off. --- # 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.veza.com/4yItIzMvkpAvMVFAamTf/release-notes/release-notes/archive/2023.6.12.md?ask=&goal= ``` `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.