Skip to main content

Release Notes - 2025-NOV-20

Added

Policy editor

You can now edit your policy documents right in Hyperproof.

  • While in the Document tab of a Draft policy version, you'll now see an Edit button, which allows you to edit DOCX files. Clicking this button will migrate your document into our editor. Note that Livesync is not supported for files that have been migrated to the editor.

  • When creating a Draft policy version, you have the option to use an external document edited outside of Hyperproof or to edit a document inside of Hyperproof. Choosing to edit inside of Hyperproof migrates your document to the editor and lets you start editing.

  • Policy approvers can leave in-line comments when reviewing documents that have been migrated to the editor.

  • Additional editor features include:

    • Full rich-text editor with live, collaborative editing

    • Change tracking and comment threads

    • Revision history

    • Option to export to PDF

Multi-step approvals - GA

Multi-step approvals for tasks and policies are now generally available to all Hyperproof customers. For tasks, the functionality allows compliance managers to automate and orchestrate the review and approval of evidence collected using tasks, eliminating the manual and ad hoc processes required today. In the policy module, this extends the previously released single-step approvals to now support multiple approval rounds (up to 6):

  • Sequential or parallel approval rounds

  • Supports requiring all approvers to approve in a round or only a specific number of approvers. Example: Add the Legal department, only require approval from 1 of them

Improvements from the early access release include:

  • The task assignee receives an email notification when a change is requested during an approval round. The task is returned to them with a status of In progress so they can address any feedback and resubmit it.

  • The comment from the approval is also included in the task Activity Feed.

  • When a new approval round is started, the previous round's incomplete approvals are cancelled.

Note

The approvals feature will be enabled automatically for early access users and any customers using the policy module. If you would like to use the approvals feature, reach out to your CSM to have it enabled.

Important update for Hyperproof Gov organizations

As part of a technology upgrade, the Hyperproof Gov production IP addresses will be replaced.

The shutdown process for the current IP addresses will take place at the end of November. When the shutdown process is complete, we will announce it in the release notes.

This change will affect any Hyperproof integration where the other system Hyperproof is connecting to has restrictions on the IP addresses allowed to access it. To avoid any connection disruptions caused by this change, we recommend you update any  allowlists you might have to include all of the following IP addresses:

Hyperproof service

Current IP address

New IP address

Main app

4.154.201.6

4.155.77.155

Integration

4.246.104.90

4.155.78.5

Failure to update your allowlists with our new IP address could result in failed connections for:

  • Hypersyncs

  • LiveSyncs

  • Task integrations

  • Selecting proof from a cloud storage system

  • Connections between Hyperproof and any other third-party system that requires an entry in their allowlist

We strongly recommend making this update as soon as possible to prevent any service disruption.

Improved

User Interface

The Hyperproof user interface has been updated with a new look! You'll see new visuals with brighter neutrals, higher contrast, and clearer alerts/status, offering a new unified, modern Hyperproof experience.

Self-service reporting

Added task IDs to the data warehouse to enhance task reporting.

Task integrations

Added a new Try again link on integrated tasks created from a repeating task. Use the Try again link to create a task in the integrated system if the task failed to be created during task generation.

Hypersyncs and integrations

  • New! Hypersync for Paylocity - proof type: List of Employee Details

  • Updated! Hypersync for AWS.

    • Added a new AWS Service: Lambda with new proof types: List of Configurations, Policies & Access Control

      Lambda must be added to your AWS policy permissions:

      • lambda:ListFunctions

      • lambda:GetFunction

    • Added a new AWS Service: KMS with a new proof type: List of Keys

      KMS must be added to your AWS policy permissions:

      • kms:ListKeys

      • kms:DescribeKey

    • Added a new AWS Service: WAF with new proof types: List of ACLs, List of Rule Groups

      WAF must be added to your AWS policy permissions:

      • wafv2:ListWebACLs

      • wafv2:GetWebACL

      • wafv2:ListResourcesForWebACL

      • wafv2:ListRuleGroups

      • wafv2:GetRuleGroup

    • Added new AWS proof types

      • EC2 - List of Load Balancers - Requires the following AWS policy permission: elasticloadbalancing:DescribeLoadBalancers

      • CloudTrail - List of Terminated Users - Requires the following AWS policy permission: cloudTrail:LookupEvents

  • Updated! Hypersync for Coupa - New proof types:

    • List of Approvals - Requires permission: core.approval.read

    • List of Commodities - Requires permission: core.item.read

    • List of Items - Requires permission: core.item.read

Help Center update

The Help Center has been updated to remove the individual sites for each role. Based on customer feedback and usage data, Hyperproof has determined that the Compliance Manager, User, and External Auditor help sites were being underutilized. As a result, we have consolidated all roles into a two-tier Help Center, with role and permission information embedded in each help article.

The top tier includes release notes, training information, tutorials, access to the Hyperproof community, and access to the full Hyperproof documentation. The second tier contains all of the product documentation for all Hyperproof roles. Roles and permissions for each feature are listed at the top of each help article, if applicable.

Addressed issues

  • Fixed the following issues with the List of Groups proof type for the Hypersyncs for Jira Server and Jira Cloud (Case # 00010560)

    • Improved the speed of the Hypersync when generating the List of Groups proof type.

    • Removed the Default column.

    • Added an "Incomplete" warning if the maximum number of groups is reached (1000). This indicates that the data has been truncated.

    • If a user doesn't have permission to fetch the group member count, the column is empty instead of displaying a 0.

    • Jira Cloud only changes:

      • If you have the Administer permission, the Product Roles column includes data. Previously, it was always empty.

      • With the correct permissions, the member count column displays data. Previously, it was always 0.

      • If you use scopes, you must add the read:user:jira and read:avatar:jira scopes to implement the two fixes above. Depending on your authentication method, you can add scopes to your API Token, regenerate it, and then update your credentials for the Hypersync. If you use OAuth, update your credentials for the Hypersync and reauthenticate. During reauthentication, the scopes will be requested.

  • Fixed an issue where Jira ticket numbers didn't display in integrated tasks generated by repeating tasks. (Case # 00010676)

  • Fixed an issue where task IDs were not included in the Self-Service Reporting Snowflake data warehouse.

  • Fixed a latency issue in the Audit module. ( Case # 00010776, 00010786)

  • Fixed an issue where archived vendors were included in the total count in the Vendors tab. (Case # 00010869)

  • Fixed an issue where the configuration window for the Hypersync for Azure didn't display all available resources. (Case # 00010837)

  • Fixed a latency issue in the Labels module. (Case # 00010902)

  • Fixed an issue where changes to Label descriptions were saved but were not displayed until the page was refreshed. (Case # 00010793)

  • Fixed an issue with ServiceNow task integration where tasks were not syncing as frequently as they should have. (Case # 00010921)

  • Fixed an issue where a compliance manager was required to be a manager on a label to create a Hypersync. Compliance managers who are contributors on a label can now configure a Hypersync. (Case # 00010908)

  • Fixed an issue where columns in the Labels grid were not sorting correctly when clicking the column header. (Case # 00010942)

  • Fixed an issue where the Overview tab didn't display correctly filtered data after logging in to Hyperproof. (Case # 00010923)

  • Fixed an issue with the Hypersync for Wiz where an error similar to the following was generated: Insufficient service account permissions. Permissions should be assigned during service account creation.

  • Fixed an issue where you couldn't deactivate a user and reassign their work in a single step. The user had to be deactivated first, and then their work could be reassigned. (Case # 00010971)

  • Fixed an issue where administrators couldn't add themselves as members to existing scopes. (Case # 00010975)

In this section: