Skip to main content
Project types are reusable templates that define the structure of a project. Each project type specifies the milestones a project moves through, the tasks created at each milestone, and optional outcomes and form inputs.

​
Company-wide vs book-specific

Project types can apply to a single book or be shared across all books in your company:
  • Company-wide — available to every book in the company.
  • Book-specific — available only in that book. Any user with access to the book can manage its project types.
Any team member can manage company-wide project types and project types in books they can access.

​
Access project type settings

1

Open settings

Click the icon at the top of the Projects page and select Manage project types, or go to Settings → Project types.
2

Select the scope

Use All owners to show every project type, or filter the table to Company or a specific book.
The project types list is a table showing Project, Owner, Milestones, Owner kind, Active projects, and Kanban for each template. The Owner column shows whether the template belongs to the company or a book. The Owner kind column shows whether its projects attach to a household, contact, or business.

​
Create a project type

Click New project type at the top right of the project types table to choose its owner and open the Projects library. From there, build a project type yourself or install a ready-made one.
1

Click New project type

Choose Company to make the project type available to every book, or choose a book for a book-specific project type.
2

Start from scratch

In Projects library, click Start from scratch. Slant creates New project type with one starter milestone and opens its editor with project type chat.
3

Describe the workflow

In Project type chat, describe the milestones, tasks, outcomes, form inputs, and settings you want. You can also close chat and configure the starter project type manually.
4

Review the project type

Check the editor after each change. Changes save automatically, and the status beside the project type name changes to Saved.
The new project type is ready to use after you finish its configuration.

​
Install from the library

The Projects library window also offers ready-made project types you can install with a couple of clicks. Each card shows a title, a short description, and sometimes a cover image or color tint. Project types you have already installed show an Installed badge and can’t be added again.
1

Pick a project type

In the Projects library window, click a ready-made card. The install wizard opens.
2

Review the milestones

The left side shows a read-only preview of the project type’s milestones in order. This is what projects of this type will move through.
3

Answer any assignee questions

On the right, fill in any questions the project type asks — for example, Who should handle this?. For each, choose a person or an existing team. Admins can also click Create a new team… to name a team and pick its members. The Install button stays disabled until every question is answered.
4

Click Install

The project type is added and you land in its editor, where you can adjust milestones, tasks, outcomes, and form inputs. Click Back at any point to return to the library grid.
The owner you choose from New project type decides the scope. Choose Company to make an installed project type available to every book, or choose a book to install it only in that book.

​
Edit a project type

Open the three-dot menu on a project type row and choose Edit to open the inline editor. The editor has two panels:
  • Milestone sidebar on the left — lists every milestone in order, with its color and a summary of its outcomes or auto-advance behavior.
  • Content tabs on the right — switch between Tasks, Outcomes, Form inputs, and Settings for the selected milestone.
The editor also has a Settings sidebar pane with template-level options: the Owner kind picker (whether projects attach to a Household, Contact, or Business), the Kanban toggle (see Rename, describe, or toggle kanban), an Attachments section, and a Danger zone for deleting the project type. Changes save automatically. A status indicator at the top of the editor, beside the name and description, shows Saving… while a change is in flight and Saved once it is stored. If a required field is missing, the indicator changes to Unsaved changes and a toast explains what to fix. If the save itself errors out, it shows Save failed.
Most changes to a project type affect new projects only. Existing projects keep their current milestone structure and tasks. Removing a milestone is the exception because it can move or complete active projects.

​
Edit with project type chat

Project type chat can update the project type through conversation while you keep its configuration visible.
1

Open project type chat

Click Open project type chat beside the save status.
2

Describe the change

Enter the result you want in Describe the changes you want…. The chat understands the milestone and tab you are viewing, so you can refer to “this milestone” or “this tab.”
3

Review the update

The editor refreshes after the change. Check the updated settings and continue the conversation if you need adjustments.
Use project type chat to:
  • Change the project name, description, owner kind, or Kanban setting
  • Add, edit, remove, or reorder milestones
  • Add, edit, remove, or reorder tasks, outcomes, and form inputs
  • Copy a milestone from another project type you can access
  • Add every milestone from another accessible project type to the current one
Use New chat to start a separate conversation. Use Chat history to return to an earlier conversation about the project type.
Configure project type attachments and task email prompts, email templates, and attachments in the manual editor.
Removing a milestone can move or complete active projects that currently use it. Project type chat explains the impact and asks you to confirm before removing the milestone.

​
Rename, describe, or toggle kanban

Click the project type name or description at the top of the editor to edit either inline. Open the Settings pane and toggle Kanban view to display this project type as a pipeline tab on the Projects page.

​
Work with milestones

Milestones are the stages a project moves through from start to completion. Each has its own tasks, outcomes, and optional form inputs.

​
Add a milestone

1

Click the + button

In the Milestones sidebar header, click the button.
2

Fill in the milestone

In the Add milestone window, enter a Name, pick a Color, and choose an Auto-advance trigger — when all tasks are completed, when a meeting is scheduled, or when a meeting is completed.
3

Click Add milestone

The new milestone is added to the end of the list and selected.
On the final milestone, the All tasks completed trigger only completes the project once every task on that milestone is closed. If no tasks have been created yet, the project waits rather than auto-completing. To finish a project with open tasks, use the Complete button on the milestone or the project detail menu.

​
Reorder milestones

Drag the handle on a milestone in the sidebar to change its position. On smaller screens, use the Reorder button above the milestone picker to open a Reorder milestones window with drag handles. Milestone order determines the default progression sequence for projects.

​
Delete a milestone

Open the milestone’s Settings tab and click Delete milestone in the Danger zone section.
Removing a milestone moves in-flight projects to the next milestone, or marks them complete if it was the final step. A project type must always have at least one milestone.

​
Configure tasks for a milestone

Select a milestone and open the Tasks tab. Tasks listed here are templates that will be created when a project enters this milestone.
1

Click Add task

The task editor window opens.
2

Fill in the task details

Each task template includes:
  • Title and Description — supports variables from form inputs and household fields
  • Priority — urgent, high, medium, or low
  • Labels — for categorization
  • Due in — a deadline offset from when the milestone is entered
  • Assigned — a specific team member, team, or a field reference
  • Email prompt and Email template — used when the task generates an email (optional)
  • Attachments — files copied to the task when it is created
3

Save

The task appears in the tasks list. The tab label shows the task count — for example, Tasks (3).
Use the three-dot menu on a task row to duplicate or delete it. Drag the handle to reorder.

​
Configure outcomes

Outcomes control what happens when a milestone is completed. Without outcomes, the project moves to the next milestone in order. With outcomes, the user picks the path. Select a milestone and open the Outcomes tab, then click Add outcome.
1

Enter a label

Type the name shown to the user (for example, “Client approved” or “Needs revision”).
2

Choose a destination

Pick Next milestone, Specific milestone, or Complete project. If you choose Specific milestone, select which milestone from the dropdown.
3

Add a default comment (optional)

Enter a comment that is pre-filled on the project when this outcome is selected.
4

Click Add outcome

Drag the handle on an outcome row to reorder. The three-dot menu offers Duplicate outcome and Remove outcome.
When a milestone has outcomes, the Auto-advance setting is replaced with “Managed by outcomes” — the outcome choice determines where the project goes next.

​
Configure form inputs

Form inputs are custom fields that collect information when a project enters the milestone. Values can also be used as variables in task titles and descriptions. Select a milestone and open the Form inputs tab, then click Add field.
1

Enter a label

Type the field name shown to the user (for example, “Account number” or “Transfer amount”).
2

Choose a field type

Pick the input type: text, long text, number, currency, date, select, yes/no, household field, or file attachment.
3

Configure the field

  • For Select, add the options.
  • For Household field, pick the record type: custodian account, person, trust, or address.
  • For most types, you can add a Placeholder.
4

Toggle Required (optional)

Required fields must be filled before the milestone can be completed.
5

Click Add field

Drag the handle on a field to reorder.
Click Preview above the form inputs list to see how the form will appear to users on a live project.

​
File attachment fields

A File attachment field renders an Upload file button on project forms. Uploaded files are stored in the household’s connected storage (Google Drive, OneDrive, etc.) and also appear in the household’s Files section. The project’s household must have a linked storage folder — otherwise the upload is disabled with a gating message. Files are limited to 10 MB, and allowed types are PDF, DOCX, TXT, CSV, XLSX, XLS, PNG, JPEG, and GIF.

​
Duplicate a project type

From the project types table, open a template’s three-dot menu and choose Duplicate. Slant creates the copy in the same scope as the original: company-wide templates stay in Company, and book-specific templates stay in that book. The copy includes all milestones, tasks, outcomes, and form inputs.
Duplicating does not move a template between the company and a book.

​
Delete a project type

From the project types table, open the three-dot menu and choose Delete. You must type the project type’s name to confirm.
Deleting a company-wide project type removes it and all associated projects for every book in the company. This cannot be undone.
You cannot delete a project type that has active projects (in progress or overdue). Complete or cancel all active projects first.

​
FAQ

Any team member can edit company-wide project types. Book-specific project types are available to team members with access to that book.
Duplicating a company-wide project type creates another company-wide template. To create a book-specific version, click New project type, choose the book, and reproduce the settings you need.
Existing projects are not affected. The new milestone only applies to projects created after the change.
Yes. Those projects are automatically moved to the next available milestone, or completed if it was the final step.
There is no fixed limit. Each project type requires at least one milestone.

​
Next steps

Creating projects

Start a new project using a project type

Pipeline view

View projects on a kanban board by milestone