Turn company playbooks into agent templates
Organization templates and member creation controls help admins give teams approved Gobii agent starting points without opening creation to everyone.
Teams get more value from AI agents when the starting point is consistent.
If every new customer handoff, recruiting workflow, or market monitor begins from a blank agent, small setup choices turn into process drift. Organization templates and member creation controls give admins a cleaner model: define approved starting points once, then decide which members can use them to create agents.
This update builds on Custom Instructions and the broader Organizations rollout. Instructions shape how agents behave. Templates shape how they start. Permissions decide who can create them.
Quick Summary - Organization templates create an internal library for approved Gobii agent setups. - Member creation controls let admins choose whether standard members can create agents. - Used together, templates and permissions reduce drift while keeping repeatable workflows available to the right people.
What Organization Templates Standardize
Organization templates give your team a shared starting point for repeatable agent workflows. Templates are not new in Gobii, but organization-level templates move them out of personal libraries and into team infrastructure.
Previously, you could create templates in your personal library and optionally make them public. Now your organization gets its own internal template library. Instead of one person keeping a useful setup in a private template list, the organization can make that setup available as an approved internal template.
Create a "Customer Relationship Manager" template once. When a new client signs, a teammate with creation access can launch an agent with the right instructions, defaults, and workflow assumptions already in place.
That same pattern works for onboarding agents, lead qualifiers, competitive monitors, support triage agents, or any workflow your team repeats often enough to deserve a known-good starting point.
From what we have seen, the hard part usually is not creating one useful agent. It is making the next ten agents start from the same playbook.
How Member Creation Controls Limit Sprawl
Member creation controls let organization admins decide whether standard members can create agents. That matters because team scale changes the risk profile: the same permission that helps a fast-moving launch team can create agent sprawl in a tightly controlled environment.
Admins can enable member creation when they want teammates building from organization templates. They can keep it off when new agents should be created only by admins.
For example, during a go-to-market rollout, an admin can allow members to create agents from approved templates. The team moves quickly, but each new agent still starts from a sanctioned setup instead of a one-off prompt.
Why Templates And Permissions Belong Together
Templates and permissions solve opposite halves of the same governance problem. Templates answer, "What should a new agent start with?" Permissions answer, "Who is allowed to create one?"
Without templates, creation permission can produce inconsistent agents. Without creation controls, templates can spread faster than the team can manage. Together they make agent creation more deliberate.
Same starting point. Member creation on your terms. Less drift.
When To Turn Member Creation On
Use member creation controls as a rollout switch, not just a security setting. Turn member creation on when you want people launching from approved templates, and keep it admin-only when the organization still needs tighter review.
That gives teams room to grow without treating agent creation as all-or-nothing. Start with admin-only creation, publish the templates your team trusts, then open creation to members when the process is ready.
If your team is continuing to refine repeatable workflows, Team Templates now make approved workflows easier to create and launch.