Concepts Overview

How Flipswitch organizes flags, environments, and permissions

Flipswitch organizes feature flags in a hierarchy:

Organization
├── Project (e.g., "Web App")
│   ├── Environment: Development
│   │   └── Flag rules + API keys
│   ├── Environment: Staging
│   │   └── Flag rules + API keys
│   └── Environment: Production
│       └── Flag rules + API keys
├── Project (e.g., "Mobile App")
│   └── ...
└── Segments (reusable across projects)

Key Concepts

Organizations

The top-level container. An organization has:

  • Members - Users who can access projects
  • Groups - Collections of users with shared permissions
  • Projects - Containers for flags

Projects

A project typically represents an application or service. Each project contains:

  • Flags - Feature flags with their definitions
  • Environments - Isolated configurations (dev, staging, prod)
  • Segments - Reusable targeting groups

Environments

Environments let you configure flags differently for each deployment stage:

EnvironmentPurpose
DevelopmentLocal testing, all features enabled
StagingPre-production validation
ProductionLive user traffic

Each environment has its own:

  • Flag states (enabled/disabled)
  • Targeting rules
  • API keys

Flags are defined at the project level, but their rules and states are configured per environment.

On this page