> 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/administration/settings.md).

# Settings

### Overview

Settings control defaults and behavior at the Account, Organization, or Project level.

### Key Concepts

* **Account settings**: affect every Organization and Project
* **Organization settings**: affect the Organization and Projects inside it
* **Project settings**: affect a single Project
* **Default**: starting value applied to new items

### How It’s Used

Use Settings during rollout and when governance changes. Use Account settings for shared fields and controls. Use Project settings for delivery-team workflow defaults.

### Benefits

* More consistent workflows across Projects
* Cleaner reporting through standardized fields
* Reduced access drift through scoped configuration

### Setup Steps

{% stepper %}
{% step %}

### Open settings at the required scope

Open settings from Account, Organization, or Project navigation.
{% endstep %}

{% step %}

### Apply changes with governance in mind

Prefer Account-level settings for shared fields. Use Project settings for initiative-specific workflows.
{% endstep %}
{% endstepper %}

### Best Practices

* Document field meanings and status definitions in a shared SOP.
* Duplicate shared configurations before major changes.
* Review settings quarterly to remove unused fields and templates.

### Summary

Settings control defaults and behavior by scope.

Account settings standardize shared fields.

Project settings shape delivery workflows.

Related:

* [Account Configuration](/administration/account-configuration.md)
* [Project Settings and Configuration](/organizations-and-projects/project-settings-and-configuration.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 by asking a question.

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

```
GET https://help.transform.ai/administration/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.