Skip to main content

Deployment Scope

Before you deploy, decide how the agent maps endpoints to organizations. There are two modes. The install properties differ between them. For the full property table, see Download and verify.

Single-org (internal IT)​

All agents register directly under the token's organization.

  • Pass USEPARENTORG=1 to register under the token's organization and opt out of sub-org creation.
  • CLIENTNAME is rejected in this mode (a server-side safety gate).

Use single-org when all endpoints belong to one organization, for example your own internal IT.

Client-orgs (MSP, multi-tenant)​

Each endpoint auto-creates or links a child organization under the token's organization, keyed by your client identifiers. You do not pre-create client organizations by hand.

SparkLogs Agent auto-creating client organizations under an MSP parent
  • Pass RMMCLIENTID and/or PSACLIENTID as the linking keys. The agent creates or links the matching child organization.
  • Use a distinct identifier per client so each client gets its own organization.

The client name is a display label only, never a linking key.

  • It is auto-detected per endpoint: AD domain when domain-joined, otherwise the RMM ID, then the PSA ID. It is never a placeholder.
  • Override the detected label with CLIENTNAME (quote values that contain spaces).
  • Use a distinct value per client. Never set one constant name across a whole fleet, and never use CLIENTNAME as a way to group agents (use the RMM or PSA IDs for that).

Next steps​