Personal vs. Workspace Environments: How They Work

An environment variable only matters as part of a named set you can switch between — “local,” “staging,” “production.” That named set is the environment. This page is about the environment itself as an object: who owns it, who can see it, and what happens when you switch, duplicate, or share one.

Personal vs. Workspace Scope

Every environment belongs to exactly one of two scopes:

PersonalWorkspace
Who can see itOnly its creatorEvery workspace member with read access
Who can edit itOnly its creator (or the workspace owner, for the scope change itself)Anyone with environment-management permission
Typical useYour own local credentials, a scratch environment for debuggingShared staging/production config the whole team relies on
Default when createdWorkspace, unless you explicitly choose personal—

A personal environment is invisible to everyone else — not “read-only to others,” genuinely absent from their list. This is deliberate: it’s the right place for a token or local override you don’t want to accidentally publish to teammates, without needing a separate “draft” concept.

Switching and Activation

Only one environment can be active per scope at a time: one active workspace environment, shared by everyone who hasn’t overridden it locally, and separately, one active personal environment per person. Activating a new one automatically deactivates whichever was active before in that same scope — there’s no state where two workspace environments are both “the” active one.

Which environment a given request actually uses to resolve {{variables}} is a per-browser choice on top of this, so switching your own active environment never changes what a teammate’s session is pointed at.

Moving an Environment Between Scopes

An environment can change scope after creation, but the two directions aren’t symmetric:

  • Personal → Workspace only requires owning the environment — anyone can publish their own personal environment to share it with the team.
  • Workspace → Personal requires being either the environment’s original creator or the workspace owner — converting a shared environment to personal removes it from everyone else’s view, so it’s gated more carefully. If the workspace owner does this to someone else’s environment, ownership stays with the original creator, not the owner making the change — the owner loses access to it too.

Duplicating an Environment

Duplicating always tries to create a workspace-scoped copy first. If you don’t have permission to create workspace environments, it falls back to a personal copy owned by you instead of failing outright — every member who can see an environment can always duplicate it into something they can work with. A duplicate never starts active, regardless of whether the source was.

Secrets and Who Can See Them

A variable marked secret (see Variables) stores and resolves the same way, but two separate things decide whether you specifically can see its real value in a given environment: whether you have read access to that environment at all, and — for workspace environments — whether your role includes permission to read secrets. Several default roles can fully read and edit a shared environment’s structure but still can’t see decrypted secret values; see Workspace Roles and Permissions for exactly which ones.

Managing Environments in HTTP Titan

The environment manager (the dropdown next to the active-environment indicator) lists workspace and personal environments in separate groups, lets you create either kind, duplicate or delete the selected one, and flip its scope inline — locked with a tooltip explaining why when you don’t have permission. Which actions are available follows the same environment.workspace.* and environment.personal.manageOwn permissions used everywhere else in the product.