# Slot management One slot = one X account. Slots have independent plans, settings, and credentials. Username rotation is locked to once every 7 days per slot. ## What is a slot A slot is the container for one X account inside HelperX. It stores: - X credentials (auth token, proxy) — encrypted at rest. - Profile metadata (screen name, display name, avatar, blue verified status). - Plan assignment and expiry date. - Module settings (reply search, top repost, etc.). - Daily counters, replied-tweet stores, and other operational state. Slots are independent — each has its own plan, caps, and module state. One user can manage multiple slots on different plans. ## Replacing a profile The **Replace Profile** action swaps the X account attached to a slot. It accepts a new auth token, proxy, and account info. The system performs several checks: 1. **Token collision:** If the new auth token is already used by another slot, the request is rejected. 2. **Same user:** If the new screen name matches the current one (case-insensitive), it's treated as a credential refresh — only the token, proxy, and display fields are updated. No lock is applied. 3. **Different user:** The 7-day rotation lock is checked (see below). If the lock has expired, the full profile swap proceeds. ## 7-day rotation lock When a slot's X username changes (different screen name), a lock timestamp is recorded. For the next **7 days**, the slot cannot be assigned to a different X account. If you attempt to replace with a different username during the lock, the system shows an error with the unlock date and remaining time. Refreshing credentials for the *same* username is always allowed, even during the lock period. ## Detach & reattach **Detach** removes the X credentials from a slot. All module settings are reset to defaults. The slot becomes empty, ready for a new profile. Fields **preserved** on detach: - Plan and expiry date - Rotation lock (the 7-day lock persists) - AI settings (options) Fields **reset** on detach: auth token, proxy, screen name, display name, avatar, all module settings, daily counters, replied-tweet stores. All running module workers **must be stopped before detaching** — the caller is responsible for this. ## Plan survives detach Because plans are slot-level metadata (not user-level), detaching an X account does not cancel or reset the plan. The slot retains its plan so the user can reattach a new profile and immediately use the same plan tier. The 7-day rotation lock also survives detach, preventing rapid account cycling. Operator guides: [Multi-account isolation](https://helperx.app/blog/multi-account-x-isolation) · [How many accounts can one operator run](https://helperx.app/blog/how-many-x-accounts-safely) · hub: [Safety & Multi-Account Ops](https://helperx.app/guides/x-safety-multi-account-ops).