Environment Behavior

Environments are fully isolated

Lens treats each environment as a separate world. Feedback submitted against staging will never appear in production, and feedback submitted against production will never appear in staging or preview environments. If you are looking for an item that you cannot find, the most likely cause is that you are looking at the wrong environment, not that the item was deleted.

Outcome

You will understand why Lens can behave differently across production, staging, and preview environments, and why “the same site” does not mean “the same feedback stream.” This page is the single most important concept to internalize before scaling Lens across a team: most “missing feedback” and “Lens looks broken” reports come from environment confusion rather than from real defects.

Why This Matters

Lens is environment-specific by design. A team reviewing staging should not assume that the feedback items, widget state, or settings they see will automatically appear in production. Each environment maintains its own:

• Feedback inbox and item history
• Widget enabled or disabled state
• Install configuration and credentials
• Status, comment, and assignment history
• Export and import boundaries

The reason for this strict isolation is that production feedback and pre-release feedback have very different audiences, retention needs, and escalation paths. Mixing them would make it impossible to tell whether a reported issue affects real users or only a staging branch.

How Feedback Flows Across Environments

The diagram below shows how feedback streams are kept separate at the source and only converge inside the TMXIO Lens inbox, where they are immediately filtered back apart by environment.

flowchart TB
  subgraph Production
    PWP[Production WP] --> PFB[Production feedback stream]
  end
  subgraph Staging
    SWP[Staging WP] --> SFB[Staging feedback stream]
  end
  PFB -.-> |never crossed| SFB
  PFB --> TMXIO[TMXIO Lens inbox]
  SFB --> TMXIO
  TMXIO --> Filter[Filter by environment]

The dotted line is the important part. The two feedback streams enter the same TMXIO product, but they are never merged. Every view, every export, and every status change is scoped to a single environment.

What Is Isolated Per Environment

The table below summarizes what is separated. If you need any of these to be shared across environments, the answer is almost always “no, you need to switch environments” rather than “we can merge them.”

Area	Isolated per environment	Notes
Feedback items	Yes	An item submitted in staging will never appear in production.
Widget enabled state	Yes	Lens can be enabled in staging but disabled in production, or vice versa.
Install configuration	Yes	Credentials and install paths are scoped to one environment at a time.
Statuses and comments	Yes	Status changes only apply to the item in its own environment.
Exports	Yes	An export reflects one environment at a time.
Imports	Yes	Imports must target a specific environment; cross-environment imports are not supported.
User access	No	Access is granted at the site level; a reviewer can see every environment they have access to.

Common Effects

When teams forget about environment isolation, the same handful of symptoms appear. Recognizing them early saves a lot of support time.

• Feedback exists in one environment but not another, and a reviewer thinks the item was deleted.
• The widget is enabled in staging but unavailable in production, and the team thinks Lens is broken.
• A reviewer leaves feedback in production by accident when they meant to review staging, and the item ends up in front of the wrong audience.
• An export taken from staging is assumed to represent production state.
• A status change in one environment is expected to “carry over” to the same logical issue in another environment. It does not.

Working With Environments Cleanly

Use the following habits to keep environment confusion out of your review sessions.

1. Name the environment before each review session. Say “we are reviewing staging” out loud before opening the inbox. This catches a surprising number of mistakes.

2. Confirm the dashboard header matches. The TMXIO header shows the active environment. If it does not match what your team just agreed on, switch before doing anything else.

3. Filter the inbox by environment. Even though items are already scoped, applying the environment filter explicitly makes it obvious in screenshots and shared links.

4. When something looks wrong, switch environments first. Before opening a support escalation, switch to a different environment. The item is usually there.

What Success Looks Like

• Your team can explain which environment any given feedback item belongs to without checking.
• Review sessions stay tied to one intentional environment from start to finish.
• “Missing feedback” reports drop to near zero, because reviewers know to check environment first.
• Exports, escalations, and status changes all carry the right environment context.

Related

Get started with Lens

Review and triage feedback

Lens settings in TMXIO

Troubleshooting