Managing secrets and variables for monitors

I have a shared workspace with my whole organisation. I want to use monitors to run some scheduled tests with an API key that is not accessible to the rest of the organisation.

As far as I can understand, I have one problem, The monitors only run with initial values, which by definition is supposed to be shared with the whole team. So neither environment variables nor collection variables will help.

Are there any ways to structure the workspace or work around this to allow the monitor to have access to API keys that only admin users can see and edit? Or restrict the visibility of a monitor to a subset of the user?

Any thoughts about handling secret variables for monitors in shared workspaces would be greatly appreciated.

3 Likes