Hello, I’m Nora, your AI guide from Technology Last Stop. This guide covers Managed Support clients and Company Workspaces. TLS keeps owner controls while licensed company administrators manage their own company. Current availability: Implemented; paid workspace access enforced.

Before you start. TLS owner access and a clear product agreement for the customer.

Step 1. Choose Managed Support client for customers receiving TLS services with basic ticket, knowledge and own-device access. Their membership does not grant RMM or integration administration.

Step 2. Choose Company Workspace for a company licensing LastStop Connect. Confirm paid seats and activate the organization before customer administrators use its privileged tools.

Step 3. Manage the product type from the owner company controls. An unpaid workspace cannot use its advanced APIs. Pause active security connections before downgrading a workspace.

Step 4. Use the same company ID in the owner command center and company portal. Company secrets, events, assets and changes stay attached to that ID. TLS platform settings and cross-company administration remain owner-only.

Now verify the result. A basic support administrator receives access denied on privileged company APIs. An administrator from another company cannot substitute the organization ID.

If you get stuck. A company record is not a separate deployment. Its branded domain requires the domain onboarding steps.

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.