Skip to main content
A locked template is how one owner standardizes a process for a whole group: everyone clones and runs it, but nobody can change the core logic — only the fields marked as placeholders stay editable. This is what turns a template into an admin-controlled agent.

​
Updates reach every clone

The key difference to an open template: the locked template stays in the owner’s hands after people deploy it.
1

One person builds a proven agent

A workflow works — say, a standardized Salesforce visit report — and the team wants it.
2

The owner publishes it locked

Everyone clones it; nobody can edit it. The process is identical for all.
3

Every improvement propagates

When the owner updates the template, the change is published to all clones at once — one central version, no drift, no chasing people to update.

​
What stays yours in each clone

Locked doesn’t mean centralized data. The owner manages the instructions, process logic, and upgrades — but every clone runs with its own access:
  • Your Salesforce, your Slack channels, your task system, your inbox context.
  • Every action happens in your systems with your credentials.
Everyone works the same way — with their own access.

​
When to lock — and when not to

  • Lock it when many (or less-experienced) people must run the identical process, and compliance or consistency matters.
  • Keep it open when users need to adapt the instructions to their own context — share a normal template instead.
Common mistake: locking too early. You freeze a workflow before it’s proven, and everyone inherits the flaws — a locked template must work from the first clone.

Watch: Templates (open and locked)

See both template types in action.

When to share what

Next: the decision guide — personal, team, or template.

Chapter 5: Admin

Governance beyond templates: people, spend, connections.