When to use this endpoint

Use for legacy report user-series labels that need to identify outsourced assignees. External rows are labelled with their company name, not necessarily an employee name.

Authentication and permissions

Authenticate with signed API-key fields or a logged-in CRM session. Session requests use the dispatcher’s CSRF protection when configured.

Configured TeamAccess row scope is applied in the queries. Ordinary collection requests do not need artificial record IDs. Explicit IDs still pass dispatcher record authorization; unavailable IDs can be rejected there rather than silently omitted.

Login is required. No additional page permission is imposed by this handler.

Parameters

This endpoint has no operation-specific parameters.

Example request

$result = FM_api('Users_listIncludeOutsourced', [
]);

Example response

{
  "1042": {
    "id": "1042",
    "name": "Alex Morgan",
    "active": "1"
  },
  "2048": {
    "id": "2048",
    "name": "Partner services",
    "a": "1"
  }
}

Errors and unusual responses

ResponseCondition
{"error":"not logged in"}No authenticated tenant context is available. Invalid signed credentials can be rejected by the dispatcher before the handler runs.

Legacy application errors may be returned with HTTP 200. Check the decoded response for error, not only the HTTP status.

Behaviour and edge cases

  • Starts with visible non-temporary tenant users, without active or parent filtering. Adds distinct nonzero assignees from visible non-deleted Jobs when absent from the tenant user table.
  • Resolves each external identity and company through global tables. A missing identity yields name=unknown and a=0; an identity whose company row/name is absent can instead have a null name. No outsourcing-link/status check is added to that historical assignment lookup.
  • Local rows use active; external appended rows use a. The map is keyed by user ID, with no sort/pagination. A nonempty map is an object; no rows yields [].
  • The historical external active/a shape and company-name resolution remain compatibility behavior; this is not an outsourcing-link directory.

Side effects

  • Reads data without changing business records, edit markers, activity history or notifications. Shared setting reads can populate their normal settings cache.

See it in Fieldmotion

CRM1

CRM1 report rendering calls Users_listIncludeOutsourced for user_id series labels.

CRM2

No direct production caller was found in CRM2. Current User layouts use the mapped getRequestedDetails/getDataTable flow; do not assume those contracts match this legacy reader.

Related endpoints

  • User_getCompanyName — Resolve an authorized outsourcing-company label.
  • Users_list — Read the basic selectable user list and its explicit scope predicate.