Your knowledge.
The right hands.

Each company has its own boundary.

Server credentials select the workspace. End-user sessions bind the workspace, person, allowed website origin and current access versions. A company-wide record belongs to that company’s audience; it is not shared across customers.

Gates are checked before retrieval and again before protected answers or action results are returned. Source deletion, restrictive updates and identity changes can invalidate access to earlier conversation content.

Prompts don’t grant permission.

Your instructions shape the assistant’s behavior. They do not grant access to records. Retrieved content and customer-hosted action results are treated as untrusted context, even when the current person is allowed to read them.

Golden tests use the selected person’s real context. Expected answers go to the judges, not into the assistant’s answering prompt. Publication is tied to the tested version and its current release context.

Actions stay accountable.

Huck signs deliveries to your configured HTTPS service and verifies incoming callbacks. Unique invocation IDs, monotonic progress and terminal-state checks handle retries and out-of-order events.

Your service must also authorize the requested business record. Cancelling in Huck does not undo work your service already accepted; reconcile that work at its source.

Know what you’re connecting.

Configured model and embedding providers receive the authorized content needed for generation or indexing. Review those providers and your deployment’s data practices before sending sensitive information.

Keep source records current through the API, revoke access when responsibilities change, and remove content that is no longer needed. Your control room shows indexing status, usage and test results so your team can review what the assistant is working with.

A private place to ask for help.

Support requests and feature ideas go to a separate team inbox. Contact details, subjects and messages are stored encrypted, and team access requires a separate support permission. These messages do not become part of your assistant’s knowledge.

Include enough detail to explain the issue, while keeping passwords, API keys and private customer conversations out of the request.

Your identity is yours, too.

Your customers can meet a neutral assistant or your own brand. You can change the name and welcome and turn off the Huck character. Ranch and Frontier also support your logo, full branding removal and custom placement.