McLeod Software support

Last updated date:

Connect, reconnect, and troubleshoot McLeod Software without sharing credentials or customer content through support channels.

1. Before you start

  • Ask an authorized McLeod administrator for read-only API1 access to the intended company.
  • Choose Cloud or Direct deliberately and gather the complete credential set required by that deployment.
  • For Direct, verify the API1 origin is HTTPS and registered for the bearer token; review the excluded sensitive fields before connecting.
  • Do not send McLeod Software credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
McLeod API documentationMcLeod's API1 reference.

2. Connect McLeod Software

  1. In Seedling, open Connections and choose McLeod Software.
  2. Connect from workspace scope as a current Seedling workspace administrator.
  3. Enter the Cloud tenant/API/user/password credential set or the Direct bearer token/API1 URL, plus the exact company ID.
  4. Seedling validates the selected deployment, exact company identity, HTTPS origin, order search, and audit-log availability before creating the source.
  5. Allow the first McLeod Software synchronization to finish, then verify the expected resource population and member access policy.

3. Authorization and connection problems

McLeod credential set rejected
Confirm the mcleod credential set is active, was entered without surrounding whitespace, and belongs to the intended McLeod Software account and environment.
Missing permission or resource
Restore the exact read permission or provider-side resource access described in this guide. Seedling does not substitute a broader credential or silently treat a forbidden McLeod Software population as empty.
Wrong account or scope
Disconnect before retrying with the intended McLeod Software identity, account, and Seedling connection scope. Seedling does not infer account ownership from a display name or email address.

4. Missing or delayed data

  1. Confirm the record belongs to the verified McLeod company and an extracted record family.
  2. Check deployment-specific credentials, API1 origin, API user roles, record dates against the 365-day initial window, and synchronization warnings.
  3. Confirm the member has the exact-connection declared scope for that record family.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Create replacement mcleod credential set for the same McLeod Software account with the same or narrower released permissions.
  2. Replace the credential on the exact Seedling connection and repeat identity, scope, and capability verification.
  3. After Seedling confirms the replacement, revoke the old mcleod credential set in McLeod Software.