This is a walkthorugh of the io.Manager Admin UI and how to do some simple task in it. The versions from the screenshots are io.Manager Server 4.0.4, Admin UI 4.0.2.
1. Аdd an app
In Apps → List, choose Import Definitions. Manager stores app definitions; the application itself must already be hosted somewhere the user can reach.
Importing an app definition does not deploy the web application or start its server. Verify the URL from the end-user machine. See application definitions.
Paste an array of app definitions
Paste the JSON, leave Skip validation unchecked, and click Continue. This example registers client-contact-tour against the running local demo server. Use your deployed app URL in a real environment.
Use an array even for one definition. The technical name client-contact-tour is distinct from the display title Client Contact Tour; the refresh command later uses the technical name. The screenshot uses http://localhost:22080/clpc/dist/#/clientcontact/, which requires the local demo server. Substitute a URL reachable from your target client when following this with your own app.
Set app visibility
The next page is Define access. You can keep the app as public or make it available only to selected users or groups.
With Public App Off, add Credit desk under Groups, then Continue. This is an app-access group. It is not a Manager administration permission group.
Credit desk controls app access here; IO_MANAGER:* groups control administration. See Manager authorization.
Review definition and access together. The intended result is public: false with Credit desk in accessList. Complete the import, then click Finish on the success page before checking the stored app.
2. Give the end user group membership
Open Users → All Users → demo-user → Info. Add Credit desk under Groups. The user remains a non-admin; no IO_MANAGER permission or GLUE42_SERVER_ADMIN group is assigned.
Verify effective app access
If Desktop does not receive the expected definition, check the signed-in identity, group membership, Manager app-store feature and polling interval. Local app stores may also supply applications independently. See the Desktop Manager connection.
3. Review incoming feedback
In io.Connect create a Feedback Report and submit it. Then back in io.Manager Open Diagnostics → Feedback Reports and open its ID to inspect it. You can follow the report’s user and session.
See Manager diagnostics.
4. Explore a current session
Switch to Users → Sessions and select a session.
The session detail page identifies Desktop 10.5.2 and the MANAGER-DEMO / LOCAL environment, together with machine, OS and display information. This page does not show a historical memory chart.
Compare performance over time when telemetry is available
io.Insights publishes metrics, traces and logs using OpenTelemetry so you can use it for diagnosing reported issues and user behavior. See io.Insights architecture and visualization.
5. Get logs from the correct session
Open Diagnostics → Commands → Add Command. Select io.Connect Desktop, GetLogs and your user’s compatible target session. For more details see Command Center.
6. Request a live system-information snapshot
Choose GetSystemInfo, select the target session and click Create. This gathers running-app and resource information from that client.
Inspect the returned JSON
Open the command ID after execution. This actual result contains version, environment, perfData and Workspace information for the selected session. Treat memory values as a snapshot. Trend analysis requires repeated measurements with a known time range.
7. Refresh only the application you intend
Add a RefreshApps command for the same session. Use {"apps":["client-contact-tour"],"windows":,"autoStart":false}.
The response lists the refreshed sample instance, has no failed entries and has an empty started array.
8. Check Layout access
Advanced Layouts distinguish private (owner visibility), shared (owner and specified users or groups) and public (all users). Editing rights are separate from visibility. Layout sharing requires enabling advanced Layouts on both io.Manager and io.Connect Desktop; support was introduced with io.Manager 4.0 and io.Connect Desktop 10.5. See Layout sharing and access and Desktop configuration.
More to try
- Share a working setup with colleagues: Layout & Workspace Sharing Implementation Tips
- Investigate an application failure: Track down issues fast with io.Insights