---
metadata:
  - name: generator
    content: Diplodoc Platform v5.57.3
alternate:
  - https://sourcecraft.dev/portal/docs/en/sourcecraft/concepts/org-config.md
  - https://sourcecraft.dev/portal/docs/ru/sourcecraft/concepts/org-config.md
  - href: en/sourcecraft/concepts/org-config.md
    type: text/markdown
    title: Markdown version
  - href: ../../llms.txt
    type: text/markdown
    title: llms.txt
title: Approval rules and branch policies at the organization level in SourceCraft
description: How to manage general approval rules and branch policies for all repositories in an organization using a dedicated `.sourcecraft` repository.
---
> **Documentation Index:** Fetch the complete configuration index at https://sourcecraft.dev/portal/docs/en/llms.txt


# Approval rules and branch policies at the organization level in SourceCraft

You can use a dedicated `.sourcecraft` repository to [manage](https://sourcecraft.dev/portal/docs/en/sourcecraft/operations/org-config.md) the general [approval rules](https://sourcecraft.dev/portal/docs/en/sourcecraft/concepts/code-review.md) and [branch policies](https://sourcecraft.dev/portal/docs/en/sourcecraft/concepts/branch-policies.md) for all repositories in an [organization](https://sourcecraft.dev/portal/docs/en/sourcecraft/concepts/index.md#org). This ensures uniform development standards and simplifies administration.

When you create the `.sourcecraft` repository, all its configuration files automatically apply to all repositories in the organization. You can make this repository private; the configurations will persist across all the organization’s repositories.

## Configuration files {#files}

The `.sourcecraft` repository supports the following configuration files:

* `.sourcecraft/review.yaml`: Approval rule settings.
* `.sourcecraft/branches.yaml`: Branch protection policies.

The syntax of organization-level settings is identical to that of repository-level settings.


## How configurations are applied {#principles}

Configuration changes are applied immediately after they are committed to either `main` or `master` branch of the `.sourcecraft` repository. Changes in other branches are not applied, allowing you to work on configuration changes in separate branches.

Individual repositories can override organizational settings, but only to enforce stricter requirements. For example, if the organization level settings require two approvals for a [pull request](https://sourcecraft.dev/portal/docs/en/sourcecraft/concepts/index.md#pr), a specific repository may increase this number to three approvals, but not reduce it to one.

If there are errors, the merge of branches is rejected with a detailed description of problems.


#### Useful links {#see-also}

* [Setting up approval rules and branch policies at the organization level in SourceCraft](https://sourcecraft.dev/portal/docs/en/sourcecraft/operations/org-config.md)
* [Setting up approval rules in a SourceCraft repository](https://sourcecraft.dev/portal/docs/en/sourcecraft/operations/code-review.md)
* [Setting up a branch policy in a SourceCraft repository](https://sourcecraft.dev/portal/docs/en/sourcecraft/operations/branch-policies.md)
* [Approval rules in SourceCraft](https://sourcecraft.dev/portal/docs/en/sourcecraft/concepts/code-review.md)
* [Branch policies in SourceCraft](https://sourcecraft.dev/portal/docs/en/sourcecraft/concepts/branch-policies.md)