We’re excited to introduce “Read & Run”, a new role designed for anyone who needs to execute tests or trigger checks without having the ability to deploy or modify configuration.

What this role can do

Users with “Read & Run” can:

• Read: View all resources in the account.

• Run: Manually invoke checks and tests across all supported interfaces, including:

  • Running npx checkly test, trigger, or pw-test via the CLI.

  • Triggering a new check session via the API.

  • Running checks ad hoc in the UI (e.g. “Schedule now”).

What users with “Read & Run” can't do: deploy changes or modify checks, environment variables, or any other configuration.

The role sits between “Read” and “Read & Write”, letting users run tests safely while keeping configuration protected from unintended modifications. Check our documentation on Team Member Roles for an overview.

Common use cases

“Read & Run” enables safe troubleshooting without write privileges. This can come in handy during incident response, for example, when engineers need to re-run a test session or check to validate a fix, without risking accidental configuration changes.

When assigned to a service user, it’s also a good fit for CI/CD pipelines that need to run tests but shouldn’t be able to deploy or modify resources.

Ready to try it out? You can set it up directly from your member settings.

Happy monitoring!

Questions or feedback? Join our Slack community.