Shared Environment synchronization lacks granular permission boundaries for secret variables

Goal

Enable team collaboration through Shared Environments while preventing sensitive variables from synchronizing to every device linked to a single user account.

Constraints and uncertainty

Insomnia's Shared Environments synchronize all variables across all devices authenticated to the same user account. There is no documented mechanism to mark individual variables as non-syncable or to restrict synchronization scope within a shared workspace. Private Environments remain local-only, but they cannot be shared across team members. The absence of granular role-based access control means any variable added to a Shared Environment—including API keys, tokens, or passwords—is automatically uploaded to the provider's cloud storage and replicated to every signed-in device.

Questions

1. Is there a supported configuration or variable metadata flag that excludes specific keys from cloud synchronization while keeping them in the Shared Environment?
2. Can a workspace be structured so that secret variables reside in a Private Environment yet remain referenceable by requests shared via the workspace JSON export?
3. Does the application provide an audit log or synchronization status indicator that confirms which variables have been uploaded to the cloud versus kept local?