Feature flags can reach multiple projects while keeping one primary project for ownership. You can share a flag with the projects that need it, then scope individual rules within that delivery set. You manage one shared flag instead of copying it into each project.
Separate ownership from delivery
A flag used to belong to a single project. If your projects map to services, apps, or teams, a flag that several of them needed didn't fit that model. Feature-level targeting now controls where the flag is delivered:
- Editing and publishing permissions stay tied to the primary project.
- Add specific Targeting Projects, or target all projects.
- SDK connections scoped to the primary project or a targeted project receive the flag.
Scope individual rules
A rule's project scope limits that rule to selected projects within the flag's delivery set. Leave the rule unscoped to cover the full set. Its environment scope and targeting conditions still apply.
A rule scoped to a project outside the flag's delivery set has no effect.
Getting started
Sharing needs at least two projects. On current plans, Free includes one project and Pro includes three.
- Open a feature and choose its destinations with Targeting Projects.
- To narrow a rule, set its project scope beneath the rule's environment scope.
- Before publishing, check that you can target each destination project and whether its approval requirements apply.
Read the cross-project delivery guide.
