Skip to content
Documentation

Company Apps and Scripts

Application Manager gives you three ways to deploy software to Windows endpoints: Company Apps, Scripts, and Repository Apps. Choosing the right type saves time and reduces maintenance overhead — understanding the differences is the first step.

The three app types

Section titled “The three app types”

Company Apps

Section titled “Company Apps”

Company Apps are installer files you upload yourself — MSI, EXE, or similar. Use them for in-house applications, licensed software that cannot be distributed through a public catalog, or any application that CapaOne does not already include in its Repository.

You control the version entirely. When a new release of the software is available, you upload the new installer and update the app entry manually.

Company Apps and Scripts share a 100 GB storage quota per organization, shown as a progress bar at the top of both tabs.

Scripts

Section titled “Scripts”

Scripts are PowerShell or other shell scripts that run on assigned endpoints. Use them for configuration tasks, one-off fixes, system checks, or anything that is not a traditional installer. Like Company Apps, scripts are versioned and go through the same release status workflow.

Repository Apps

Section titled “Repository Apps”

Repository Apps are a curated catalog of common applications maintained by CapaOne, with versions sourced automatically from winget. See Repository Apps for the full catalog behavior.

Powerbricks

Section titled “Powerbricks”

Powerbricks are CapaSystems-maintained PowerShell building blocks that you can use in both Company Apps and Scripts. Each Powerbrick is a ready-made script component covering a common task — such as installing software silently, configuring Windows settings, or handling prerequisites — so you do not have to write everything from scratch.

Use Powerbricks to speed up script authoring and reduce errors. You can combine multiple Powerbricks into a single script or embed them in a Company App’s install logic.

Release status workflow

Section titled “Release status workflow”

Both Company Apps and Scripts use a two-stage release status:

  • Testing — the app or script is deployed only to endpoints explicitly assigned during testing. Use this to validate behaviour before rolling out broadly.
  • Released — the app or script is available for production deployment.

Promote an app from Testing to Released once you have confirmed it installs and behaves correctly. Keeping unvalidated software in Testing prevents accidental rollout to the full fleet.

Monitor patch compliance

Section titled “Monitor patch compliance”

The Overview tab gives a fleet-wide view of application patch status:

  • Patch Percentage — the share of required patches that are currently installed across all endpoints. A low percentage means many endpoints are running outdated software.
  • Repository Apps Compliance — per-application breakdown showing which apps have updates available, which are up to date, and which are not installed.
  • Patch Compliance History — trend over time so you can see whether compliance is improving after a patch deployment.
  • Repository Apps Updates Available — which specific apps have outstanding updates, and how many endpoints are affected.

Use the Overview tab regularly to identify which apps need attention and to confirm that a recent deployment raised compliance as expected.

Assign apps to endpoints or groups

Section titled “Assign apps to endpoints or groups”

Company Apps are assigned either to individual endpoints or to groups. Group assignment is the preferred approach for anything that should apply broadly — it means new devices that join the group automatically receive the software without additional steps.

Click the app name to open its detail page and manage group and endpoint assignments from there.

Good to know

Section titled “Good to know”
  • Storage is shared between Company Apps and Scripts. If you are running low, review old deprecated entries and remove those that are no longer needed.
  • Clicking endpoint or group counts in the app list navigates directly to the assignment details for that app, making it easy to audit which devices have a specific application.
  • Scripts can complement Company Apps — for example, a script can run pre- or post-installation checks alongside a Company App deployment using Automation workflows.
Section titled “Related”