Based on the available documentation, Permit.io's GitOps workflow follows a specific repository structure where ​*each repository is mapped to a specific Permit project, and branches are created and mapped for each Permit environment*​ (1) . When you configure GitOps, Permit creates environment branches following the format

permit/generated/<env_id>

where

<env_id>

is the unique identifier for each environment (2) . The repository structure for each environment branch looks like this:

repo/
├── main (initial branch)
└── permit/generated/{env-id}/ (environment branch)
    ├── root.rego
    ├── rbac.rego
    ├── abac.rego
    ├── permit/
    │   └── root.rego
    └── custom/
        └── root.rego

(3) The documentation indicates that ​*by default, each repository is mapped to a specific Permit project*​ (2) . However, the policy code can be nested in different folders within the repository (4) . For your use case of having multiple projects in a single repository with different directories, the documentation doesn't explicitly describe this configuration. Your suggested approach of using ​*different main branches for each project*​ aligns with how the system works - you can specify a

main_branch_name

when configuring the repository (2) . You can also customize the branch name by setting the

custom_branch_name

of your environment . To explore whether directory-based separation is possible for your specific setup, I'd recommend reaching out over Email to discuss your multi-project, single-repository requirements in detail. **

To learn more, see the sources I considered: [[1] Modeling and Implementation Components](https://docs.permit.io/how-to/SDLC/modeling-implementation-components) [[2] Git and Permit](https://docs.permit.io/integrations/gitops/github) [[3] GitOps: Role assignments remain "pending" and never sync to PDP](https://github.com/permitio/opal/issues/876) [[4] GitOps Overview](https://docs.permit.io/integrations/gitops/overview)