Agents
An agent is an assistant you shape: its own instructions, its own knowledge base, its own greeting. Where plain chat answers from the model's general knowledge, an agent answers as a specialist you've briefed, the conveyancing assistant that knows your precedents, the policy assistant that knows this year's manual.
Creating and editing agents needs the author agents grant or admin permissions. Every member sees the workspace's agents on the chat page's Agent tab, unless an agent is limited to specific users/roles.
Create an agent
- On the Agents page, click to create one and provide name, description, and an optional greeting.
- You will be taken to the agent's editor with a draft version. Write the instructions (its system prompt, who it is, how it answers, what it must and mustn't do) and build its knowledge base.
- Test it: authors see draft agents on the chat page, marked (draft) with an amber banner, so you can test it before normal users.
- Click Promote when it's ready. The draft becomes the active version every member can use.
The active version is immutable, so an agent in daily use can't drift. To change a live agent, take a new draft from active, edit, test, and promote, the change is instant, and the previous active version is archived. Conversations that were already running keep the version they started with (a banner offers the newer one).
Knowledge bases and Agents folders
An agent's knowledge comes from two places, usable together:
- Its own knowledge base — documents uploaded directly to the draft. These belong to the agent: they don't appear in the library, and they're versioned with the agent (a promoted version's knowledge base can't be quietly changed). Refresh from latest updates a knowledge-base document to its current library version, on the draft.
- Linked Agents folders — folders of the Agents kind from the library. These are live: whatever the folder contains at the moment of a question is what the agent knows. Use a linked folder for material that changes (this month's rates, the current policy set) and the built-in knowledge base for material that should be pinned with the agent.
By default an agent presents its knowledge as its own expertise, without citing the underlying files; you can switch on knowledge-base citations per version if the sources should show.
Greetings
The greeting is the first bubble a member sees when they open a conversation with the agent, you can use it to say what the agent is for and what to give it ("Paste the clause you'd like reviewed…"). It's presentation only: it doesn't consume the model's attention/tokens and isn't part of the conversation record.
Chat agents and workflow agents
Every agent is one of two kinds:
- Chat agents appear on the chat page for members to talk to.
- Workflow agents exist to be steps inside workflows. Workflow agents never appear on the chat page, and agents created by the workflow generator arrive as this kind.
The kind is switchable on a version (Mark as workflow agent / Mark as chat agent); turning a workflow agent back into a chat agent is blocked while any workflow still uses it, and the message names the workflows it is used in.
Who can use this agent
A chat agent can be restricted: Who can use this takes members and roles, and everyone else no longer sees the agent at all. Admins, agent authors, and the agent's creator always retain access. Workflow agents aren't restricted directly instead they're reachable only through workflows, and access is governed there.
Export and import an agent bundle
Export downloads the agent as a portable bundle, instructions, greeting, and knowledge-base documents included; nothing else from your workspace travels with it. Import (on the Agents page) accepts a bundle into a workspace: everything arrives as a draft with fresh identity, knowledge documents are re-processed on arrival, and a name clash gets a suffix rather than an error. Review the draft and promote it as usual.
Limits
Your plan includes an allowance of chat agents, expandable with agent packs from the account portal; a create that would exceed it says so. Workflow agents have their own, much larger allowance and building workflows doesn't spend your chat-agent allowance.