Configuration¶
The top-navigation Configuration menu provides native TrackMe interfaces for system-wide settings and integration accounts. System settings manages logging, default ownership and RBAC, and the defaults used across tenants. Dedicated pages manage Remote deployment accounts, Email delivery accounts, S3 export accounts, Cribl connections and Webhook accounts; Configuration Guardian checks configuration health. Native interfaces replaced the Splunk UCC configuration page in version 2.4.8. 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 and
The scheduled owner and service account for component-specific scheduled-owner requirements beyond this
baseline.
Important
System settings and account management require a Splunk administrator-class user
with TrackMe admin capabilities, typically trackme_admin together with admin /
sc_admin. If a configuration request is denied, the native interface displays an
Insufficient permissions message. Tenant administration and scheduled monitoring use
separate permissions. For next-generation components, named scheduled owners have
additional requirements: use The scheduled owner and service account for the current owner checks
and Roles & access control — in depth for each source/API account.
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 user-interface defaults (theme, auto-refresh, volume unit labels and more) that apply until each user picks their own (see Personal preferences);
Remote Splunk accounts are managed separately under Configuration → Manage Remote deployment accounts (see Remote Splunk deployments). To change an existing tenant’s RBAC or ownership, use its Virtual Tenant UI (see Managing tenants); system-wide defaults apply to tenant creation.
See also
Configuration — in depth — every Configuration interface, the service-account & minimal-permission setup, and logging mechanics.
Roles & access control — the capability and role model.
REST API reference — the API behind the Configuration UI.
Large-scale environments — using a service account at scale.