> For the complete documentation index, see [llms.txt](https://docs.cogram.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cogram.com/administration/project-templates.md).
# Project Templates
Project templates capture the parts of a project that are the same across many projects: group access, project type, email filing, discoverability, and a starting description. Once a template exists, anyone creating a new project can pick it from the wizard's first step and skip straight to **Create Project** without configuring those fields by hand.
Templates are created and managed in [Organization Settings → Projects → Project Templates](https://app.cogram.com/dashboard/settings/admin/projects/project-templates).
## Who can manage project templates
| Action | Required role |
| -------------------------------------------- | -------------------------------- |
| Pick a template when creating a project | Any user who can create projects |
| Create, edit, duplicate, or delete templates | Org Admin or Org Owner |
Members see existing templates in the project-creation wizard but do not see the **+ Create new template** link or the empty-state nudge if no templates exist yet.
## What a template includes
Each template stores:
* **Name**: shown in the wizard's template picker. 1–100 characters, unique within the organization (case-insensitive).
* **Description**: optional. Pre-fills the project's description field. Treat it as a starting point; specific projects usually need their own details added on top.
* **Default project type**: optional. See [Project Types](/administration/project-types.md).
* **Email filing default**: whether projects created from this template have email filing enabled out of the box.
* **Discoverability**: whether projects created from this template are listed in the organization-wide project directory. Choose **Organization default**, **Discoverable**, or **Hidden**. See [Discoverability](#discoverability) below for exactly what each one does.
* **Groups**: one or more groups to grant access to, each with a role of **Member** or **Viewer**. See [Project Roles](/administration/project-roles.md) for what those roles can do.
Templates do not store a project name, project number, client, or address. Those are unique to each project and must be entered each time.
### Discoverability
The Discoverability setting in the project template editor
This setting controls whether projects created from the template are listed in the organization-wide project directory (the **Organization Projects** tab on the [Projects page](https://app.cogram.com/dashboard/projects/)). The three options map exactly to the dropdown above:
| Option | What the template forces | What it means for people | If the org default changes later |
| ------------------------ | ------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| **Organization default** | Nothing: the project inherits your org's discoverability default **at the moment it's created**. | Whatever your org's default is today (Discoverable or Hidden; see [Project Management Permissions](/administration/project-management-permissions.md#project-discoverability)). | Projects already created keep the value they were given. Only future projects pick up the new default. |
| **Discoverable** | The project is always **listed** in the org-wide project directory. | Every org member can see the project exists and can **request access**; project owners, org admins, and org owners approve requests. Org admins and owners can open and edit it directly. | No effect: the template overrides the org default, so these projects stay discoverable. |
| **Hidden** | The project is always **kept out** of the org-wide project directory. | Only people who are already members (or who have a direct link) can find or open it. Non-members can't see it and can't request access; an admin must add them manually. | No effect: the template overrides the org default, so these projects stay hidden. |
"Discoverable" and "Hidden" affect only **who can find and request access to** the project. They do **not** change what a member can see *inside* a project once they're in. That's governed separately by [Asset Visibility](/administration/asset-visibility.md). For the full member-facing explanation, see [Projects: Project discoverability](/guides/projects.md#project-discoverability).
## Creating a project template
1. Go to [Organization Settings → Projects → Project Templates](https://app.cogram.com/dashboard/settings/admin/projects/project-templates).
2. Click **Add Template**.
3. Enter a **Name** (e.g., "Healthcare – Tier 1").
4. Add a **Description** that explains when this template should be used.
5. Toggle **Enable email filing by default** on or off.
6. Optionally pick a **Default project type**.
7. Choose a **Discoverability** setting: Organization default, Discoverable, or Hidden.
8. Under **Groups**, click **Add group** to bind groups to the template. For each group, pick a role (Member or Viewer). Use the search field in the picker to find groups in large orgs.
9. Click **Save**.
The template is immediately available in the project-creation wizard for everyone in the organization.
## Editing a project template
1. Go to [Organization Settings → Projects → Project Templates](https://app.cogram.com/dashboard/settings/admin/projects/project-templates).
2. Click the row of the template you want to edit.
3. Change any field: name, description, defaults, or group bindings.
4. Click **Save**.
Editing a template affects future projects only. Projects already created from the template are not modified.
## Duplicating a project template
Use duplicate when you want a new template that's close to an existing one, for example a "Healthcare – Tier 2" that starts as a copy of "Healthcare – Tier 1".
1. Go to [Organization Settings → Projects → Project Templates](https://app.cogram.com/dashboard/settings/admin/projects/project-templates).
2. On the template's row, click the **⋯** menu and choose **Duplicate**.
3. The copy is created immediately with the name suffixed by "(Copy)" (or "(Copy 2)", "(Copy 3)", etc., if a "(Copy)" already exists). All group bindings and settings are preserved.
4. Click the new row to rename it and tweak the bindings.
## Deleting a project template
1. Go to [Organization Settings → Projects → Project Templates](https://app.cogram.com/dashboard/settings/admin/projects/project-templates).
2. On the template's row, click the **⋯** menu and choose **Delete**.
3. Confirm the deletion.
Deleting a template does not affect any project that was previously created from it. Those projects keep all their groups, settings, and members.
## Using a template when creating a project
Anyone who can create a project can use a template. The template picker lives at the top of the wizard's first step.
1. Go to [Projects](https://app.cogram.com/dashboard/projects) and click **New Project**.
2. In the **Basics** step, open the **Start from template** dropdown and pick a template.
3. The wizard pre-fills:
* Description
* Project type
* Email filing default
* Discoverability
* Groups (and their roles)
4. Enter a **Project name** and **Project number**. These are always required and unique to the project.
5. Click **Create Project**.
When a template is selected, the wizard skips ahead: the **Details**, **Members**, and **Review** steps still appear in the stepper for context but are greyed out. You create the project from step 1 in a single submit.
To start from scratch instead, pick **No template** from the dropdown. The wizard restores the four-step flow and clears any values the template had pre-filled.
The **(i)** icon next to the **Start from template** label opens a short explanation and a link back to this page if you need a reminder of what templates do.
If you're an Org Admin or Owner, a **+ Create new template** link sits below the dropdown so you can jump straight into the template editor without leaving the wizard. When the org has no templates yet, the dropdown is replaced by a one-line **Create a template** nudge that links to the same place.
### What's not pre-filled
Templates intentionally don't carry per-project information. You always enter:
* **Project name**
* **Project number**
* **Client** (optional)
* **Address** (optional)
### Adding members and groups not in the template
The template's groups are applied automatically on create. To add individual users or extra groups that aren't part of the template, open the project after it's created and use **Project Settings → Members**.
## Searching and sorting templates
The [Project Templates](https://app.cogram.com/dashboard/settings/admin/projects/project-templates) list supports:
* **Search** by template name or description (case-insensitive).
* **Sort** by Name, number of bound Groups, or Last modified: click the column header.
---
# 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.cogram.com/administration/project-templates.md?ask=&goal=
```
`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.