Workspace Weekly: 6.5 features – Launcher Access Control and Application Test Reporting

February 26, 2026

This week’s focus is on two areas that matter more as your Login Enterprise usage grows: controlling who can use shared test infrastructure and making Application Test results easier to share and automate.

Login Enterprise 6.5 adds access control to launchers and launcher groups, plus improvements to application test PDF reporting, including custom text and Public API support.

Together, these help you run Login Enterprise across multiple teams with fewer surprises, clearer ownership, and reports that carry the story alongside the data.

ACL on Launchers and Launcher Groups: Better control, cleaner resource ownership

As soon as more than one team uses the same appliance, launchers become shared infrastructure.

Awkward problems start here: the wrong team selects the wrong launcher group; resources get consumed unexpectedly, and people spend time untangling who ran what, where.

In 6.5, you can assign roles to launchers and launcher groups. The UI then shows only the launchers and groups that the signed-in user has access to, while admins can still manage everything centrally.

This makes it easier to keep environments organized by team, function, geography, or customer, without needing separate appliances for every use case.

What it means for you

• Cleaner operator views that show the launchers that matter for their work.
• Better resource ownership, so teams don’t accidentally consume others’ test capacity.
• Improved security posture by limiting visibility into infrastructure details.

How it works

• Launchers are now managed as first-class objects with a dedicated overview page.
• Offline launchers are visible, with an online or offline status and a last state change timestamp.
• You can show or hide offline launchers to keep the table focused.
• Roles can be assigned to launchers from the Launcher page, and in bulk from the Roles page.
• Launcher groups now have dedicated create and edit pages rather than popups.
• When building a group by selecting launchers, users can only add launchers they have access to.
• When using group filters, the group editor shows only the launchers the user can see. Tests may still use additional launchers at runtime based on the filter logic.

Imagine if you are

A platform team supporting multiple departments on one appliance. You create separate launcher groups for security testing, EUC Operations, and app packaging, then restrict access, so each role only sees and uses its own launchers.

The platform team keeps full visibility, while day-to-day users stop tripping over shared infrastructure or picking up the wrong resources by accident.

For more information, refer to: ACL on Launchers and Launcher Groups

Click to View Details

Figure 1: ACL assignment configuration for Launchers

Application Test PDF Reports: Add custom text, and generate reports via API

Application test PDFs are often shared outside the team that ran the test. That is where raw charts are not enough.

Stakeholders want to know what was tested, why it matters, and what you recommend.

In 6.5, Application Test PDF reports now support custom text. You can add a short management summary, scope notes, or conclusions at the beginning of the report so that the PDF delivers a clear narrative rather than a raw export.

Click to View Details

Figure 2: Setting Application Test custom PDF text

Version 6.5 enables application test PDF generation and download through the Public API, including multi-run comparison reports. This makes it easier to integrate Login Enterprise reporting into ticketing, change management, or CI-style workflows.

What you get

• A simple way to add context to PDFs without editing them after export.
• More consistent reporting for recurring tests, releases, or weekly checks.
• A path to automate report generation and distribution using the Public API.

How it works

• In application testing results, generate a PDF report and choose what to include.
• Enable custom text to open a lightweight editor with basic formatting options.
• Your text appears at the beginning of the report under the standard introduction.
• For automation, use the Public API to generate and download application test PDF reports, including reports that compare multiple application test runs.

This means you can move from manually downloading PDFs to fully automated reporting tied to releases, infrastructure changes, or weekly operational checks.

Automate Application Test PDFs with the Public API

If you want reporting to flow into ticketing systems, CI jobs, or scheduled checks, you can generate and download Application Test PDFs directly through the Public API.

To use this, you need:

• Your appliance URL
• A Public API bearer token
• One or more application test run IDs

To generate a token and review the API reference, see: Using the Public API

The easiest way to get a test run ID

1. Go to Application Testing results
2. Click into a specific Application Test result
3. Copy the GUID at the end of the browser URL

Example:

https://your-appliance-url/application-testing/results/952eef25-d210-46f6-bb67-e83b45d9111e

The GUID at the end is the Test Run ID.

Example: Download Application Test PDFs via PowerShell

Paste the script below into PowerShell (5.x or 7.x both work). Replace the placeholders with your own values.

$baseUrl = "https://your-appliance-url"
$token   = "YOUR_BEARER_TOKEN_HERE"
$runIds  = @(
  "00000000-0000-0000-0000-000000000000"
  # Add more IDs on new lines if needed
)

foreach ($runId in $runIds) {
    $outFile = "AppTestReport_$runId.pdf"
    Invoke-WebRequest -Method Get -Uri "$baseUrl/publicApi/v8-preview/reports/application-test-runs/pdf?testRunIds=$runId" -Headers @{Authorization="Bearer $token";Accept="application/pdf"} -OutFile $outFile
}

What this does:

• Downloads a PDF for each Test Run ID
• Saves the file to your current PowerShell working directory
• Names each file using the Test Run ID

If you want to control where the file is saved, change the $outFile line to include a full path, for example:

$outFile = "C:\Reports\AppTestReport_$runId.pdf"

Pop this into PowerShell and see it in action.

For more information, refer to: Custom text in Application Test PDF reports & Generating Application Test PDF reports via Public API

This is especially useful for bulk archiving, scheduled exports, or for stakeholders who need reports without logging into the web interface.

Ready to get started using 6.5?

Upgrade your appliance and launchers, then follow the documentation above to tighten access around shared Launcher infrastructure and start producing Application Test reports.

To set up a new appliance or update an existing one, go to Downloads. If your Appliance already exists and is internet-connected, follow Updating Login Enterprise (there are additional update steps here). Don’t forget to take a snapshot first.

As always, thank you for your feedback! We use your insights to make Login Enterprise better for you.

Stay tuned for more Workspace Weeklies and join our Slack channel #workspace-weekly to share field stories, tips, and interesting finds.