Schematic supports multiple environments (e.g. staging and production) to support your development workflow.

Resources in Schematic are predominately environment-scoped, but some are available account-wide (regardless of the selected environment). The table below highlights available resources and how they are scoped.

Resource typeAccount/environment scopeOriginates fromConcept exists inDefinition / Notes
EnvironmentAccountApp & APIApp & API
PlanAccountApp & APIApp & API
FeatureAccountApp & APIApp & API
Feature flagAccountApp & APIApp & API
Flag ruleEnvironmentApp & APIApp & API
Rule conditionEnvironmentApp & APIApp & API
API keyAccount and EnvironmentApp & APIApp & APIAPI keys are always environment-specific, but can be accessed in the Application account-wide.
CompaniesEnvironmentAPIApp & API
UsersEnvironmentAPIApp & API
EventsEnvironmentAPIApp & API
Plan entitlementEnvironmentApp & APIApp & APIAn association between a feature and a plan
Company overrideEnvironmentApp & APIApp & APIAn association between a feature and a company
Entity key typeAccountAPIApp & APIA type of key that can be used to look up an entity (user or company). For example, “email” or “id”
Entity key valueEnvironmentAPIApp & APIThe value for a given entity key, e.g. the value “” in the context of the key “email” as a lookup for a specific user
Entity trait typeAccountAPIApp & APIArbitrary data that can be attached to entities (Users/Companies), which can later be used for flag targeting via rule conditions. This model defines a type of trait, e.g. “location” being a string
Entity trait valueEnvironmentAPIAPIThe value for a given entity trait, e.g. the value “Atlanta, GA” in the context of the “location” trait for a specific
Metric countsEnvironmentAPIApp & APIThis is an aggregated count of events grouped by type/hour/company/user primarily used for rule-based targeting