Feature Requests

Please let us share Custom MCP Connections across tenant. This will allow us to create custom agents/apps/workflows that use them for everyone.

We'd love to be able to see how many credits are used within the chat after (Or even before!) we send a message.

It provides a good low-cost option versus competitors. Currently GLM 5.2 is latest. I see a feature request for 5.1, we're still on 5, so I'd like to see this kept up to date.

It would be great to have integration with ITGlue (and other documentation platforms) so we can use the Chat and AI Apps to search for information in the documentation platform or ask questions about standard operating procedures.

I created a workflow to generate a report and email it to a recipient but am learning that the only options with outlook is to save a draft and then approve and send it out manually. I seems like if we were using google it would be possible but for outlook this is not an option. Seems like a pretty large gap in the workflow functionality since having to manually send a draft defeats the purpose of an automated workflow.

Having the ability to report on a per user level of usage, model selection and credit usage over a specific period. I often have clients asking for reports but lack the ability to dig deeper. I have setup some custom reports using the API calls, but the user level endpoint doesn't have the granular details I'd prefer. being able to identify the users defaulting to GPT5.5 or Opus 4.7,4.8 who use 50% of the tenants credits is becoming a pressing matter.

As an MSP, some of our client's range in size from big clients with hundreds of users to small companies with less than 20 users. For our smaller clients, they are still very interested in the capabilities that Hatz can bring to them. Since the price is one flat rate, the smaller the company the more expensive the license gets per user. Is it in the works to have a smaller license for companies in the 10-15 user ballpark?

Currently, Hatz's SSO implementation is limited to a single domain. Customers with multiple domains require the ability to configure SSO across all their domains. This request is that Hatz add multi-domain support to its SSO implementation.

I'd really like to see Hatz keep up-to-date on these models. It's becoming increasingly important for us to be able to offer viable model alternatives as pricing for the most well-known providers has become increasingly volatile and unsustainable for some use cases.

===================== Current Behavior: ===================== When you set up an integration like AutoTask, even though this requires an API Service Account where you have to put in the API Username, API Secret, API Integration Code, and (optionally) Zone URL, it is still configured on a per-user basis. This integration does not connect directly to the user's account in AutoTask, and providing all of the users credentials for the API service account creates additional risk with each user. AutoTask has some particular limitations for API users, and you unfortunately cannot tie user accounts to API service accounts in a way that automatically scopes them to whatever permissions the user has. ===================== Desired Behavior ===================== There is the ability to provision an integration like this once for the entire tenant, so everyone is able to access the integration without needing to have all of the API Service Account Information. There should also be an option to override this on a per-user basis for users who need different permissions. ===================== Use Case ===================== We want an organization wide baseline of read-only for the AutoTask Integration, and we don't want to share authentication information for an API Service Account with the entire company or worry about troubleshooting things for all of the individual accounts. Allowing for an override of the org-wide setup also allows us to provision API accounts with more or less access in the case that users need to use the AutoTask integration for something that requires more than read-only permissions or we want to limit the read-only permissions of some users.