Navigation and resource model
FlagTGL is organized as organization → project → environment → resource. An organization owns members, teams, tokens, billing, integrations, and the audit trail. A project owns environments, flags, segments, metrics, experiments, release controls, contexts, and event history. An environment isolates targeting state and SDK credentials so a test rollout cannot change production.
Find any feature
Open Dashboard, choose an organization, then select a project. The project sidebar is grouped by job:
| Area | Navigation | Use it for |
|---|---|---|
| Flags | Release → Flags | Flag values, targeting, prerequisites, rollouts, SDK delivery |
| Segments | Release → Segments | Reusable audiences across flags |
| Guarded rollouts | Release controls → Guarded rollouts | Metric-protected progressive delivery and rollback |
| Experiments | Release controls → Experiments | Hypotheses, treatments, allocation, metrics, results |
| Approvals | Release controls → Approvals | Pending, approved, rejected, scheduled, and applied changes |
| Workflows | Release controls → Workflows | Multi-stage release automation |
| Release pipelines | Release controls → Release pipelines | Reusable release stages and policy |
| Metrics | Release controls → Metrics | Conversion, count, numeric, and guardrail definitions |
| Context explorer | Runtime → Context explorer | People, tenants, devices, services, and custom contexts seen by SDKs |
| Live events | Runtime → Live events | Evaluation, identify, custom, metric, and diagnostic events |
| Integration configurations | Release controls → Integration configurations | Provider-specific configuration preserved during sync |
| Project settings | Settings → Project settings | Project, environment, SDK, flag, lifecycle, and approval defaults |
| Provider migration | Settings → Migrations | Connect, preview, migrate, and inspect reports for LaunchDarkly, Unleash, ConfigCat, or Flagsmith |
The environment selector changes the environment filter for flags, controls, contexts, and events. A resource marked Project-wide applies to every environment; otherwise its environment key is shown beside its status.
Roles
- Reader can inspect configuration, runtime data, and audit history.
- Writer can create and update flags and submit governed changes.
- Admin can manage organization settings, integrations, members, tokens, billing, projects, and destructive operations.
Every API request is scoped to an organization. Use the organization slug in /api/orgs/{org} routes and a numeric project ID in project routes. See authentication.