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

# Project Settings

{% hint style="info" %}
Who can use this feature?

Only Project Admins can edit Project Settings. Members can view the configured Project Settings, but cannot edit them.
{% endhint %}

Admins can set project-specific rules from Project Settings. Any changes that are made to Project Settings will apply to all users across the project. 

### **Project Settings**

***

Project Settings can be located from the dropdown after clicking on the Project Name in the top left corner. 

#### General 

<table><thead><tr><th width="280.60546875">Setting</th><th width="498.03125">Description</th></tr></thead><tbody><tr><td><kbd><mark style="color:purple;">Project Name</mark></kbd></td><td>Custom Project Name</td></tr><tr><td><kbd><mark style="color:purple;">Project Logo</mark></kbd></td><td>Upload a PNG or JPEG as a Custom Project Logo to be used on PDF printouts (optional)</td></tr><tr><td><kbd><mark style="color:purple;">External Project ID</mark></kbd> </td><td>Custom ID used for business reference (optional)</td></tr><tr><td><kbd><mark style="color:purple;">Project Location</mark></kbd></td><td>Entering a Location for a Project enables the Weather feature, and serves as the default position for any Real World Maps.</td></tr><tr><td><kbd><mark style="color:purple;">Project Timezone</mark></kbd></td><td>Sets the default timezone for Planner and Diary features⁠</td></tr><tr><td><kbd><mark style="color:purple;">Tasks without a Production Measure</mark></kbd></td><td>Choose how progress is tracked for tasks without a production measure. Opt to <kbd>Track % Complete</kbd> or <kbd>Track End Date</kbd>. See also <a href="/docs/planner/features/status.md#changing-how-progress-is-tracked" class="button secondary">Changing How Progress is Tracked</a>.</td></tr></tbody></table>

## Project Permissions <a href="#transferring" id="transferring"></a>

***

#### **Adding Users to the Project**

Project Admins can control who can add users to the Project.

<details>

<summary>Adding Users to Project Permission Options</summary>

<table><thead><tr><th width="165">Option</th><th>Description</th></tr></thead><tbody><tr><td><code>Admins only</code></td><td>Adding users to the organisation is restricted to Admins only</td></tr><tr><td><code>All Members</code></td><td>All members of the project can add users to the organisation</td></tr></tbody></table>

</details>

<details>

<summary>Organisation subscription based Rules</summary>

<table><thead><tr><th width="165">Option</th><th>Description</th></tr></thead><tbody><tr><td><code>Enterprise</code></td><td>Adding of users to the Organisation can be restricted to System Admins only (if a person you want to add isn't a user at the organisation level, you will not be able to add them to the project unless you are a System Admin at the Organisation level)</td></tr><tr><td><code>Pro+</code></td><td>Providing users have permission to add other users to the project, there is no restrictions based on them existing at the Organisation level or not</td></tr></tbody></table>

</details>

#### **Task Status**

Project Admins can control who can edit Task Status (Planned → Promised → Done).

<details>

<summary>Task Status Permission Options</summary>

<table><thead><tr><th width="165">Option</th><th>Description</th></tr></thead><tbody><tr><td><code>Admins Only</code></td><td>Editing Task Status is restricted to Admins Only</td></tr><tr><td><code>Admins &#x26; Owners</code></td><td>Editing Task Status is restricted to Admins and Task Owners</td></tr><tr><td><code>Admins, Owners &#x26; Assignees</code></td><td>Editing Task Status is available to Admins, Task Owners &#x26; Task Assignees</td></tr></tbody></table>

</details>

#### **Regress Task Status** <a href="#transferring" id="transferring"></a>

Additionally, if `Admin & Owners`, or `Admins, Owners & Assignees` is selected, Projects can control the direction of Status changes to make sure their commitments can't be undone.

<details>

<summary>Regress Task Status Permission Options</summary>

<table><thead><tr><th width="162">Option</th><th>Description</th></tr></thead><tbody><tr><td><code>True</code></td><td>All project members can regress Task Status. <br>E.g: <br>Done → Planned or Promised<br>Promised → Planned</td></tr><tr><td><code>False</code></td><td>Project Members cannot regress Task Status. Only Project Admins can regress task status in the following ways.<br>E.g<br>Promised ← Planned<br>Done → Promised or Planned</td></tr></tbody></table>

</details>

#### Create and Manage Folders <a href="#transferring" id="transferring"></a>

Project Admins can control who can edit Create and Manage Folders.

<details>

<summary>Folder Management Permission Options</summary>

<table><thead><tr><th width="165">Option</th><th>Description</th></tr></thead><tbody><tr><td><code>Admins Only</code></td><td>Creating and Managing Folders is restricted to Admins Only</td></tr><tr><td><code>Admins &#x26; Members</code></td><td>Creating and Managing Folders can be done by Admins and Members</td></tr></tbody></table>

\*Managing Folders includes editing all properties (name, code, colour, position) and the ability to delete folders. \
\
It does not include the permission to change Folder Protection State. This will always be reserved for Admins Only.

</details>

#### Create Root Folders <a href="#transferring" id="transferring"></a>

Additionally, if `Admins & Members` have permission to Create & Manage Folders, Projects can disable the option for Members to create Root Folders .

<details>

<summary>Root Folder Permission Options</summary>

<table><thead><tr><th width="162">Option</th><th>Description</th></tr></thead><tbody><tr><td><code>True</code></td><td>Members can create Root Folders</td></tr><tr><td><code>False</code></td><td>Members cannot create Root Folders.<br>(Subfolders can still be created)</td></tr></tbody></table>

</details>

#### Create & Manage Blockers

Projects can control who can edit Create and Manage Blockers.

<details>

<summary>Blocker Management Permission Options</summary>

<table><thead><tr><th width="165">Option</th><th>Description</th></tr></thead><tbody><tr><td><code>Admins Only</code></td><td>Creating and Managing Blockers is restricted to Admins Only</td></tr><tr><td><code>Admins &#x26; Members</code></td><td>Creating and Managing Blockers can be done by Admins and Members</td></tr></tbody></table>

Managing Blockers includes editing all properties (name, category, colour, automated due date) and the ability to archive & delete Blockers.

</details>

#### Create & Manage Tags

Projects can control who can edit Create and Manage Tags.

<details>

<summary>Tag Management Permission Options</summary>

<table><thead><tr><th width="165">Option</th><th>Description</th></tr></thead><tbody><tr><td><code>Admins Only</code></td><td>Creating and Managing Tags is restricted to Admins Only</td></tr><tr><td><code>Admins &#x26; Members</code></td><td>Creating and Managing Tags can be done by Admins and Members</td></tr></tbody></table>

Managing Tags includes editing all properties (name, colour) and the ability to archive & delete Tags.

</details>

## Transferring Projects <a href="#transferring" id="transferring"></a>

***

Projects can be transferred from one Organisation into a different Organisation (within the same data region).

All data inside a transferred Project is preserved. Transferring a Project impacts the Project URL, leaving any prior URLs to Published Versions and Shared Plans invalid.

If the users on the Project do not already exist as a User inside the Destination Org, they will be automatically invited as Standard Organisation Users.

In order to start a Project transfer, the user initiating must be an Organisation Admin in both Organisations.

## Archiving Projects <a href="#archiving" id="archiving"></a>

If a project is Archived, it is no longer accessible to any users and will not appear in the Project list. Archived Projects can be restored at any time.

Archived Projects can be permanently deleted. All project data will be deleted without any possibility of being restored.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.aphex.co/docs/project-settings/project-settings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.