What Neo can do with Todyl
- Endpoints: list a client’s devices with their agent version against the latest one, last check-in, tamper protection, paused protection, pending reboot and billing status, and flag the stale or outdated ones
- Users: see the account signed in on each device’s latest session, and whether that sign-in used MFA, to find the device a user works on or the user of a device
- Device list breakdown: count a client’s devices by type, operating system, agent version and deployment group, with each deployment group’s products and device count
- Billing: read Todyl’s invoices to you, each client’s slice of an invoice and the devices that checked in during its period
Your tenants are mapped to companies
Neo matches your Todyl tenants to the companies in your PSA and keeps the mapping on the Todyl card’s Organization Mapping tab, refreshed on each PSA metadata sync. Neo reads the tenants from your deployment groups. Matching uses the tenant name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Last comes an AI match for the long tail. A name match, or one you confirm, is handed straight to your agents. An AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it. Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync. On a ticket, an agent reads Todyl only for the tenant mapped to the ticket’s company, and never reads whole invoices, which cover every client. A company with no mapping that agents can use gets no Todyl reads until you set or confirm one on the tab. Agents with no ticket, such as a chat or a scheduled report, read every tenant.Next steps
Connect Todyl
Create an External API token, allow Neo’s addresses and save the token in Neo.
