> For the complete documentation index, see [llms.txt](https://docs.infraglide.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraglide.com/templates-and-reference-architectures/custom-templates.md).

# Custom Organization Templates

Teams often want to standardize “our” architecture as a reusable template across Workspaces. This page describes what exists today and what to use instead until a first-class org template library ships.

***

## Current Product Reality

* The Templates gallery is a **static built-in catalog** (see [InfraGlide Template Library](/templates-and-reference-architectures/library.md)).
* Creating a pipeline from a template sets `isTemplate: false` — you get a normal draft pipeline.
* There is **no** dedicated API/UI to publish an organization-scoped custom template back into the Templates gallery, and no template-specific RBAC beyond ordinary pipeline permissions.

***

## Practical Reuse Patterns Today

Until a custom template library exists, reuse designs with these supported flows:

### 1. Export / Import pipeline

1. Open a golden pipeline → pipeline menu → **Export pipeline**.
2. In another Sandbox, **Import pipeline** (or share the export with teammates).
3. Adjust credentials, names, and environment-specific fields.
4. Save as a new pipeline / version.

### 2. Save as new version + clone workflows

Use **Save as new version** within a lineage for controlled evolution, and duplicate pipelines at the My Pipelines level when your deployment allows copy/create-from-existing patterns.

### 3. Generate with AI

On Templates, **Generate with AI** (Jane `synthesize-template`) can draft a starting architecture from a description. Review on the canvas before treating it as a standard.

### 4. Inventory import

For brownfield accounts, **Deployed Resources → Create pipeline** imports mapped AWS/GCP assets into a new draft (Azure mappings pending). See [Cloud Inventory Discovery](/cloud-sync-and-drift-detection/inventory-discovery.md).

### 5. Terraform import

**Import Terraform JSON / HCL** into the designer to turn existing IaC into a visual pipeline, then standardize manually across Sandboxes.

***

## Recommended Internal Convention

Even without a gallery entry, many teams:

1. Keep a **reference Sandbox** with golden pipelines named clearly (`ref-three-tier-web`, etc.).
2. Restrict edit rights with RBAC (Viewer on consumers, Editor/Admin on the reference Workspace).
3. Document which credential shapes and provider pins the golden pipelines expect.
4. Export/import (or recreate from template + checklist) when spinning up a new Sandbox.

***

## Hub Module

The sidebar **Hub** module provides central repository synchronization and architecture sharing capabilities across your organization.

***

## See also

* [InfraGlide Template Library](/templates-and-reference-architectures/library.md)
* [Pipeline Versioning](/visual-canvas-and-pipeline-designer/versioning.md)
* [Role-Based Access Control (RBAC)](/settings-governance-and-rbac/rbac.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.infraglide.com/templates-and-reference-architectures/custom-templates.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.