Quickstart

This walks through the shortest useful path: create a workspace, fill in a few pages, publish them, connect Claude, and watch it use what you wrote. You can do all of it alone and invite your team afterwards.

Prefer to let your agent do it? Share Set up Herald with your agent with Claude, ChatGPT or Claude Code. The page is written for the agent, which connects the workspace and drafts your first pages with you.

1. Create your workspace

Sign in and you'll be asked for two things: your company name and a name for your first workspace. The company becomes your organization. The workspace is where your pages live. If you're not sure what to call it, use the company name again; you can rename it later from the Members page.

Then pick a starting point:

• Sales & Marketing gives you ten starter pages in four folders (Company, Market, Voice & rules, Proof), a set of channel and funnel-stage tags, and seven packs for common jobs like outbound email and landing pages. The pages are mostly empty headings with prompts underneath. Pick this if you're starting from scratch, even if you're not in sales or marketing: it's easier to delete pages than to stare at a blank sidebar.
• Blank is an empty workspace. Pick this if you already have docs you're going to import.

2. Write three pages

Don't try to write everything today. Three good pages are enough to see the difference, and they tell you what's worth writing next.

If you took the starter template, fill in these:

Company overview. What you do in a paragraph a customer would recognize, who you serve, and a few hard facts (founded, headquarters, number of customers). Write it the way you'd explain it to a smart new hire on their first morning.

Brand voice. This one is already set as a rule, so it'll go out with every request. Describe how you sound in a line, then give a few short examples of sentences that sound like you and a few that don't. Examples do more work than adjectives: "friendly but direct" means something different to everyone, but two sample sentences don't.

One page about the thing people ask your AI for most. For a support team that might be the refund policy. For sales, the competitor that comes up on every call. For engineering, the API conventions. Whatever it is, give each distinct topic its own ## heading.

The editor saves as you type. You can switch between the rich editor and plain Markdown with the two buttons at the top right of the page.

Why headings matter: pages are split into sections at their headings, and an agent usually gets the best few sections rather than whole pages. A heading like "Refunds after a downgrade" can be found on its own. A wall of text under "Policies" can't. Writing pages agents can use goes into this properly.

3. Publish

Nothing you write reaches an agent until it's published. Each page has a status chip at the top: Draft means agents can't see it at all, Unpublished changes means they're still getting the previous version, and the highlighted Published means they get exactly what you see.

Press Publish on each of your three pages. If you have a lot of pages waiting, the Unpublished item in the sidebar lists them all, and you can publish everything at once from there.

Once a page is published, open How agents see this page at the bottom of it. That's the list of sections search will work with, along with their sizes in tokens and the tags they picked up automatically. If a section looks too big or a heading looks vague, this is where you'll notice.

4. Connect Claude

Open Connect agents in the sidebar. At the top you'll see two URLs. For Claude you want the first one, the sign-in URL. It ends in /api/mcp.

In Claude (web or desktop):

1. Go to Settings → Connectors → Add custom connector.
2. Paste the sign-in URL and save.
3. Click Connect, then sign in with the same account you use for Herald.

That's all. Claude now has the workspace's tools, and it acts as you: it sees what you can see.

Claude decides for itself when to use the workspace. To have it check every time, add a few lines to your Claude preferences. Instructing Claude has the wording, or share Set up Herald with your agent with Claude and it will walk you through it.

If you use something other than Claude, the Connect agents page has a tab for ChatGPT, Cursor, Claude Code and other clients, and Connecting your tools covers each one.

5. Try it

Start a new chat and give Claude a real task, the kind you'd normally do by hand. For example:

Write a short LinkedIn post announcing that we now support group bookings.

You should see Claude call get_context before it starts writing. If it doesn't, nudge it once ("use the context tools first") and it will. Most clients also let you expand the tool call to see exactly what came back.

Now read the draft. Does it sound like your voice page? Does it get the facts from your overview right? If something's off, the fix is almost always in a page, not the prompt.

6. Look at what the agent asked for

Back in the app, open Activity. Your request is at the top, with the task Claude passed, which pack it matched (if any), and the pages that went back. If the Pages column says 0, the workspace had nothing for that task. The Nothing found filter shows only those, and over time it becomes a to-do list of what to write next.

Where to go from here

• Invite your team from the Members page. Give people read access, or edit access to the workspace or just the folders they own. See People and access.
• Import what you already have. Word docs, PDFs, Markdown, spreadsheets and decks. See Importing what you have.
• Write a few packs for the jobs your team does most, so the right pages always turn up. See Rules, pinned pages and packs.
• Give a contractor or an automation an API key that reads this workspace and nothing else. See API keys.