Configuration

The top-navigation Configuration menu is where you set TrackMe’s service account, its required Splunk capabilities, logging, and the system-wide defaults that govern every tenant. From version 2.4.8 it groups a set of native React interfaces — System settings (every system-wide setting), Manage Remote deployment accounts, Manage Email delivery accounts and Manage S3 export accounts — replacing the generic Splunk UCC configuration page as the primary management surface (the legacy page remains as a fallback). AI Provider accounts are managed under the Artificial Intelligence menu (see Configuring AI Provider accounts).

The service account

A dedicated service account is optional but recommended. Without one, TrackMe creates its knowledge objects and runs its scheduled searches as the Splunk system account — which works, but a dedicated account gives you clean cost attribution and lets you apply Splunk Workload Management.

A service account needs, at minimum: the Splunk power role (for search and schedule_search), the three TrackMe capabilities (trackmeuseroperations, trackmepoweroperations, trackmeadminoperations), and the ability to search all non-internal indexes plus _internal. See Roles & access control for the role model.

Important

Opening any of the Configuration interfaces additionally requires the native Splunk capabilities list_settings, list_storage_passwords, and admin_all_objects — so they are reserved for Splunk admins (persistence still flows through the Splunk UCC REST endpoints, which mandate them). A user lacking these capabilities is shown a clear insufficient permissions message. They are not needed by the service account, nor to manage tenants and trackers day to day. This is deliberate: TrackMe’s least-privilege design keeps these sensitive capabilities off everyday users.

System-wide settings

The System settings page holds the settings that apply across all tenants, including:

  • enabling the AI Assistant and the Configuration Manager receiver;

  • data-sampling thresholds and maintenance / SLA-exclusion behaviour;

  • logging levels, honoured by both the REST API and the custom commands;

  • the remote accounts used to reach remote Splunk deployments (see Remote Splunk deployments).

See also