> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/organizations-and-projects/project-settings-and-configuration.md).

# Project Settings and Configuration

{% columns %}
{% column %}
**What is covered**

* Project details and defaults
* Teammates, roles, and permissions
* Custom fields
* Integrations, templates, and automation (if enabled)
  {% endcolumn %}

{% column %}
**Permissions**

Most settings require **Project Admin** access.

Some options are **account-level**.

For example: statuses and shared fields.
{% endcolumn %}
{% endcolumns %}

### Overview

Project settings shape how a single Project works. They affect access, structure, and day-to-day workflows.

### Key Concepts

* **Scope**: changes apply at Account, Organization, or Project scope
* **Teammate roles**: permissions granted within a scope
* **Custom fields**: structured metadata for reporting and filtering
* **Templates and automation**: repeatable defaults and trigger-based actions (if enabled)

### How It’s Used

Use this page when setting up a new Project. Use it for governance changes that affect access and reporting.

### Benefits

* More consistent workflows for delivery teams
* Cleaner reporting through standardized fields
* Reduced access drift through defined roles

### Setup Steps

{% stepper %}
{% step %}

### Open the project

Open the Project to configure.
{% endstep %}

{% step %}

### Open settings

Click the **Settings** gear icon in the project navigation.
{% endstep %}

{% step %}

### Confirm permissions

Project Admin access is required in most configurations. Some Accounts also use an **Owner** role.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Screenshot placeholder: Project navigation with the Settings (gear) icon.
{% endhint %}

#### Project settings menu

Common sections:

* **Project details**
* **Team / members**
* **Custom fields**
* **Connectors / integrations**
* **Templates** (if enabled)
* **Automation** (if enabled)
* **Advanced** (if enabled)

{% hint style="info" %}
Screenshot placeholder: Settings sidebar showing the menu items above.
{% endhint %}

#### Project details

**Project information**

Typical fields:

* **Name** and **description**
* **Color / icon**
* **Project key** (short identifier used in item IDs)
* **Start date** and **end date**

{% hint style="info" %}
Screenshot placeholder: Project details form (name, description, key, dates).
{% endhint %}

**Visibility and privacy**

Options vary by Account configuration:

* **Private**: only invited Teammates
* **Team**: all Teammates in the Account
* **Public**: anyone with the link (if enabled)

**Status**

Common statuses:

* Active
* On hold
* Complete
* Archived

**Default view**

Set the first view Teammates land on.

Common defaults: **List**, **Board**, **Gantt**.

#### Team, roles, and permissions

**Add Teammates**

{% stepper %}
{% step %}

### Open the team page

Go to **Settings → Team** (or **Members**).
{% endstep %}

{% step %}

### Add a person

Click **Add member** or **Invite**.
{% endstep %}

{% step %}

### Select Teammates

Select existing Teammates, or invite a new Teammate.
{% endstep %}

{% step %}

### Assign a role

Choose the role they should have in this project.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Screenshot placeholder: Project members list with role dropdowns.
{% endhint %}

**Roles (typical)**

Transform role names vary by Account configuration.

These are the most common:

* **Admin**: manage settings, access, and content
* **Member**: create and edit work items
* **Viewer**: read-only

For scope vs role, see [Understanding Access Levels](/organizations-and-projects/understanding-access-levels.md).

**Permissions to review**

* Set who can create tasks
* Set who can delete tasks
* Set who can invite new Teammates
* Set who can change project settings
* Set who can archive the project

{% hint style="info" %}
Screenshot placeholder: Permission controls (toggles/checkboxes).
{% endhint %}

#### Custom fields

Custom fields standardize how teams capture metadata.

**Create a custom field**

{% stepper %}
{% step %}

### Open custom fields

Go to **Settings → Custom fields**.
{% endstep %}

{% step %}

### Add a field

Click **Add custom field**.
{% endstep %}

{% step %}

### Configure the field

Set:

* **Name** (for example: `Client`, `Workstream`, `Phase`)
* **Type**
  * Text (single line)
  * Text (multi-line)
  * Number
  * Date
  * Dropdown (single select)
  * Multi-select
  * Checkbox
  * URL
  * Currency
* **Required** (optional)
* **Default value** (optional)
  {% endstep %}
  {% endstepper %}

{% hint style="info" %}
GIF placeholder: Add custom field → name it → pick type → save.
{% endhint %}

**Manage custom fields**

* Reorder fields by dragging
* Hide fields from views
* Archive unused fields (data stays)
* Edit options for dropdowns and multi-selects

{% hint style="info" %}
Screenshot placeholder: Drag-and-drop reorder in the custom fields list.
{% endhint %}

**Best practices**

* Avoid duplicates of built-in fields.
* Keep names consistent across Projects.
* Document meanings in an internal SOP.
* Keep the list short. Too many fields slow everyone down.

For deeper setup, see [Custom Fields](/administration/custom-fields.md).

#### Workflow and statuses

Statuses and shared workflow fields are often **Account-level**.

Set them once, then reuse them across Projects.

{% stepper %}
{% step %}

### Open statuses

Go to Account settings for **Statuses**.
{% endstep %}

{% step %}

### Review current status columns

Review current status columns.
{% endstep %}

{% step %}

### Update statuses

Add, edit, or remove:

* **Name** (for example: `Discovery`, `Build`, `UAT`)
* **Color**
* **Type** (Not started / In progress / Complete)
  {% endstep %}
  {% endstepper %}

#### Workflow rules (if enabled)

* Define which statuses can transition to which
* Set a default status for new work
* Align on what “complete” means

#### Automation rules (if enabled)

* Auto-assign tasks when status changes
* Send notifications on specific transitions
* Update fields when conditions match

#### Templates (if enabled)

Templates speed up repeatable work.

**Create a task template**

{% stepper %}
{% step %}

### Open templates

Go to **Settings → Templates**.
{% endstep %}

{% step %}

### Create a template

Click **Create template**.
{% endstep %}

{% step %}

### Configure defaults

Set:

* Template name
* Default title and description
* Default assignee (optional)
* Default status and fields
* Subtasks (optional)
  {% endstep %}

{% step %}

### Save

Save template.
{% endstep %}
{% endstepper %}

**Use a template**

When creating a new task, pick **From template**.

Then adjust the task as needed.

{% hint style="info" %}
GIF placeholder: Create task → From template → pick template → fields prefill.
{% endhint %}

For example:

* Customer onboarding
* Bug report
* Feature request
* Meeting follow-up

#### Automation (if enabled)

Automation applies simple trigger → action rules.

**Create an automation rule**

{% stepper %}
{% step %}

### Open automation

Go to **Settings → Automation**.
{% endstep %}

{% step %}

### Create a rule

Click **Create automation rule**.
{% endstep %}

{% step %}

### Define trigger and action

For example:

* Triggers: task created, status changed, due date approaching, field updated
* Actions: assign owner, add comment, update field, send notification, create subtask
  {% endstep %}
  {% endstepper %}

For example:

* Status = `Ready for review` → assign to project lead
* Priority = `High` → send a notification to a messaging channel
* Overdue by 2 days → notify assignee and manager

#### Connectors / integrations

Connectors link a Project to external tools.

**Configure a connector**

Go to **Settings → Connectors**.

Select a service and complete the authentication flow.

{% hint style="info" %}
Screenshot placeholder: Connectors list (notifications, calendar, document storage, and other external tools).
{% endhint %}

Typical connector patterns include:

* Notifications to messaging or email tools
* Calendar sync for due dates
* Document storage links

{% stepper %}
{% step %}

### Select a service

Open a connector to enable.
{% endstep %}

{% step %}

### Authenticate

Complete authentication and approve permissions.
{% endstep %}

{% step %}

### Configure and test

Set options. Then run a test event if available.
{% endstep %}
{% endstepper %}

For account-wide integrations, see [Connectors](/administration/connectors.md).

#### Archive and delete

**Archive a Project**

{% stepper %}
{% step %}

### Open advanced settings

Go to **Settings → Advanced**.
{% endstep %}

{% step %}

### Archive

Select **Archive project**.
{% endstep %}

{% step %}

### Confirm

Confirm archival.
{% endstep %}

{% step %}

### Result

Archived projects are hidden, but restorable.
{% endstep %}
{% endstepper %}

**Delete a Project**

{% stepper %}
{% step %}

### Permissions

Only available to Project Admins or Account Owners.
{% endstep %}

{% step %}

### Open advanced settings

Go to **Settings → Advanced**.
{% endstep %}

{% step %}

### Delete

Select **Delete project**.
{% endstep %}

{% step %}

### Confirm

Confirm deletion (this cannot be undone).
{% endstep %}

{% step %}

### Result

All tasks, comments, and history are permanently deleted.
{% endstep %}
{% endstepper %}

{% hint style="danger" %}
Deletion is permanent.

Archive when restoration may be required.
{% endhint %}

### Best Practices

#### When setting up a new Project

* Set up custom fields before importing or creating many tasks.
* Pick a default view that matches the team’s workflow.
* Add key Teammates early, with least-privilege roles.

#### Ongoing maintenance

* Archive fields you no longer use.
* Review automation rules quarterly.
* Keep naming conventions consistent across Projects.

#### Team alignment

* Make one person accountable for configuration changes.
* Collect feedback before changing shared statuses or fields.
* Document field definitions and “done” criteria.

### Summary

Project Settings control access, fields, defaults, automation, and connectors for a Project.

Treat configuration changes as governed updates. Keep shared settings stable.

Related:

* [Understanding Access Levels](/organizations-and-projects/understanding-access-levels.md)
* [Add Teammates](/organizations-and-projects/add-teammates.md)
* [Custom Fields](/administration/custom-fields.md)
* [Connectors](/administration/connectors.md)
* [Working with Views](/getting-started/working-with-views.md)
* [Statuses](/transformations/statuses.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://help.transform.ai/organizations-and-projects/project-settings-and-configuration.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.