Importing and exporting bundles

Every starter pack on this site is a bundle, the same portable file Ferrith Chat produces when you export a workflow, an agent, or a grid template from your own workspace. This page covers both directions: bringing a bundle in, and sharing one of your own.

Before you start

• Importing a workflow bundle needs workflow authoring permission in your workspace and a plan that includes workflows. Each pack's page names the plan it needs.
• Importing an agent bundle needs agent authoring permission.
• Importing a grid template is open to every member and imports to private templates.
• Nothing you import changes what your workspace already has: everything arrives as a draft under its own name.

Import a pack

1. Download the pack's zip from its page. If you want to check it first, see Verify a download below.
2. In Ferrith Chat, open the matching area, Workflows, Agents, or Analysis grids → Templates, and choose Import bundle.
3. Pick the zip. The import runs in one go: if anything in the bundle can't be accepted, nothing is created.
4. Read the import notes in the result. They list everything the import changed or needs from you (see the next section).
5. Open the new drafts, make the changes the notes ask for, and promote each draft when you're happy with it.

What you'll see after an import

Everything a bundle creates arrives as a draft:

• A workflow bundle creates the workflow plus the agents it uses, all as drafts. Knowledge documents inside the bundle are re-processed on arrival and you'll see a Processing chip on each until it finishes.
• An agent bundle creates one draft agent, with its knowledge documents re-processing the same way.
• A grid template appears in your private templates, ready to start a grid from.

The import notes tell you what to look at:

• Renamed — something in your workspace already used the bundle's name, so the new draft carries a suffix. Rename it if you prefer.
• Reviewers reset — bundles never carry people. Any review step that named specific members or roles arrives assigned to admins; re-point it at the right reviewers before you promote.
• Folder links removed — a bundle can't reach your folders. If an agent expects a linked folder, link one of yours from the agent's page.
• Model substituted — the bundle named a model this workspace doesn't serve, so the nearest available one was used instead.

If the import is refused

The message tells you which of these happened:

• The file isn't a Ferrith bundle, or it's damaged. Download it again from this site.
• The bundle was exported by a newer version of Ferrith than your workspace runs. Update first, or ask us.
• Your workspace is at its agent limit or its storage limit. Free some space or raise the limit from the account portal, then retry.
• A document inside the bundle was refused, an unsupported format, or was over your workspace's size or page limits.
• The workflow inside the bundle didn't pass validation. This shouldn't happen with packs from this site; tell us which pack, and check the source workflow if it's your own bundle.

What to change first

1. Reviewers, always. Every imported review step is assigned to admins so you should decide who should actually review and set them on the step.
2. Knowledge. Packs may ship with small sample documents so they run out of the box. Replace them with your own material or link one of your folders.
3. The greeting and prompts. Read what the agents say and adjust the tone and specifics to your organisation before anyone else uses them.
4. Run it once yourself before promoting, so the first real user isn't the test.

Share bundles from your own workspace

The export buttons live on an agent's page, a workflow's page, and on a grid template. Exports take the active version (or the draft, if nothing is active yet) and download a zip you can send to a colleague or import into another workspace.

Before you pass a bundle on, know what's inside it:

• The bundle's contents are readable, prompts, workflow steps, grid questions, and any knowledge documents travel as-is. Share a bundle the way you'd share the documents inside it.
• No people travel. Member names, reviewer assignments to specific people or roles, and anything identifying your workspace are stripped on export.
• No data travels. Conversations, run history, your document library, and keys are never part of a bundle.

What travels in a bundle

Verify a download

Every pack's page shows the file's SHA-256 checksum. After downloading, compare:

sha256sum nda-drafter-v1.zip        # macOS / Linux
Get-FileHash nda-drafter-v1.zip     # Windows PowerShell

The printed value should match the one on the pack's page exactly. Only import bundles you downloaded from this site. Bundles aren't signed, so the checksum and the source are your guarantees.

Limits and notes

• A bundle can be up to about 250 MB, though packs on this site are kept far smaller.
• A pack's version history stays on its page; importing a newer version of a pack you already adapted creates a separate draft, it never overwrites your changes.