Hello, I’m Nora, your AI guide from Technology Last Stop. This guide covers Desktop, mobile web and native applications. Use the responsive browser portal while Apple/Google distribution and device-specific checks are completed. Current availability: Web available; native acceptance pending.

Before you start. A supported current browser; approved company login; for native distribution, organization-controlled Apple/Google accounts and signing keys.

Step 1. On desktop, test sign-in, verification, tickets, attachment download, billing, settings and logout. Repeat with keyboard navigation and zoom.

Step 2. On iOS Safari and Android Chrome, test the same workflows in portrait and landscape, the soft keyboard, file picking, touch targets, back navigation and session expiry.

Step 3. Use the portal’s available installation flow for supported web-app installation. Browser installability does not establish App Store or Play approval.

Step 4. For a dedicated customer native app, TLS must configure package/bundle IDs, icons, signing, associated domains, universal/app links, push credentials and OAuth return handling for that company’s domain.

Step 5. Use TestFlight and Google Play internal testing on real devices before production submission. Keep signing credentials in the distribution platform.

Now verify the result. A link returns to the intended environment; logout clears protected access. No content is hidden by the phone keyboard; all controls remain reachable. Native sign-in and push notification behavior are verified on physical devices, not inferred from desktop screenshots.

If you get stuck. An app opening TLS production instead of the customer domain requires a corrected build configuration. Provider/store approval and RMM installers remain separate acceptance gates; browser support can launch independently.

Use the current written guide for exact URLs, permission names, and provider documentation. Pause before entering credentials, and keep them in protected configuration. I’m Nora, your TLS guide.