What you will achieve now
A decision or test applied to “Permissions and agents: automate only when the flow is ready”.
- 1 Understand the criterion
- 2 Do a small practice
- 3 Save evidence
A short note covering what you did, what went well, what failed, and what you would review next.
- Distinguish a draft, a scoped automation, and an agent with tools.
- Grant minimum, reversible permissions based on potential harm.
- Decide when a case should stay under human review or move to a technical agent path.
Not every flow needs an agent
A template that classifies an email and creates a draft can be a simple flow with fixed rules. An agent appears when the system decides which tool to use, maintains state, or chains steps with some autonomy. That capability can add value, but it multiplies error combinations. Do not add tools, memory, or multiple agents because it sounds advanced: add them only when a measured task cannot be solved with a smaller flow.
NIVEL 0 · Asistente Lee una entrada y prepara un borrador. No escribe ni envía. NIVEL 1 · Flujo acotado Clasifica o extrae con esquema, validación y revisión. Puede guardar en una zona de borradores. NIVEL 2 · Acción con aprobación Propone una acción; una persona la revisa y la confirma explícitamente. NIVEL 3 · Permiso limitado Ejecuta una acción reversible y registrada dentro de un alcance probado. NIVEL 4 · Agente con herramientas Planifica pasos y usa herramientas. Requiere estado, límites, observabilidad y recuperación específicos.
A practical permissions ladder
- Read access in a test environment: use synthetic or authorized data and do not touch real systems.
- Draft writing: store a proposal separate from the production system and require review.
- Reversible action: only after tests, logging, and a clear way to undo it.
- Irreversible or sensitive action: requires explicit human approval; payments, contracts, shipments, deletions, and decisions about people are not a good first permission.
Use separate service accounts, scope limits, and credential expiration. Do not share an admin key with an agent or put secrets in prompts, test documents, or repositories.
MATRIZ DE PERMISOS acción: crear borrador de respuesta entorno: bandeja de prueba cuenta: servicio-borradores puede_leer: ticket asignado y base documental autorizada puede_escribir: carpeta borradores no_puede: enviar, borrar, descargar masivamente, cambiar CRM aprobación: responsable de atención antes de enviar registro: ejecucion_id, propuesta, revisor y decisión revocación: desactivar cuenta de servicio y pausar flujo
Conditions for moving to automation with action
Before granting an additional permission, check that there is a flow contract, a test sample that includes failures, reviewed metrics, an owner, and a minimum operating process. Also define an error rate or incident type that forces a return to draft mode. If you cannot explain how to revoke access and recover the manual process, the permission is still too broad.
When to move toward agents in production
If the case needs multiple tools, state, retries, queues, per-user permissions, or failure recovery, continue with the technical agents path. There you will learn to design those components without turning a demo into an opaque system. If your case works as a draft with review, keeping it that way can be the most cost-effective and safest decision.
Open “Agents in production” when you already have this checklist completed.
If you have saved the evidence for this lesson, continue with “Emails: reviewable drafts”. If not, repeat the check before moving on.
Learn with a verifiable reference
Aulafy separates stable concepts from data that changes—versions, prices, models, and commands. Check the course card for the review date, verified scope, and primary sources.
“Editorial review” means structure, claims, and sources have been reviewed. It does not mean every command has been executed: when a technical test exists, it will be labeled as such.