User Interface (UI) Overview

11 min

the floating server ui allows you to manage licenses efficiently you can activate and deactivate licenses (online, offline, air‑gapped) trigger synchronizations with the license api update server configuration review users registered to licenses and features licenses page the licenses page lists all licenses added to the server key actions add a license enter a license key or upload a license file activate / deactivate licenses online uses the license api directly offline / air‑gapped see offline & air‑gapped licensing below view details inspect license status, expiry, features, and usage see registered users click on a license to view users associated with that license and its features trigger a sync push local consumption data and pull updates (button located at the top right) offline & air‑gapped licensing use this page when the server cannot reach the license api directly supports generating and uploading activation/deactivation files or codes for offline and air‑gapped environments refer to the respective endpoints for detailed workflows configuration page adjust server level settings that affect synchronization, connectivity, and other global options periodic synchronization the server automatically synchronizes with the license api to maintain a consistent state during synchronization sends local consumption data to the license api pulls license updates, including status, features, expiration dates, and usage limits how to configure synchronization set the sync period on the configuration page use sync data (top right) to trigger a manual synchronization at any time using the swagger page the swagger interface allows you to test api endpoints directly example adding a license fill out the required fields in the request body click execute if successful, the server will return the appropriate response authorization look for the small lock icon 🔒 (or authorization icon) on the right side of the endpoint click it and provide your jwt token in the format bearer \<your jwt token> bearer \<your jwt token> using cli instead of swagger after testing an endpoint in swagger, you can switch to the command line interface (cli) copy the equivalent curl command generated by swagger (visible below the response section) paste it into your terminal to execute the same request