> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Let an AI Agent Fill Fields and Move Cards
- URL: https://blog.jestor.com/ai-fill-fields-move-cards/
- Published: 2026-09-17T22:26:05.000Z
- Updated: 2026-09-17T22:26:05.000Z
- Author: Bruno Bannach

Letting an **AI agent fill fields and move cards** is a permissions question before it is an AI question. You decide which fields it may write to, and everything you do not select stays outside its reach.

## The fields nobody wants to fill

There is a category of data that is genuinely useful and genuinely tedious, which is why it usually goes unfilled.

- Sentiment — whether the person writing is frustrated
- Category — finance, HR, support, or something else
- Priority — how urgently this needs attention
- Responsible team — who should pick this up

## Full access versus scoped access

| Approach                     | What it means                           | Risk profile                                |
| ---------------------------- | --------------------------------------- | ------------------------------------------- |
| **Full access**              | The agent can write to any field        | High — mistakes reach critical data         |
| **Scoped access**            | Only the fields you select are writable | Low — errors are contained and correctable  |
| **Scoped plus confirmation** | A person confirms before the agent acts | Lowest — recommended for critical processes |

## How to configure it in Jestor

1. Open the agent configuration in **Jestor** and find the field permissions area.
2. Select only the fields the agent should be able to change.
3. Leave sensitive fields unselected — the agent cannot access or alter them.
4. Enable card movement if you want the agent to advance or close records.
5. Add a checkbox variable as a confirmation gate on processes where mistakes are expensive.

## Why choose Jestor for controlled AI automation?

**Jestor** makes the boundary explicit and visible in the configuration itself, rather than buried in a policy document. That is what makes it reasonable to start with a process that matters instead of a test case.

Permissions on the platform already work by role, field, and action — agent permissions follow the same logic your team is used to.

## Frequently Asked Questions

### What happens to fields I do not select?

The agent cannot access or change them.

### Can the agent move cards between phases?

Yes, including closing resolved records. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### How do I add a human checkpoint?

Use a checkbox variable that must be ticked before the agent acts.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.