Skip to main content
You can use Markdown to customize your agents with AI personalization. They read it when they start working on a new workflow and follow the instructions it contains. It’s especially useful for rules that apply across all your workflows, for example how your team names fields, which date format your warehouse expects, which sources are off limits, and who to ask when something is ambiguous.

​
Where to set it

Go to Settings > Workspace and edit the AI personalization field, then click Save. Anyone in the workspace can edit it. Renaming the workspace still requires an Admin or Owner. The field takes Markdown and holds up to 8,000 characters.

​
When it takes effect

The text is read once, when a workflow’s Assistant session is created. Every workflow has one long-lived session, so:
  • Workflows and real-time monitors you create after saving an edit follow the new text.
  • Workflows that already exist keep the instructions their session started with. Reopening the chat resumes that session, so it does not pick up the edit. To apply new rules to an existing workflow, say them in the chat or put them in the workflow prompt.
Personalization applies to the whole workspace, so everyone’s agents follow it. If you belong to several workspaces, each one has its own text.

​
What to write

Write it like onboarding notes for a new colleague. Short, concrete rules beat long prose.
A few more examples of instructions that pay off:

​
What not to put here

  • Secrets. Store credentials as variables or secrets and reference them by name.
  • Instructions for one workflow. Those belong in that workflow’s prompt or in a template.
  • Schema definitions. Define fields in the workflow schema, where they are validated per run.

​
Next steps

Kadoa Assistant

Build and debug workflows by chatting

Prompts

Write per-workflow extraction instructions

Templates

Share prompt and schema settings across workflows

Variables

Store reusable values and credentials