Beta
ESEN
Log inBook a demo
Documentation index
Concepts

Autonomy levels and agent rules

How to decide how much to automate each pipeline stage.

5 min read

Autonomy is how much initiative you give each pipeline module: normalization, content, SEO, images, quality control and publishing. You set it in «Configuración» → «Agente IA» (Settings → AI agent). Each one can run at four different levels.

The four levels

Automatic
The agent acts and moves on to the next one without human intervention.
Semi-automatic
The agent acts but creates an approval. The pipeline pauses until a person reviews and approves it.
Manual
The agent doesn't start on its own. It only runs if someone triggers it explicitly from the product record or a batch.
Locked
The agent is completely disabled. The pipeline skips it.
Mix levels per agent
The levels are independent. Content can be on Automatic while the publisher is on Semi-automatic. Neither depends on the other.

When to use each one

Automatic
When you trust the result. Typically after 2-3 weeks of use, once you've fine-tuned your brand voice with real examples.
Semi-automatic
The sensible default when you're starting out. Everything gets generated, and you review it before it reaches the store. A good balance between speed and control.
Manual
When the results don't convince you, or for a regulated catalog (pharmacy, children's products). You use the AI only when you decide to.
Locked
To skip an agent entirely. For example, if you already have content you've written yourself and only want to use Noobit for images and publishing.

Automatic rules

Besides the fixed level per module, you can create rules in «Configuración» → «Reglas auto» (Settings → Auto rules). Each rule says when it acts (a scan is linked, content is generated, images are processed, Product Knowledge is consolidated or quality control finishes), what conditions the product has to meet and what Noobit does then: run a task or the pipeline, change the status, notify the team or rebuild the photo from the scanner.

Some examples, in when → if → then form:

  • When a scan is linked → if it has scanner photos and no product photo → rebuild the product photo
  • When Product Knowledge is consolidated → if it has a brand → generate the content
  • When quality control finishes → if the score is below 70 → notify the team

Approval queue

When an agent on Semi-automatic runs, it creates an approval. Approvals appear in a shared queue for the whole account, in «Aprobaciones» (Approvals). Any member with the EDITOR role or higher can review them.

Each approval shows what the AI proposes. Three actions are available:

  • «Aprobar» (Approve) → it's applied and the pipeline continues
  • «Rechazar» (Reject) → it's discarded, nothing is applied
  • «Pedir revisión» (Request revision) → it's regenerated with a correction hint you write

What gets logged

For each rule, you can see how many times it has fired and when it last did, in «Configuración» → «Reglas auto».

Related

ApprovalsPipelineFeature · Approvals and autonomy levels