Core Web App

Have the ScreenConnect Helper automatically open the matching company passwords for the device you're connected to instead of having to choose a company first to view their passwords.

Some passwords have more than one URL/Web portal, clicking on the URL with those multiple urls in the single field breaks redirects. Would be nice to have multiple URL fields with what goes where.

When opening a Picture, the only way to close it is to hit the "x" icon. Escape, clicking out of it, etc do not close. Additionally, the trash can is right next to the close icon. I believe this should be moved to prevent risk of accidental deletion or inconvenience at the least.

It would be great if we could create 1 single link & page, with multiple separate cards displayed, to share passwords in bulk. For example, a user might have a domain account, MS365 & Google account - under the current system, you need to create a separate share link for each.

Add support for assigning ownership to Knowledge Base articles, similar to Confluence and other documentation platforms. Problem Currently, Hudu KB articles lack formal ownership, making it difficult to: Identify which technician maintains specific procedures Ensure accountability for client-specific documentation Know who to contact for technical questions Manage content when technicians leave Proposed Solution Phase 1: Core Ownership Basic Functionality: Assign primary owner during article creation/editing (defaults to author) Display owner name/avatar on article pages Individual and bulk ownership transfer Filter/search articles by owner Owner dashboard showing owned articles Migration tools for existing articles UI Changes: Add "Owner" dropdown in article creation/edit form Show owner information prominently on article display Link to owner's profile/contact info Phase 2: Advanced Features Secondary/co-owner support Enhanced permissions for owners Notification system for ownership changes Approval workflows Client assignment integration Ownership analytics and reporting Benefits for MSPs For Technicians: Clear identification of subject matter experts Know who to contact for specific procedures Ownership pride improves documentation quality For Service Managers: Better visibility of documentation responsibilities Identify knowledge gaps and training needs Smooth ownership transfer when staff leave For MSPs: Improved client accountability Consistent service delivery Better knowledge retention Meet client compliance requirements User Stories As a technician , I want to own procedures I create so I'm notified of changes As a service manager , I want to see who owns procedures for proper coverage As a support tech , I want to know who to contact about specific procedures As an MSP owner , I want to reassign ownership when technicians leave Success Metrics Reduced time to identify procedure maintainers Increased procedure update frequency Improved service consistency Higher technician satisfaction Decreased duplicate procedures MSP-Specific Considerations Link ownership to client assignments Service team alignment Procedure specialisation by expertise Clear escalation paths for complex issues Priority: High - Addresses core MSP need for documentation governance and service delivery consistency.

It is not possible to add 0.0.0.0/0 to the networks tab as a public catch all. Currently, you have to add two separate networks to achieve this. 0.0.0.0/1 128.0.0.0/1

It would be great, if a layout of VLANs / Networks could be used as a template and applied into different customers (if it wouldn't be filled out automatically with the upcoming? unification of integration based card-data into Hudu-Fields).

Currently, search scope is limited to either global or company-specific. It would be helpful to support a hybrid search mode, where certain data types (e.g., passwords) are restricted to the current company, while others (e.g., companies) can still be searched globally. This would reduce the need to constantly toggle search settings and improve workflow efficiency.

We see you have the ability to export to S3 but we would like to keep our information within our already setup and controlled environment in Azure. Can we have the ability to export / backup directly to our Azure storage.