Workspace Weekly: 6.3 feature – Assign roles to individual Test Runs
October 14, 2025
This week’s Workspace Weekly digs into a 6.3 feature that continues solving a problem we hear about constantly: granular access control.
You can now give teammates access to specific Test Runs instead of dumping an entire Test history on them.
What does this mean in short? Tighter security, faster reviews, and less confusion when you’re trying to troubleshoot something.
Check out this doc for step-by-step direction: Assign roles to individual Test Runs
Figure 1: Showing the Managing Access to Test Runs flow
What it means for you
Right now, sharing usually means all-or-nothing. Your security team probably doesn’t need to see every run from the last six months, they just need last night’s data. Share information that is immediately actionable, for example, if the assigned project team wants a specific regression snapshot.
What about an external auditor? They definitely don’t need full access to everything. Per-run access fixes this. Instead of “Here’s the whole test, good luck finding what you need”, you can say “Here is the run you asked for”. For you this also means least-privilege access, faster collaboration, and fewer opportunities for something to be accidentally broken.
What you get
- Faster reviews: send people straight to the evidence they need.
- Better compliance: show auditors exactly what they need to see, nothing more.
- Lower risk: stop exposing unrelated data during incident response.
How it works
- Single run: Open a Test Run, hit the Access tab, and add the roles you want.
- Bulk access: Head to Access Control > Roles > Test Run Access to add multiple runs to a role at once. There’s a toggle to hide inherited runs, so you’re only looking at what you’ve explicitly granted.
- A few things to know: You can’t remove roles inherited from the parent Test at the run level. If you delete the Test, those inherited roles become editable. And every run needs at least one role – you can’t accidentally lock everyone out.
This works for Load and Application Test Runs. Continuous Tests don’t create separate runs, so those stay managed at the Test level.
Check out how to use this feature in a demo:
Real-world examples
You’re a service owner and SecOps needs to review a spike. Add them to yesterday’s run only. They get what they need; you don’t have to worry about them poking around in old data or accidentally changing something.
Audit prep. Compliance wants proof from a specific two-week window. Share just those Test Runs with your Audit role. No over-sharing or endless email chains!
You run managed services, and a customer reports an issue during a change window. Grant them view access to the relevant runs so they can verify you fixed it without seeing your entire test setup and results.
Running a POC? Give your customer’s Tech Lead access to a handful of your best runs that show stability and performance for clean and focused proof points.
Quick tips
Figure out upfront who you would like to designate as “reviewers” versus “owners”, so your access model stays consistent. When you remove access, make sure at least one role stays on each run. Lastly, use the role-level Test Run Access tab to manage multiple runs at once and keep things organized.
Ready to try 6.3? Upgrade your appliance and launchers, then follow the doc to start assigning roles: Assign roles to individual Test Runs.
Next week’s Workspace Weekly will cover more features in our 6.3 release. Jump into #workspace-weekly on Slack to share your own tips and stories.
As always, we use our customers’ feedback to make Login Enterprise better for you. We hope you enjoy the value of these new releases’ features.
Workspace Weekly
