For the complete documentation index, see llms.txt. This page is also available as Markdown.

Project Templates

Save reusable project setups that pre-bind groups, project type, email filing, discoverability, and a default description, so you don't reconfigure the same fields every time you create a project.

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.

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.

  • 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 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 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 dropdown in the project template editor, open to show Organization default, Discoverable, and Hidden
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). 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).

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. For the full member-facing explanation, see Projects: Project discoverability.

Creating a project template

  1. Click Add Template.

  2. Enter a Name (e.g., "Healthcare – Tier 1").

  3. Add a Description that explains when this template should be used.

  4. Toggle Enable email filing by default on or off.

  5. Optionally pick a Default project type.

  6. Choose a Discoverability setting: Organization default, Discoverable, or Hidden.

  7. 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.

  8. Click Save.

The template is immediately available in the project-creation wizard for everyone in the organization.

Editing a project template

  1. Click the row of the template you want to edit.

  2. Change any field: name, description, defaults, or group bindings.

  3. 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. On the template's row, click the menu and choose Duplicate.

  2. 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.

  3. Click the new row to rename it and tweak the bindings.

Deleting a project template

  1. On the template's row, click the menu and choose Delete.

  2. 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 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 list supports:

  • Search by template name or description (case-insensitive).

  • Sort by Name, number of bound Groups, or Last modified: click the column header.

Last updated

Was this helpful?