Environment variables and secrets

Overview

Environment variables let you pass sensitive information—API keys, passwords, authentication tokens—to your Projects without exposing them in your code. Use them to authenticate with external services, configure different settings for development versus production, or share configuration across multiple Projects.

How it works

Environment variables are defined at either the Project level or workspace level. Variable hierarchy: Project-level variables take precedence over workspace-level variables. If you define the same key at both levels, the Project-level value is used. This lets you set workspace-wide defaults while allowing individual Projects to override specific values. Environment targeting: Each variable can target three contexts: Online IDE (development), deployed Projects (production), or both. Use different API keys or configuration for development versus production.

Usage

Project-level environment variables

Project environment variables are scoped to a single project. Manage them via the dashboard at https://app.intuned.io/projects/{project-id}/env-vars or with the CLI from your project directory.

Create an environment variable

Dashboard
CLI

Select New and provide a key, value, and optional description. Choose where to expose it: Online IDE, deployed Projects, or both.

Deployed environment variables require redeployment to take effect. When developing locally via CLI, see Local development.

To use different values per environment, create two variables with the same key and select the appropriate environment for each.

Create Environment Variable Different Values

Run from your project directory (where Intuned.json is located), or specify the project explicitly with -p <project-name>.

intuned platform env-vars create --key MY_VAR --value my-value

Use --envs to target specific environments (comma-separated). Supported values: PUBLISHED, AUTHORING. Defaults to PUBLISHED.

# Create for both environments
intuned platform env-vars create --key MY_VAR --value my-value --envs PUBLISHED,AUTHORING

# With a description
intuned platform env-vars create --key MY_VAR --value my-value --description "My API key"

# Specify project explicitly
intuned platform env-vars create -p my-project --key MY_VAR --value my-value

To use different values per environment, create two variables with the same key using --envs to target each environment separately.

Deployed environment variables require redeployment to take effect. When developing locally via CLI, see Local development.

See Env Vars Create for all options.

Edit an environment variable

Dashboard
CLI

Select … > Edit next to a variable to update its key, value, or environments.

Run from your project directory (where Intuned.json is located), or specify the project explicitly with -p <project-name>.

intuned platform env-vars update MY_VAR --value new-value

See Env Vars Update for all options.

Delete an environment variable

Dashboard
CLI

Select … next to the variable you want to delete, then select Delete. Confirm when prompted.

Run from your project directory (where Intuned.json is located), or specify the project explicitly with -p <project-name>.

intuned platform env-vars delete MY_VAR

Add --force to skip the confirmation prompt:

intuned platform env-vars delete MY_VAR --force

See Env Vars Delete for all options.

Workspace-level environment variables

Workspace environment variables are defined at the workspace level and exposed to all Projects in that workspace.

Dashboard
CLI

Go to https://app.intuned.io/settings/env-vars to manage workspace-level variables.Access them from within a project by selecting Shared variables in the Environment Variables tab.

Alternatively, go to side panel > Workspace Settings > Environment Variables.

Workspace Level Environment Variables Side Panel

Manage workspace-level variables with the workspace env-vars subcommands:

# List workspace env vars
intuned platform workspace env-vars list

# Create a workspace env var
intuned platform workspace env-vars create --key SHARED_KEY --value shared-value

# Update a workspace env var
intuned platform workspace env-vars update SHARED_KEY --value new-value

# Delete a workspace env var
intuned platform workspace env-vars delete SHARED_KEY

See Workspace Env Vars for all options.

Local development

When developing locally via CLI, the CLI reads .env files and system environment variables.

.env

TEST_VAR=local_value

.env files are for local development only and aren’t deployed. Before deploying, configure your environment variables using the dashboard or CLI commands above.

Online IDE

Develop on Intuned with zero config

CLI

Develop locally with your favorite IDE and tools

Getting started

Intuned Agent

Platform features

Learn

How-To

Integrations

References

Resources

Environment variables and secrets

Overview

How it works

Usage

Project-level environment variables

Create an environment variable

Edit an environment variable

Delete an environment variable

Workspace-level environment variables

Local development

Online IDE

CLI

Getting started

Intuned Agent

Platform features

Learn

How-To

Integrations

References

Resources

​Overview

​How it works

​Usage

​Project-level environment variables

​Create an environment variable

​Edit an environment variable

​Delete an environment variable

​Workspace-level environment variables

​Local development

​Related resources

Online IDE

CLI

Overview

How it works

Usage

Project-level environment variables

Create an environment variable

Edit an environment variable

Delete an environment variable

Workspace-level environment variables

Local development

Related resources