Templates
A template (also called a blueprint) is a definition of a resource that FYAI maintains centrally — an agent, a team, a model configuration, a workflow and so on. FYAI copies templates into customer projects so that every workspace starts with useful, working resources. These copies are your platform-managed resources.
Templates are published and maintained by FYAI. Customers don't create their own templates; to share your own work with other projects or organisations, use promotion or a Marketplace stack.
Which resources come from templates
FYAI can publish templates for:
| Resource | Notes |
|---|---|
| Agents | Bring their model and functions with them. |
| Teams | Bring their member agents and coordinator. |
| Functions | Connected to your copies of the integrations they use, where available. |
| Models | Platform-managed model configurations. |
| Integrations | Copied without any secrets. |
| Workflows, manifests, dashboards | |
| Elements | Usually shared: one platform copy that every organisation reads, rather than a copy per project. |
| AI systems and control catalogues | Used by Governance. |
| Data sources | Data source templates are available through the API. |
How templates reach your project
When an organisation or project is created. New organisations get a default project stocked with the platform's starter resources. When you create a project, the Include platform-managed resources option (on by default) does the same for that project. Turn it off for a project with only your own resources. See Organisations and projects.
When FYAI rolls out a new template. FYAI can deploy a template to every organisation. Rollouts go to each organisation's default project.
When you first chat with a platform agent. Some platform agents are listed in every organisation. The first time you start a chat with one, FYAI creates your organisation's copy.
On request, through the API. You can list templates and create a copy in your current project with the Platform API or the platform MCP server — for example with the list_agent_templates and instantiate_agent_template tools, instantiate_catalog_template for workflows and manifests, and instantiate_integration_template for integrations. There's no template picker in the app.
Platform-managed resources
Copies of agents and functions made from templates are platform-managed:
- they show a Platform chip, and the editor says Managed by platform — read only
- you can use them — chat with them, add them to teams, call them from workflows — but you can't edit or delete them
Other copies (for example workflows, manifests, dashboards and integrations) are ordinary resources you can change.
Platform-managed copies are linked to their template:
- Updates. When FYAI updates a template, it can push the change to every platform-managed copy, overwriting it. If FYAI changes the model behind an agent template, managed copies of that agent switch model straight away.
- Retirement. When FYAI retires a template, the copies made from it are removed from every organisation.
If you create an agent, function or integration with exactly the same name as a platform template, FYAI may later treat it as that template's copy. It then becomes platform-managed and read-only, and is removed if the template is retired. Give your own resources distinct names.
Readiness checks
Before FYAI publishes or rolls out an agent, team or function template, it checks a set of governance readiness gates: the template has a risk rating and recent review, has passed its evaluations, has a clean risk assessment, has its controls in place, and that existing copies are up to date. This is how FYAI makes sure platform-managed resources meet the same governance bar it asks of customers. See Governance.
Templates, stacks and promotion compared
| Templates | Marketplace stacks | Promotion | |
|---|---|---|---|
| Who creates them | FYAI | Any FYAI user | Any project Admin |
| What they copy | Single platform resources and their dependencies | A bundle of your components and their dependencies | One team or workflow and its dependencies |
| Where copies go | Customer projects | The installer's current project | Another project in your organisation |
| Copies stay linked? | Yes, for platform-managed agents and functions | No | No |
| Secrets copied? | No | No | Some (see the guide) |