Feature Requests

We have clients in a variety of verticals and locations where the state has extensive consumer protection laws on consumer privacy. If a business is large enough, standard HR departments will be handling employee PII. We implement DLP solutions within MS365, firewall, Checkpoint Avanan for these clients and some clients have other point solutions in place that they manage. We need to be able to monitor for compliance breaches in Ai prompts within Hatz Ai. Feature options such as: Warn the end user for possible PII in real-time Alert a security officer or email distro while halting the user/Agent AI usage or process provide a compliance dashboard reporting mechanism full api access to the prompt and input txt I am sure others are much more verse in other safeguards and actual regulation standards that must be met. However, we are getting these types of questions to provide our clients (outside of possible Hatz deal) to provide them with Prompt security to Copilot and Claude. It's still early in the industry, every vendor is just 6 weeks they claim from going GA on some new Ai security solution. One of our clients didn't understand that with SentielOne's recent Prompt Security platform, we couldn't just turn it on in the S1 agent. Customers are seeking security solutions for AI, the more native and baked into Hatz the better.

Currently only MSP admins can create custom roles and add credit limits. I have a tenant who wold like to create custom roles and add credit limits to have more granular control over the credits used in their account. This makes more sense to me that the power to restrict credit usage should be in the hands of the client admin, rather than the MSP admin because they (or their company) are the ones paying for the credit package.

One big concern that has come up with our clients is the lack of ability for an admin to be able to have visibility to any agents or workflows that a particular user has built unless they proactively share them. This is a major concern for two reasons. 1st. if the user is terminated and account removed, there's no ability to confirm if there are agents/workflows that need to be moved to someone else. 2nd--and this is an even bigger concern, without visibility there's no way to audit the user and verify they aren't using the companies Hatz environment for their own personal benefit or to generate side income using the companies resources. I would love to see some kind of ability to audit or view all private agents and workflows so the company paying for the platform can be reassured that credits and useage aren't being abused and used for personal gain.

Currently the compliance log is missing some logging I would consider critical. Would like to request audit log shows when agents/workflows/etc are created or deleted.

Currently there is no ability to delete multiple users at once through the GUI. This lengthens the time it takes if you have multiple users that need to be deleted. Hatz should allow checking off multiple users at once and then just clicking a single delete button to perform the deletion.

Need an option to sell to orgs governed by HIPAA. This means a bundle of LLMs that are HIPAA friendly and the ability to get a BAA signed by Hatz. We've lost opportunities because this isn't available yet.

Would be great to have a geo location in a Canadian AWS DC to hit the data residency requirements of a lot of Canadian companies.

There does not seem to be a way to move assets for an employee to a different person when their employment is terminated (in a similar way that Onedrive move, shared mailbox, password vault migrations etc) and there does not seem to be a way to even see if someone has agents and workshop items that the business could be relying on. Please provide the ability to move resources to a different user. Ideally this would function the same way that Keeper or Onedrive does, where all assets show up under a FromUserX tag/folder.

Currently, as an MSP, my understanding is we would have to have a user account in each of our clients' Hatz tenants to be able to see the Workshop > Connections turned on. We would like the ability to see Connections turned on per tenant at the admin level for increased transparency in management/consulting and usage education. Honestly, it would also be nice to add a widget on the Tenant Dashboard: "Top Connections"

Title: Account Team Permissions and Role-Based Access Control (RBAC) Business Problem Today, applications inherit broad access permissions, making them available to all users with platform access. As we expand internal applications and client-facing workflows, there is a need to restrict access based on account ownership, team membership, and job function. Managing permissions separately in every application creates operational overhead, inconsistent security controls, and increases the risk of unauthorized data access. Requested Enhancement Create a centralized Account Team Role and Permission framework that can be used across all applications and workflows. Requirements Account Team-Based Security Groups Associate users with specific client account teams. Support assignment by: CAM vCIO Service Manager Project Manager Executive Sponsor Technical Resources Custom roles Role-Based Access Control Allow administrators to define roles and permission sets centrally. Roles should be reusable across applications. Permissions should determine: View access Edit access Administrative access Reporting access Workflow approval rights Client Data Segmentation Users should only see data, reports, notes, action items, dashboards, and workflows for accounts they are assigned to. Support exceptions for executives, management, and delegated access. Application Integration Applications should inherit permissions from the centralized RBAC engine. Developers should not need to build custom permission systems within each application. New applications should be able to consume the framework as a shared service/module. Active Directory / Entra Integration Integrate with existing user and group management. Allow permissions to be assigned to: Individuals Security groups Department teams Account teams Audit & Governance Track: Who has access to each client account Permission changes Role assignments Delegated access activities Business Value Prevents unauthorized access to client information. Enables secure scaling of internal AI and operational applications. Reduces development effort by providing a shared permissions framework. Improves governance, compliance, and auditability. Creates a consistent user experience across all applications. Requested Outcome A centralized Account Team and Role-Based Access Control service that can ensure permissions are managed once and consistently enforced everywhere.