OnimatorOnimator
Check price

What is Copy Settings in Onimator? Copy Settings is the specific OniHelper Suite feature (currently exposed in the Threads Manager container) that replicates one source account’s Follow tool configuration onto many target accounts in a single action, controlled by a checkbox tree that lets the operator specify exactly which settings to propagate rather than copying every field indiscriminately. Instead of manually opening each target account’s settings and duplicating the source account’s Follow limits, timing ranges, Follow Method selection, and Auto-Increment configuration one field at a time across the fleet, the operator picks a source account whose configuration they trust, ticks the specific settings groups they want to replicate, selects target accounts, and clicks Copy Settings to apply the source’s chosen configuration to every target at once. It is the specific mechanism that turns fleet-wide configuration standardization from an impractical per-account editing exercise into a bulk operation completed in seconds.

How Copy Settings Works

The mechanism runs against the Onimator bot folder that Threads Manager is pointed at. When the operator opens the Copy Settings sub-tab and clicks Select Source Account, a picker appears listing every account in the current bot folder — the operator picks the specific account whose configuration will be the source. The operator then ticks which specific settings to copy in the settings tree on the left, selects target devices and accounts on the right through the standard device and account panes, and clicks Copy Settings to execute the replication.

The action reads the source account’s Follow tool configuration from the bot folder, extracts the specific fields the operator ticked in the settings tree, and writes those field values into every selected target account’s Follow tool configuration. Fields the operator didn’t tick in the tree are left untouched on the target accounts — the copy is selective by design rather than an all-or-nothing replication.

The Settings Tree

The settings tree exposes four collapsible groups of checkboxes, each representing a category of Follow tool settings that get copied together if the group’s checkbox is ticked.

Tool Status contains the Copy Follow Status checkbox, which propagates the source account’s Follow tool Master Toggle ON/OFF state onto the target accounts. Ticking this box means target accounts inherit the source’s activation state — a source with Follow Tool ON makes every target’s Follow Tool ON after the copy, and a source with Follow Tool OFF makes every target OFF. This is one of the most consequential settings in the tree because it can inadvertently activate or deactivate tools across the fleet if the operator doesn’t consider the source’s toggle state before copying.

Follow Method contains checkboxes for the specific Follow Method choices (Follow Account’s Followers, Follow Account’s from Feed, Follow Account’s Followers from Feed) plus their sub-settings (Skip Account Randomly when Following, Randomly Like Post Feed after Follow, Limit Maximum Follow per Feed Source and its Value). Ticking these boxes replicates the source’s targeting strategy onto the targets.

Follow Action contains checkboxes for Follow Limit per Day, Follows per Operation (Min/Max), and Delays after Following (Min/Max Seconds). Ticking these replicates the source’s per-tool volume and pacing configuration onto the targets. This is the group operators most commonly copy — pacing and volume tuning that took time to develop on the source account gets propagated across the fleet with a single action.

Auto Increment Settings contains checkboxes for Auto Increment Follow Daily Limit, Auto Increment Value, and Auto Increment Max Limit. Ticking these replicates the source’s warm-up ramping configuration onto the targets, which is particularly useful for propagating a proven ramping curve to new accounts entering warm-up.

Source Account Selection Matters

The specific choice of source account determines what the target accounts inherit. Well-configured Copy Settings workflows use source accounts that have been carefully tuned and validated as producing sustainable output — accounts where the operator has confidence that the Follow configuration works well and would work equally well on similar accounts.

The specific failure mode is copying from source accounts that haven’t been validated, or from accounts whose configuration was appropriate for that specific account’s stage but wouldn’t fit the target accounts’ stages. Copying a warmed account’s aggressive daily limits onto fresh warm-up accounts produces the specific configuration state where fresh accounts run at max volume from day one — the specific pattern that causes fresh-account restriction events regardless of how well the underlying settings work on warmed accounts.

Operators developing configuration templates typically maintain specific “template accounts” whose sole purpose is holding the reference configuration for Copy Settings operations. These template accounts don’t run active campaigns; they exist so their configuration can be reliably replicated onto working accounts as fleet compositions change.

Why Bulk Config Replication Is Load-Bearing

The specific reason Copy Settings matters operationally is that fleet-wide configuration consistency is the specific practice that separates operations producing predictable outcomes from operations producing inconsistent outcomes across accounts running the same strategy. When every account in a group runs identical Follow configuration, the aggregate outcome is the sum of per-account outcomes that reflect the specific configuration’s characteristics. When accounts within the same group run different configurations (some copied from a well-tuned template, others manually configured with drift), the aggregate outcome varies across accounts in ways that trace back to per-account configuration differences rather than to underlying strategy characteristics.

Manual per-account configuration doesn’t scale past a handful of accounts. The specific time cost of opening each account, navigating to Follow settings, and editing every relevant field to match a reference configuration exceeds what any operator can sustain across fleets of meaningful size. Copy Settings turns the replication into a bulk operation that scales to fleets of any size while producing consistent per-account configurations by construction.

Common Copy Settings Workflows

Several specific operational workflows depend on Copy Settings.

Fresh account onboarding. New accounts entering the fleet start with default configurations that need to be replaced with the operator’s specific standard configuration. Rather than editing each new account manually, operators select the template account as source, tick the relevant settings, and copy onto every new account in one action.

Configuration updates across the fleet. When operators develop improved Follow configurations (better pacing values, more effective targeting settings, refined Auto-Increment curves), Copy Settings propagates the improvements across the fleet without requiring per-account re-editing.

Warm-up stage transitions. Accounts moving from warm-up to steady-state operation need configuration adjustments (higher daily limits, updated targeting, warm-up features turned OFF). Copy Settings from a “warmed template” account handles the transition across every account moving to the warmed stage in one operation.

Client-scoped configuration. Agencies running multiple clients with client-specific configurations use Copy Settings alongside Filter by Tag to scope the replication to the specific client group. Client A’s template account propagates to Client A’s accounts; Client B’s template propagates to Client B’s — each scoped by tag filter to prevent cross-client configuration contamination.

Where Copy Settings Fits in the OniHelper Architecture

Copy Settings currently lives inside the Threads Manager container tab as one of its five sub-tabs, with equivalents in other platform-specific containers as the OniHelper Suite continues to expand its bulk-configuration tooling. The specific placement inside Threads Manager reflects that Copy Settings was initially built around the Threads Follow tool’s specific configuration surface, though the pattern generalizes to any tool with a well-defined configuration structure worth propagating.

Combined with Tag Manager (for scoping) and Time Manager (for scheduling), Copy Settings contributes to the specific fleet-level configuration workflow that makes fleet-scale operations tractable — tag accounts into groups, allocate schedules across devices, copy configurations across group members, and let the aggregate fleet run coordinated operations rather than a collection of independently-configured accounts.

Why It Matters for Automation

Copy Settings is the specific mechanism that turns configuration standardization from an impractical per-account editing exercise into a bulk operation completed in seconds. Without it, operators maintaining fleet consistency would face the specific choice between accepting configuration drift across accounts (which produces inconsistent per-account outcomes and makes debugging harder) or dedicating substantial ongoing time to per-account configuration maintenance (which doesn’t scale). With it, template-based configuration management becomes practical at any fleet size, and updates to proven configurations propagate across the fleet without requiring the per-account editing burden that would otherwise cap operational scale.

Related Terms