Feature Requests

Allowing a user role to be assigned to a group, so anyone in that user role is automatically added to that group. for larger clients having a more flexible and diverse way of sharing access to groups with workshop items can help solve the time and effort of manual group administration.

I've seen a few instances of internal information being accidentally shared in the Community and often from MSPs themselves. Agents and Workflows that reveal sensitive information that were clearly not intended to be shared publicly, as they have since been removed. In order to prevent such incidents, I would like a setting or role adjustment for MSP Users to prevent them from having "Share in community" permission. I see we can disable community entirely, but for adoption/onboarding having ideas from the community is so very beneficial, at the same time during adoption/onboarding, people are the least informed about the platform and may not understand that "Share in community" is essentially public.

I was trying to determine if we were to create a custom "Agent" specifically for a client, could we restrict the ability for them to see or edit the Instructions (System Prompt) once deployed in their tenant? The goal would be to protect any IP in our development that would then be used by the client for their benefit.

In order to keep track of which tenants templates have been shared with would be helpful.

An account-wide/shared source library for our company that will inform all Hatz AI usage throughout individual accouts, Documents like our writing style guides and product listings.

Similar to folders for organizing chats, there should be folders available on a tenant and personal level for AI assets. We need to be able to label a tenant folder "finance" for all the finance-related apps, agents, and workflows. Then we could have more folders for "compliance", "service desk", etc., and keep the growing number of AI assets more organized. I'd love this on a personal level as well since I develop a lot of assets and my screen is overloaded when I go looking for specific assets to do further work on.

Implement "Project" folders that function as a unified workspace, similar to Claude projects. - Folder-Level Knowledge: Allow users to upload "Project Files" (PDFs, docs, code) that are automatically indexed and accessible to every chat within that folder. Custom Instructions: Set a "Project Brief" or system prompt that applies to all chats in the folder, eliminating the need to repeat context. Cross-Chat Awareness: Enable the AI to reference context or conclusions from previous chats within the same project folder.

the ability to transfer ownership of an app, agent or workflow in the case of the original owners dismissal.

Currently, only the creator/owner of an agent can edit it. While agents can be shared across an organization for use, editing rights are restricted to the original creator. Other users attempting to edit a shared agent receive a "Failed to save agent" error. Custom roles and permissions do not appear to offer a workaround for this at this time. Requested Feature: Allow account admins or agent owners to grant editing permissions for shared agents to other users within the organization — without requiring those users to duplicate the agent into their own workspace. Use Case / Business Need: Teams that want to maintain a single, consistent version of an agent across their entire company are currently unable to do so collaboratively. If edits are needed, the only current option is for each user to create their own copy, which leads to version inconsistencies and defeats the purpose of a shared, company-wide agent. The ability to collaboratively edit a single shared agent would allow organizations to: Maintain consistent outputs across all users Streamline agent management and updates Avoid duplicate, out-of-sync agent copies within the same account