Self-Service Apps
Self-Service Apps lets the people who use your endpoints install approved software themselves. You build catalogs of Windows, macOS, and custom apps and assign them to tags. People on those endpoints open App Catalog in the TridentStack Control app and install what they need. They do not need admin rights or a help desk ticket. Each app either installs as soon as someone asks for it or waits for your approval.
Turn on Self-Service Apps
Open Orchestration > Self-Service Apps. An administrator turns the feature on or off for the whole organization with the Self-Service Apps switch at the top right of the page, next to a label that shows whether it is On or Off. Both directions ask you to confirm first. Turning it off removes App Catalog from every endpoint and nothing new installs from it, but nothing else changes: your catalogs, their apps and tag assignments stay as they are, and requests waiting for approval or install are kept. When you turn it back on, those requests continue where they left off. Requests still expire 30 days after they were made.
Self-Service Apps requires a verified organization. Until your organization is verified, the switch is unavailable and the help icon next to it explains why.
Create a catalog
On the Catalogs tab, select New Catalog and give it a name and an optional description. A catalog only reaches endpoints while it is enabled: use the Enabled checkbox under the catalog's name, then Save Changes, which also saves its name and description. Tags and apps save as soon as you change them. You can duplicate a catalog to start a new one from its apps, or delete one you no longer need.
Add apps
Open a catalog and select Add Application. Choose a package from the Windows (winget) or macOS (Homebrew) catalog, or from your custom packages. Review its details, set its install mode and other settings, then select Add Application to save it. Apps already in the catalog are marked and cannot be selected. You can also add an app from Update Management > Package Catalog: use Add to self-service catalog... on a custom package's menu, or on a winget or Homebrew app's details.
Select an app in the catalog's list to see its settings, then select Edit Application to change them and select Save Changes. You can also remove the app from the catalog there. For each app you can set:
- Install mode: Install on request or Requires approval (see below).
- Version: Latest at install installs the newest version once, when someone installs the app. Specific version always installs the version you pick from the app's available versions. Neither setting updates the app afterwards: see Keep installed apps updated. Homebrew apps always install the latest version.
- Allow reinstall: lets people reinstall an app that is already installed, for example when it stopped working. Uninstall from App Catalog is coming later.
- App Catalog Display: off by default, so App Catalog shows the app's standard name and publisher. Turn on Customize to set your own name, description, and category.
Remote-access tools, such as AnyDesk and TeamViewer, start as Requires approval when you add them, so a request is reviewed before anything installs. You can change this to Install on request on the app's page.
Install on request or require approval
- Install on request: the app installs as soon as someone selects Install in App Catalog.
- Requires approval: the person selects Request, adds an optional reason, and the request waits on the Requests tab until an administrator approves or declines it.
Choose which endpoints see a catalog
Assign tags to a catalog. An endpoint sees every enabled catalog that any of its tags reaches, and only the apps for its own platform. The catalog page shows how many endpoints the tags reach.
You can also work from the tag side: open the tag under Tags and use its Self-Service Apps card to add or remove catalogs, then select Save Changes.
When two catalogs offer the same app to one endpoint, the stricter setting wins: Requires approval beats Install on request, reinstall is allowed only if every catalog allows it, and a specific version beats the latest available version. If two catalogs choose different specific versions, the endpoint gets the lower one and both catalogs show a warning.
Keep installed apps updated
A catalog installs an app, but it does not update it afterwards. An app installed from App Catalog falls behind as new versions come out unless an app update policy with a deployment ring keeps it current.
Each app shows whether an app update policy manages it, in the catalog's Updates column, on the app's page, and in the Catalogs list:
- Managed: an app update policy with an active deployment ring updates the app on every endpoint the catalog reaches. The details name the policy.
- Partly managed: some of those endpoints are covered and some are not, for example because a policy's tags reach only part of the catalog's endpoints.
- No schedule: a policy includes the app, but its deployment ring is paused, turned off, or missing, so no updates are installed.
- Not managed: no app update policy updates the app on these endpoints.
The Catalogs list shows how many apps in each catalog are not managed, and an endpoint's Self-Service tab notes any installed catalog app that no app update policy manages.
To fix it, select Manage updates... on the app. You can add the app to an existing app update policy, turn the app back on in a policy where it is switched off, or create a new app update policy for the catalog's tags on a deployment ring you choose. Each choice shows how many endpoints it fixes before you apply it, and the app's status updates once it is applied.
Windows apps that install for each user are updated only when Auto-install per-user app updates is turned on in the client settings, under Per-User Application Updates.
Review requests
The Requests tab lists the requests waiting for a decision under Needs approval, with the person who asked, the endpoint, the app, and their reason. All activity uses the same list and adds past requests, so it shows every request and its current status. The sidebar shows how many requests are waiting.
- Approve installs the app on that endpoint. If the endpoint is offline, the app installs when it comes back online.
- Decline asks for a reason, which the person sees in App Catalog. They can ask for the same app again whenever they need it.
- Cancel withdraws an approval that has not installed yet.
- On a computer, select several requests to approve or decline them together, up to 100 at a time.
Requests that nobody decides expire after 30 days. Removing an app from every catalog that reaches an endpoint cancels that endpoint's open requests for it.
The Requests tab works on a phone, so you can approve or decline requests one at a time from anywhere.
Get notified about requests
To get an email when someone asks for an app, open Settings > Notifications and turn on the Self-Service category. The Requests tab also offers to turn this on for you. Notifications are grouped, so a burst of requests sends one email listing them rather than one email each.
What people see in App Catalog
On Windows and macOS, the TridentStack Control app shows App Catalog in its sidebar whenever at least one app is available to that computer. Each app appears as a card with its icon, name, publisher, description, and version. People can search, filter by category, and filter by installed or available apps.
A card shows where the app stands: ready to install, waiting for approval, installing, installed, declined (with your reason), or failed with an option to retry. While a request waits for approval, or is approved but has not started installing, the person who asked can select Cancel request and confirm to withdraw it, then request it again later. People can switch between cards and a list, and App Catalog remembers their choice. While the computer is offline, the buttons are disabled. Status is shared by everyone who signs in to that computer, so a second person sees that a request is already waiting instead of asking again.
History
Each install from App Catalog appears in the endpoint's history as Application Install, requested by followed by the person's name and (App Catalog). The trigger shows App Catalog. The requester's name is the one the computer reports for the signed-in user.