Skip to content

docs: add topology-based project structure decision tree #7517

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Holmus wants to merge 1 commit into
base: main
Choose a base branch
from
+13 −0
Open

docs: add topology-based project structure decision tree #7517

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions docs/docs/best-practices/structuring-your-projects.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,19 @@ Before diving into recommendations, it's helpful to understand how Flagsmith org

For more details, see the [Data Model](/flagsmith-concepts/data-model) documentation.

## Decision tree: pick a structure by topology

Most decisions land cleanly when you look at how your business products and teams map to Flagsmith.

| Your topology | Recommended structure |
|---|---|
| Single business product, multiple surfaces (web + mobile + backend) | **Single project** — one shared source of truth across surfaces. Use tags, naming conventions, and tag-based RBAC to manage scope within it. |
| Multiple distinct business products under one organisation | **One project per business product.** Each product gets its own list of features and its own access boundary. |
| Independent service teams with no shared product context | **Split by team ownership.** Easy to refactor later via flag export between projects. |
| Default when uncertain | **Bias toward fewer projects.** Splitting later is reversible. Merging is harder. |

The sections below explore the trade-offs in more depth.

## When to create separate projects

Consider creating separate projects when:
Expand Down
Loading