> ## Documentation Index
> Fetch the complete documentation index at: https://www.greptile.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Customization Overview

> Three ways to customize Greptile — .greptile/ folders, greptile.json, and the Dashboard UI

Greptile gives you three ways to customize review behavior. Pick the one that fits how your team works — or combine them.

## Configuration Methods

<Tabs>
  <Tab title=".greptile/ folder (Recommended)">
    A folder you place in any directory of your repo. Supports cascading — root-level defaults with per-directory overrides.

    * Version controlled and reviewed in PRs
    * Separate files for settings, rules, and context
    * Per-directory overrides for monorepos
    * Structured rules with scoping, severity, and disable-by-ID
  </Tab>

  <Tab title="greptile.json">
    A single JSON file in your repository root. Everything in one file — settings, rules, and context.

    * Version controlled and reviewed in PRs
    * Repository-wide settings only (no per-directory overrides)
    * Good for simpler repos that don't need cascading
  </Tab>

  <Tab title="Dashboard UI">
    Organization-wide defaults at [app.greptile.com](https://app.greptile.com/).

    * Changes apply immediately, no commits needed
    * Affects all repositories in the organization
    * Good for quick experiments and org-wide defaults
  </Tab>
</Tabs>

## How They Interact

When multiple methods are used, settings are resolved in this order (highest priority first):

1. **Org enforced rules** — set by admins in the dashboard, cannot be overridden
2. **`.greptile/` folder** — per-directory and repo-wide settings
3. **`greptile.json`** — repo-wide settings (ignored if `.greptile/` exists in the same directory)
4. **Org default rules** — dashboard defaults, overridden by any repo-level config

<Note>
  If both `.greptile/` and `greptile.json` exist in the repository root, `.greptile/` takes precedence and `greptile.json` is ignored.
</Note>

## In This Section

<CardGroup cols={2}>
  <Card title=".greptile/ Configuration" icon="folder-open" href="/code-review/greptile-config">
    How cascading works, merge rules, monorepo examples
  </Card>

  <Card title=".greptile/ File Reference" icon="book" href="/code-review/greptile-config-reference">
    Complete schema for config.json, rules.md, and files.json
  </Card>

  <Card title="Controlling Nitpickiness" icon="volume-xmark" href="/code-review/controlling-nitpickiness">
    Adjust strictness, filter comment types, ignore files
  </Card>

  <Card title="Training the Learning System" icon="graduation-cap" href="/code-review/training-the-learning-system">
    Use reactions and feedback to improve reviews
  </Card>

  <Card title="Custom Standards" icon="pen-ruler" href="/code-review/custom-standards">
    Enforce team-specific coding rules
  </Card>

  <Card title="Cross Repo Context" icon="folder-tree" href="/code-review/cross-repo-context">
    Reference related codebases
  </Card>

  <Card title="greptile.json Reference" icon="file-code" href="/code-review/greptile-json-reference">
    Legacy format — complete parameter documentation
  </Card>
</CardGroup>