OnimatorOnimator
Check price

What is Global Settings in Onimator? Global Settings is the app-wide configuration surface inside Onimator where the operator sets up the specific integrations, credentials, and system-level preferences that apply across every account and every tool in the installation. Rather than living per-account or per-tool (like Timer Tab settings or per-tool Action Limits), Global Settings holds the configuration that logically belongs to the installation as a whole — API keys for scraping providers, AI chatter platform credentials, notification webhook URLs, MCP server enablement, and the specific system preferences that shape how the app behaves regardless of which account or tool is running. It is one of the specific configuration surfaces every operator interacts with during initial Onimator setup, and it becomes the primary reference point when integrating any external service or third-party platform into the operator’s Onimator workflow.

What Lives in Global Settings

The specific contents of Global Settings fall into a few categories.

API integrations — the credentials Onimator uses to talk to external services. This includes HikerAPI and RapidAPI keys for Instagram scraping, OpenAI API keys for custom GPT integrations, Cupid AI and FluidTalk credentials for AI chatter platforms, and any other third-party service credentials the installation needs to authenticate against. Each integration typically has its own set of fields (API key, endpoint URL, plan-tier setting, rate-limit configuration) grouped together in its dedicated section of the panel.

MCP server configuration — the specific settings that expose the Model Context Protocol integration to AI assistants like Claude Code. This includes the master switch for enabling the MCP server, access-level configuration (read-only vs full-access), and the token that AI clients use to authenticate against the server. The MCP settings live in Global Settings because they apply to the installation as a whole rather than to any specific account.

Notification and support integrations — webhook URLs, Telegram bot tokens, Discord channel configurations, or email addresses the installation uses to notify the operator about specific events. Automation failure notifications, campaign completion alerts, and other operator-facing communications route through the specific integration the operator configured in Global Settings.

System preferences — the app-wide behavior settings that shape how the installation runs. Update cadence (whether to auto-update or prompt), default folder paths, logging verbosity, and other preferences that apply across the entire installation live in this section.

The API Integration Layer

The specific reason API integrations live in Global Settings rather than per-account is that the credentials logically belong to the operator’s account with the third-party service rather than to any specific Onimator account. One HikerAPI subscription serves all accounts running in the installation; one FluidTalk credential authenticates the entire installation’s AI chatter operations; one OpenAI API key covers every custom GPT prompt across every account.

Putting these credentials in Global Settings makes them configurable once and used everywhere. The alternative (per-account credential storage) would require the operator to duplicate the same credentials into every account’s settings, which produces both configuration overhead and the specific risk of inconsistency where some accounts have the correct credentials and others have stale or missing values.

The specific implication for operators is that changing an API credential in Global Settings immediately affects every account using that integration. Rotating an API key doesn’t require per-account updates; deprovisioning an integration doesn’t leave stale credentials in per-account settings. The centralization is what makes credential management practical at fleet scale.

MCP Server Configuration

The specific MCP configuration surface inside Global Settings deserves separate attention because it introduces a new capability class to Onimator that other Global Settings sections don’t. When the operator enables the MCP server through Global Settings, they’re not just configuring an integration — they’re opening a control surface that lets external AI assistants operate against the installation.

The security implications drive the specific configuration options exposed. The Enable MCP Server checkbox activates the server; the access-level selector determines whether connected AI assistants get read-only or full-access permissions; the token field holds the specific credential AI clients need to authenticate against the server. Copy Claude Code Command generates the specific setup command with the token embedded, letting operators register their Claude Code instance against the Onimator MCP server in one action.

The token functions as a password. Operators sharing tokens in public chats, tickets, or screenshots expose their Onimator installation to whoever obtains the token, and Global Settings includes the token-regeneration option specifically to handle exposure incidents. Regenerating invalidates the old token and requires re-registration by all connected clients — limiting the blast radius of an exposed token to the window between exposure and regeneration.

Why Global Settings Sits Separate From Per-Account Config

The specific architectural rationale for splitting configuration into Global Settings (app-wide) and per-account settings (per-account, per-tool) is that different categories of configuration change at different rates and belong to different logical scopes.

Per-account configuration changes as accounts move through their lifecycle. Warm-up settings, action limits, targeting configurations, and Timer Tab windows evolve as accounts age. This configuration belongs to the account and lives in the account’s settings surface.

Global configuration changes rarely and applies universally. API keys typically get set once at installation and updated only when credentials rotate. MCP server configuration gets enabled once and typically stays enabled across the installation’s lifetime. Notification integrations get configured once and updated only when the operator changes support channels. Storing this configuration per-account would be redundant (the same values repeated across every account) and error-prone (the same values getting out of sync across accounts).

Global Settings gives this configuration its correct scope — one location, one canonical value, consumed by whichever accounts and tools need it.

The Setup-Once, Maintain-Rarely Workflow

The specific operational pattern Global Settings encourages is setup-once, maintain-rarely. During initial Onimator installation, operators work through Global Settings systematically — entering API credentials, configuring notification integrations, enabling MCP if needed, setting system preferences — then rarely return to the panel except for specific maintenance events (credential rotation, integration changes, adding new external services).

The specific contrast with per-account settings is stark. Per-account configuration is ongoing operational work that changes as accounts progress through warm-up, as strategies evolve, and as campaign requirements shift. Global Settings is a mostly-set-and-forget configuration surface that the operator touches occasionally but doesn’t work with daily.

This pattern is what lets operators focus their attention on the operational work that actually varies (per-account tuning, per-tool activation, campaign configuration) rather than on the infrastructure configuration that stays mostly static. The specific split makes Onimator’s ongoing operator workload proportional to operational decisions rather than to infrastructure maintenance.

Where Global Settings Fits in the Onimator Architecture

Global Settings is one of the specific surfaces that sits above the per-account configuration layer in the Onimator architecture. Alongside the OniHelper Suite’s fleet-management tools (which operate on per-account data at bulk scale) and the core Onimator execution engine (which reads per-account configuration to run sessions), Global Settings provides the installation-scoped configuration that the other layers depend on.

The specific reads happen at runtime. When an AI chatter integration needs to make a call, the tool reads the credentials from Global Settings. When the MCP server receives a request, it checks the enable state and access-level configuration from Global Settings. When scraping tools need to authenticate against HikerAPI or RapidAPI, they read the credentials from Global Settings. Every downstream tool that needs installation-scoped configuration gets it from this specific location.

Why It Matters for Automation

Global Settings is the specific configuration surface where the operator’s infrastructure decisions live. For operators running Onimator with any external integrations (which is essentially every operator running the platform at meaningful scale — AI chatters, scraping providers, MCP access all require Global Settings configuration), the panel is the specific place where getting configuration wrong blocks entire feature categories from working. API keys missing from Global Settings prevent all AI chatter functionality regardless of how correctly per-account chatter configuration is set. MCP disabled in Global Settings prevents any AI assistant integration regardless of how the operator has set up their Claude Code instance. Understanding what lives in Global Settings — and what belongs there versus what belongs in per-account configuration — matters for operators specifically because most infrastructure-related debugging traces back to specific Global Settings values that either weren’t set or were set incorrectly during initial installation.

Related Terms