Release: February 2025

The February 2025 release for Hive9 is available from February 26, 2025, and adds these features to the platform:

General availability

  • Administrators can log in as other users: With the new Log-in-As feature, administrators can now securely log in to Hive9 as any other user. This capability lets the administrator see the Hive9 platform exactly as that user does, making it easier to investigate and troubleshoot user issues, test permission configurations, and more. To ensure user privacy, this feature requires explicit user consent to be used, and offers configurable access duration controls.

  • Customizable user inactivity timeouts: Administrators can now set a custom idle timeout duration for their Hive9 instance to help prevent unauthorized access and safeguard sensitive data. With the new Application Timeout setting, you can define how long (in minutes) an authenticated user's session will remain valid while they are inactive: if this time period elapses before the user has become active again, the user is automatically logged out of the system and must authenticate to regain access.

  • New User Category attribute for user accounts: We have introduced a new mandatory attribute for user accounts that allows administrators to define user categories. When enabled, Hive9 users can assign themselves to a category on their profile using the new User Category attribute (the value can also be changed by authorized users with the appropriate permissions from the Org. Setup screen). All Hive9 entities (Plan, Campaign, Program, Tactic, Line Item) automatically inherit the entity owner's User Category attribute value, allowing this attribute to be used to trigger dependencies on other Custom Attributes specific to each value.

  • Prevent deletion of Tactics connected to BGETs: If Budget General Expense Transactions (BGETs) integration is enabled in a Hive9 instance, the system now helps to ensure data integrity by preventing deletion of records associated with BGETs. If a user attempts to delete a Tactic, Campaign, or Program that is linked to a BGET, they will now see an error message that they must manually remove the BGET ID before they can delete the selected entity.

To learn more about these features and how to use them, see the Hive9 User Guide.