fix(secrets): keep readonly secret names legible instead of dimming them

[waleedlatif1]

Summary

• Readonly viewers saw a workspace secret's name at opacity-50 while the masked value next to it rendered at full opacity — an inconsistent, hostile treatment of content they need to read.
• Dropped the opacity dim on the non-renameable key field; non-editability is already conveyed by the read-only field and the absent Trash/rename affordances.
• The secret detail page was already correct (read-only fields at full opacity, copyable key), so this brings the list in line with it.

Type of Change

• Bug fix

Testing

Tested manually as a readonly workspace viewer — name and masked value now render consistently at full opacity, still non-editable.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Jun 10, 2026 5:47am

[cursor]

PR Summary

Low Risk
Single CSS class change on a read-only input; no permission or data-handling logic touched.

Overview
Read-only workspace viewers no longer see workspace secret names dimmed at half opacity in the secrets list.

WorkspaceVariableRow updates the key ChipInput styling when canRename is false: it drops opacity-50 and cursor-not-allowed, using cursor-text instead so names match the full-opacity masked value beside them. Rename/delete restrictions are unchanged (readOnly, focus guard, missing trash).

^{Reviewed by Cursor Bugbot for commit f9e85bf. Configure here.}

[greptile-apps]

Greptile Summary

This PR removes opacity-50 from the read-only secret name field in the workspace secrets list, so the key name renders at the same full opacity as the masked value beside it. The cursor-not-allowed is replaced with cursor-text to signal that the text is selectable/copyable even though it isn't editable.

• The single-line class change in WorkspaceVariableRow drops opacity-50 cursor-not-allowed in favor of just cursor-text when canRename is false, bringing the list row in line with the detail page which already renders read-only fields at full opacity.
• No logic or data-flow changes are made; the field remains readOnly and all rename/delete affordances are still hidden for viewers.

Confidence Score: 5/5

Safe to merge — a single Tailwind class swap with no logic changes, no data-flow impact, and no security implications.

The change is a one-line CSS class update on a purely presentational read-only field. It removes a visual inconsistency without touching any state, permissions logic, or API calls. The field remains non-editable for viewers; only the cursor style and opacity change.

No files require special attention.

Important Files Changed

Filename	Overview
apps/sim/app/workspace/[workspaceId]/settings/components/secrets/components/secrets-manager/secrets-manager.tsx	Removes opacity-50 cursor-not-allowed from the read-only key name field and replaces it with cursor-text, fixing the visual inconsistency where the secret name was dimmed while the masked value rendered at full opacity.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[WorkspaceVariableRow renders] --> B{canRename?}
B -- Yes --> C[ChipInput: no extra className\neditable, cursor-default]
B -- No --> D["ChipInput: className='cursor-text'\nreadOnly, full opacity\ntext is selectable/copyable"]
D --> E[No opacity-50 dim\nNo cursor-not-allowed]

Loading

_{Reviews (2): Last reviewed commit: "fix(secrets): use cursor-text on readonl..." | Re-trigger Greptile}

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit f9e85bf. Configure here.}