Skip to content

Key concepts

Term Meaning
Organization Your tenant. Everything you see and every device that connects belongs to one organization.
Personal workspace An organization of one person, created from Create an account. No SSO, SSO enforcement or SCIM.
Catalog The packages your organization allows. Only catalog packages can be approved.
Package An app, identified by its WinGet identifier, such as 7zip.7zip. It comes from the WinGet community source or from your own upload.
Version One version of a package. You approve or reject versions, not packages.
Trust state The result of the checks on a version: Checks passed, Findings, Scan failed, Not scanned or Scanning…. See Checks and trust states.
Approval Your decision on a version: Pending review, Approved, Rejected, or Blocked by a finding.
Source Your organization’s WinGet REST source at /api/winget/t/{key}. It serves approved versions only.
Source key The secret part of your source URL, starting ews_. One per deployment channel. Revoke it to cut off the devices that use it.
Agent The optional EndpointWorks Windows agent. It reports installed software (Business and up) and, in Managed mode, applies approved changes (Premium).
epw The command line that ships with the agent. It works like winget against your catalog, but every change is a request the server decides.
Enrollment token A token, starting ewe_, that lets the agent enroll a device. It can only enroll, within the limits you set.
Baseline A named, ordered set of catalog packages, published as numbered revisions.
Finding Something a check found, with a severity from Low to Critical.
Advisory A known issue you record for a package and version range.

EndpointWorks connects to devices in two ways.

  • CLI-based, on every plan. Devices run plain winget against your source. No agent.
  • Agent-based, on paid plans. The agent reports what is installed, and in Managed mode keeps catalog packages on the approved version.

See Choose how to connect devices.