Hello, I’m Nora, your AI guide from Technology Last Stop. This guide covers Start a company portal. Create a company with its own Customer ID, users, product type and scoped settings. TLS retains owner administration. Current availability: Owner-assisted setup.

Before you start. A company administrator, legal business name, primary email domain and authorized billing contact. TLS owner approval, a paid agreement and access to the company DNS provider.

Step 1. Open /companies > Create company. Choose Company Workspace for a software customer or Managed Support for basic service access. Enter the company name and the registered domain you own. Your typed domain remains visible; a separate DNS-form hint explains internationalized domains. Enter a supported billing contact, or select Set up billing later to save onboarding without payment.

Step 2. Open Overview > Customer profile to add or update the actual billing contact, phone, industry and address information. New portals start with TLS support email, the TLS welcome message, America/Chicago time zone and TLS blue. Review Portal settings for customer-specific changes. Unknown business details must not be invented.

Step 3. Both products have company records, users, knowledge, requests, planned changes and authorized billing access. Paid Workspaces also have their own helpdesk, devices, integrations, passwords, security and company settings. Managed IT clients use the TLS support portal without workspace administration.

Step 4. In Licenses & billing, select Standard, Professional or Enterprise, at least five Managed IT users or ten Workspace users, and a monthly or 1/2/3-year prepaid term. Read the policies and record authorized acceptance. TLS records a cleared invoice payment or Stripe confirms payment before the plan and seats become active.

Step 5. After payment, the owner activates the workspace. Add company administrators, billing contacts and requesters in Users, then use the existing identity provisioning workflow.

Step 6. On first sign-in, every company account enrolls an authenticator, verifies its six-digit code and saves eight recovery codes. Owners, administrators, billing users and regular users all complete a second factor. TLS staff retain their separate LastStop Verify workflow.

Step 7. Open connect.techlaststop.com/portals. Choose Managed IT for TLS-managed support or Company Workspace for your own permitted tools. Pricing is publicly available at /pricing; authorized company billing is at /company?tab=billing.

Step 8. A branded connect.companydomain.com deployment and paid Dev/QA require owner-assisted domain, identity, deployment and acceptance steps.

Now verify the result. Company name, Customer ID and domain agree across billing and support. A second-company test account cannot read the first company’s tickets, files, invoices or API responses. Customer administrators cannot open TLS owner configuration or retrieve connector secrets.

If you get stuck. A saved environment request only reserves an onboarding request. It does not create hosting or verify DNS. Contact TLS if the same email must administer several companies: the current identity model allows one client organization per email. Accented domains use their actual DNS form: atéssa.com and atessa.com are different domains. Use the one the company owns; its display name may retain accents independently. Billing email: the mailbox name before @ currently requires unaccented characters; accents in the domain after @ are supported. Do not substitute an address you do not own. Leave billing blank during onboarding and add a supported existing contact later. Creating onboarding does not send email or activate a paid subscription.

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.