> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kadoa.com/llms.txt
> Use this file to discover all available pages before exploring further.

# AI personalization

> Give your workspace's AI agents standing instructions they follow on every new workflow

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](/docs/ui/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](/docs/workflows/prompts).

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.

```markdown theme={null}
## Output conventions
- Dates are ISO 8601 (YYYY-MM-DD), always UTC.
- Prices are numeric, no currency symbol, with a separate `currency` field (ISO 4217).
- Use snake_case for every field name.

## Our sources
- "The portal" means partners.acme-internal.com. It needs the login stored in the `portal_login` variable.
- Never extract personal contact details from job postings. Company-level fields only.

## How to work with us
- If a field is missing on more than half the rows, ask before guessing a fallback.
- Prefer failing a run loudly over delivering partial data.
```

A few more examples of instructions that pay off:

| Goal                | Instruction                                                                   |
| ------------------- | ----------------------------------------------------------------------------- |
| Consistent naming   | "Name the primary identifier `external_id`, never `id`."                      |
| Regional defaults   | "Unless told otherwise, extract the German (de-DE) version of a site."        |
| Compliance boundary | "Do not extract user reviews or any author names from review sites."          |
| Escalation rule     | "If a source starts blocking us, ask before switching to a different source." |

## What not to put here

* **Secrets.** Store credentials as [variables](/docs/workflows/variables) or [secrets](/docs/workflows/secrets) and reference them by name.
* **Instructions for one workflow.** Those belong in that workflow's [prompt](/docs/workflows/prompts) or in a [template](/docs/ui/templates).
* **Schema definitions.** Define fields in the workflow [schema](/docs/ui/workflows/schemas), where they are validated per run.

## Next steps

<CardGroup cols={2}>
  <Card title="Kadoa Assistant" icon="message" href="/docs/ui/assistant">
    Build and debug workflows by chatting
  </Card>

  <Card title="Prompts" icon="pen" href="/docs/workflows/prompts">
    Write per-workflow extraction instructions
  </Card>

  <Card title="Templates" icon="copy" href="/docs/ui/templates">
    Share prompt and schema settings across workflows
  </Card>

  <Card title="Variables" icon="key" href="/docs/workflows/variables">
    Store reusable values and credentials
  </Card>
</CardGroup>