The Environments screen manages team-scoped environment variables and named environment overrides. Felan merges these values with integration secrets when preparing an agent runtime.
Default values and named environments
Use All Environments for default variables. Create a named environment when the same variable needs a different value for a target such as staging or production.
When a named environment is selected, default variables remain available and environment-specific overrides take precedence. You can create an override by editing a default variable in that named environment.
Manage variables
The screen supports:
- Adding plain-text variables and secrets
- Searching variables by name
- Filtering by variable type
- Showing or hiding stored values
- Editing names and values
- Moving a variable to a named environment
- Deleting variables
Variable names use uppercase letters, numbers, and underscores.
Keep credentials scoped
Create separate named environments when credentials or endpoints differ between targets. Store sensitive values as secrets, and use the narrowest access needed for the requested work.
Environment values can be made available to agent runs. Use dedicated non-production credentials where possible and rotate any credential that may have been exposed outside its intended scope.
