McLeod Software integration

2. Connection and scope

Seedling verifies the provider account before storing the workspace connection. A current Seedling workspace administrator controls installation and disconnect; account identity is never inferred from an email address or display name.

McLeod Cloud or Direct authorization

Cloud requires tenant ID, API key, username, password, and company ID. Direct requires company ID, a registered bearer token, and the exact HTTPS API1 base URL.

Connection ownership

This connector is workspace-only. A current Seedling workspace administrator controls installation, credential replacement, disconnect, and purge for the exact connection.

3. McLeod Software data Seedling accesses

Seedling uses synchronized information for source-backed search, operating context, verification, and customer-approved workflows. Availability depends on the connected account, selected resources, provider plan, and native permissions.

Dispatch operations

Orders, movements, stops with reference numbers and notes, driver call-ins, service failures, and audit-log deletions.

Master and mobile data

Customers, prospects, contacts, comments, locations, drivers, tractors, trailers, payees and carriers, users, mobile-communication messages, units, and latest positions.

Commercial and compliance data

Quotes, billing and receivables, settlements, deductions, wires, EDI tenders, invoices, and statuses, motor accidents, OS&D claims, and reference code lists.

Excluded data

Passwords, tokens, SSNs, birth dates, license numbers, medical data, bank or card instruments, document and image bytes, reports, and every McLeod business mutation.

4. Read-only permission contract

Use provider-issued read-only API1 access with the Users role for the intended company. Families the API user cannot read are skipped with a warning and rechecked daily.

• Company identity and read-only order, movement, stop, call-in, and service-failure access.
• Read-only master-data access for customers, locations, drivers, equipment, payees, and users.
• Read-only billing, settlement, EDI, safety, and mobile-communication access for the families you want extracted.
• Audit-transaction search access so deletions are tombstoned; without it Seedling never infers deletions from absence.
• Exact Cloud tenant/company or Direct origin/company identity is mandatory; credentials are never selected by a display name.
• No McLeod record, dispatch, billing, document, or workflow mutation is implemented.

5. Security and access

• Provider credentials and other connection secrets are encrypted in the workspace tenant data plane, never returned to the browser, and excluded from logs and queue payloads.
• Every source, synchronization, secret lookup, audience contribution, disconnect, and purge remains bound to the exact connection that created it.
• Workspace objects begin with no human audience. A current workspace owner or source steward must assign the provider-defined scopes for this exact connection to active members; membership, administrator or steward status, installer identity, and provider roles grant no raw-content bypass.
• Declared human access uses one exact-connection scope per record family, such as Orders, Driver call-ins, Customers, or Pending settlements. Grants do not cross McLeod companies or connections.
• Generated output cannot bypass Seedling's human review, verification, and approval gates.

6. Retention and deletion

Connected data

Synchronized McLeod Software records remain while the connection is active and are removed through a durable integration purge after disconnect.

Credentials

Stored McLeod Software credentials or connection secrets and connection-owned synchronization state are deleted from active Seedling systems as part of the purge.

Backups

Deleted information may remain in encrypted, access-restricted backups until expiry, ordinarily within 35 days after active-system deletion.

7. Installation, help, and removal