Lens Settings in TMXIO

Outcome

You will know which Lens settings live in TMXIO, what each one changes, and when changes here affect the site-side widget experience. This page covers the TMXIO control surface; the matching site-side install guidance lives in Lens for WordPress.

What This Area Controls

The Lens settings area in TMXIO is the platform-side control surface for the widget. It does not include design or workflow configuration; those live with the individual feedback items and with team triage habits. The table below covers the settings you are most likely to touch.

Setting	Default	What it changes	Where it applies
Lens enabled	Off	Turns the widget on or off for a specific environment of a specific site.	One environment at a time.
Widget visibility	Inherits enabled state	Controls whether the widget renders for visitors of the environment, even when Lens is enabled.	One environment at a time.
Install path	Default for the site type	Shows the current install guidance and any environment-specific overrides.	One environment at a time.
Credentials	Auto-generated on enable	The values the site-side install uses to authenticate to TMXIO.	One environment at a time.
Rotation	Not scheduled	Rotates the credentials used by the site-side install.	One environment at a time.
Reviewer access	Inherits site access	Which TMXIO users can see and act on Lens items for the site.	The site as a whole, across all environments.

Settings are per environment

With the exception of reviewer access, every setting on this page applies to one environment at a time. Enabling Lens on staging does not enable it on production. Rotating credentials on production does not rotate them on staging. See Environment behavior.

When to Use This Area

Most teams visit Lens settings rarely; the area is for setup, recovery, and credential maintenance rather than day-to-day work. Use it when one of the following is true.

• Lens is enabled in principle but the widget is not behaving the way the team expects.
• You need to confirm the current install path for a specific environment.
• You need to update the site-side Lens setup after a change to credentials or hosting.
• You are onboarding a new site and need to enable Lens for the first time.
• Support has asked you to rotate credentials as part of an incident response.

Enabling Lens on a New Environment

The first time you enable Lens on a given environment is the moment most likely to surface install issues. Run the steps below in order.

1. Switch to the target environment. Confirm the dashboard header shows the right environment before changing any setting.

2. Toggle Lens on. This generates the credentials the site-side install needs.

3. Open the install guidance. Follow the steps for the site type. See Lens for WordPress for the WordPress-specific path.

4. Load the site and verify the widget. Open the environment and confirm the widget appears and responds.

5. Submit a test feedback item. Use a real piece of feedback if possible; placeholder test items are easy to forget about later. Confirm the item appears in the TMXIO Lens inbox for the same environment.

6. Document the install. Note the environment, the date, and the person who enabled it. This helps later when credentials need to be rotated.

Rotating Credentials Safely

Credential rotation is the most disruptive setting change. Treat it like a small change window rather than a casual click.

1. Tell the team. Brief reviewers that the widget may go quiet for a few minutes on the affected environment.

2. Run the rotation. Generate new credentials in TMXIO for the specific environment.

3. Update the site-side install. Apply the new credentials immediately. The widget will be unavailable until this is done.

4. Verify. Load the site in the affected environment and confirm the widget is working again. Submit a quick feedback item and confirm it appears in the inbox.

5. Record the rotation. Note the date, the environment, and the reason. Future rotations are easier when there is a history to refer to.

What Success Looks Like

• Every environment that should have Lens enabled does, and every environment that should not, does not.
• Install guidance is followed end-to-end rather than partially.
• Credential rotations are deliberate and recorded, with no surprise gaps in widget availability.
• When something looks wrong, the team checks settings here before assuming a deeper problem.

Related

Get started with Lens

Environment behavior

Troubleshooting

Lens for WordPress