AI Knowledge Base

Please let teams maintain reusable AI agent instructions and skills in a selected GitHub repository, then synchronize and deploy approved versions to the agents that use them. Use case: a general agent routes incoming requests to support, sales or billing specialists. They share business-wide writing guidelines but also have their own responsibilities and procedures. Updating one approved instruction file should update the selected agents consistently, with a visible record of which version each agent is using. Codex or Claude could help maintain these files through reviewed pull requests. Requested workflow: Connect a private repository, select a branch and instruction/skill folders, including Markdown files. Map shared instructions and specialist instructions to selected agents/workflow AI actions and authorized sub-accounts. Show inheritance, account-specific overrides and conflicts. Detect approved branch changes automatically, with manual refresh available. Show the source commit, sync status, affected agents and differences from their active version. Preview/test a new instruction version, approve its activation, pin or restore a known-good version. Keep the last approved version if a sync fails. Handle renamed/deleted files explicitly so obsolete rules do not remain active unnoticed. Separate behavioral instructions from factual Knowledge Base content. Selecting a document as a knowledge source must not silently promote it to a system instruction. Incoming emails remain conversation data and cannot rewrite the agents' rules. Example: approve a change to the support tone or onboarding procedure once; all linked support agents receive it, while the sales agent receives only its relevant guidance. Do not export mailbox contents or secrets to GitHub by default. Related existing request for updating factual Markdown KB files via re-sync/API: https://ideas.gohighlevel.com/apis/p/re-sync-or-a-document-upsert-api-for-uploaded-markdown-kb-files-in-ai-knowledge I support that request. This complementary request concerns deployment of shared behavioral instructions/skills and per-agent version visibility, beyond updating indexed knowledge documents. HighLevel already documents reusable skills, Knowledge Bases, MCP connectors and multi-agent routing. AI Studio Git Sync handles website/app code. The proposed addition is managed GitHub synchronization and controlled activation of agent instructions, so teams do not have to copy prompts manually or wonder whether different agents are following different versions.

The current Table must be uploaded either via a CSV file or Google Sheets sync. Please also allow an option whereby, after a CSV upload, we can edit the Table without needing to delete and reupload it. Best still if we can just create the Table without uploading so it naturally can be edited The problem with Google Sheet sync is that the sheet owner must share the link to anyone that wants to update it.

Some AI agets that we want to train have to be trained on certain images and designs

We would like to train some ai agents on certain video styles, styles and formats, especially certain ai video generators

Every single AI tool across the internet is asking us to upload and train to a knowledge base. We use Notion to store everything. I want to be able to import consistently what’s in our knowledge base based on Notion.

Currently the question groupings in the knowledge gaps aren't very helpful, as it groups things together in ways that make the actual gap or questions unclear. What would be more helpful is to include the specific wording / questions asked from the contacts (not just "this is what they were asking about") This currently limits the usefulness of the tool

The knowledgebase should learn automatically from all chats and optimize itself.

When you give a user access to the Voice AI Dashboard so they can listen to call recordings and view summaries, they also end up with access to the Knowledge Base tab — and there's currently no way to stop that. These two things are bundled together under the AI module, so it's all or nothing. This is a problem for anyone running an agency or using the platform for clients, because the last thing you want is a client poking around in your knowledge base documents and training files when all they need to do is check their calls. It would be really useful to have a simple on/off toggle for the Knowledge Base tab that works independently from the Voice AI Dashboard — so you can give someone access to their call data without opening the door to everything else. It's a small change but it would make a big difference for how safely and confidently we can give clients access to the platform.

I would like to request a dedicated roles and permissions option for the AI Knowledge Base inside staff settings. Right now, access to the AI Knowledge Base appears to be tied too closely to the broader AI Agents permissions. This creates an issue for agencies that want clients, staff members, or admins to update service information, pricing, FAQs, policies, and business details inside the Knowledge Base without giving them access to the entire AI system. There should be a separate permission under Staff > Roles & Permissions > AI Agents that allows access specifically to the AI Knowledge Base only. This would allow agencies to give selected staff or clients the ability to update Knowledge Base content without compromising access to sensitive areas such as: Voice AI prompts Conversation AI settings AI agent configurations Workflows Automation logic Agency-level AI systems Other private client or agency assets This is especially important for agencies managing multiple client accounts. Many clients need the ability to update their own pricing, services, business hours, policies, and FAQs, but they should not have access to the full AI agent setup. Suggested permission structure: AI Agents Permissions: View AI Knowledge Base Edit AI Knowledge Base Create Knowledge Base Content Delete Knowledge Base Content Manage Voice AI Manage Conversation AI Manage AI Agent Settings This would make the Knowledge Base safer, easier to maintain, and more scalable for agencies. It would also reduce the need for agencies to manually update client Knowledge Bases every time pricing, services, or FAQs change. The goal is simple: Allow clients or staff to manage the information the AI uses, without giving them access to the systems that control how the AI operates.

We need the ability to see change history and restore previous versions for the Rich Text Files in the KB Similar to how Google Docs does it, where you can see changes made in previous versions, who made them, when they were made and also restore past versions Currently we're using a mix of Google Docs and Rich Text Files for the KB, both are great, but the Rich Text files are so much easier to edit and update for clients and team members What is preventing us from fully adopting this over the Google Docs is not being able to see who made changes / restore past versions / etc as mentioned above This would make the system much more effecient as currently we're running into permission considerations for connecting Google Docs / Drive for clients