Switch accounts and manage your data
Switch LLMIC accounts on one Mac and understand how local workspaces, preferences and provider credentials are separated.
Using two LLMIC accounts on one Mac should not make their workspaces interchangeable. Account isolation separates saved local work and provider credentials by the signed-in identity. This is especially useful when testing a customer account separately from a developer account. A different subscription can also unlock a different set of tools, even though the same application is installed.
What this guide helps you do
Data isolation keeps one signed-in account’s workspace separate from another account on the same Mac. Learn what changes when you switch LLMIC accounts, what stays on the device and how to verify a clean workspace.
Check the current identity
Open Settings → Account & License and read the account shown there before starting work. Compare its plan and access status with the account you expected. Browser sign-in can reuse an existing Google session, so do not assume that opening authentication automatically selected a different identity. The account displayed in LLMIC is the practical check before configuring keys or starting another crawl.
Switch through the app
Use Sign out / switch account rather than deleting local folders or changing files manually. LLMIC reopens as part of switching account scope. Complete sign-in using the intended identity and check Account & License again. If the browser selects the previous account, choose the correct identity in the authentication flow. Do not share your login credentials with another person to simulate a separate customer.
Understand what should be separate
Account-scoped workspaces, saved crawl data, preferences and provider credentials should load for the correct signed-in account. A fresh account should not inherit another account’s saved API keys or crawl workspace. Client-level credential choices are a second layer within an account: selecting a client is not the same operation as switching the entire signed-in account.
Know the local-storage boundary
Account separation inside LLMIC is not the same as isolating two operating-system users. Files you export into a shared Finder folder remain ordinary files in that location. Also, local account-scoped storage does not imply automatic cloud synchronization between Macs. Keep backups of important exports and work, and make deliberate decisions about which folders you share outside the application.
Check restoration and report problems
When you return to the original account, check that its expected saved workspace and connections are available. If another account’s data appears, stop using the unexpected connection and report the app version and account-switch sequence to support. Do not delete the data as a first troubleshooting step. Signing out is not a request to permanently erase saved work or cancel the subscription.
Quick reference
| Action | What changes |
|---|---|
| Switch account | Signed-in identity and local account scope |
| Switch client | Client context inside the current account |
| Export a file | Creates a file in your chosen location |
| Sign out | Does not itself cancel billing |
| Install on another Mac | Does not imply local data automatically syncs |
Continue learning
Next, review credential scopes, review account and device access. Return to the documentation home to explore other guides. If the result differs from these instructions, contact support with your app version and the relevant steps. Remove private information from screenshots and never include API keys or passwords.
Frequently asked questions
Switch LLMIC accounts on one Mac and understand how local workspaces, preferences and provider credentials are separated.
Have the current LLMIC build, the account that should own the workspace, and any required subscription or provider access ready. Follow the prerequisites on this page before changing macOS security, account, or billing settings.
Check the app version, account email, selected plan or provider, permission state, and the exact message shown on screen. Those details are more useful than assuming that every setup problem has the same cause.
Follow the steps in order and stop at the first result that differs from the guide. Record that step and the exact message before retrying, reconnecting an account, or contacting support.
Confirm the expected screen or account state described in the Check the result section. Installation, authentication, provider connection, and subscription access are separate outcomes, so verify the one this guide covers.
This workflow confirms the visible setup result described here. It does not certify unrelated features, future updates, every Mac configuration, provider availability, or a payment outcome that was not completed.
Save or export the evidence, assign the approved action, and use the related guides linked on the page for the next check. After implementation, repeat the same workflow against a fresh crawl so the result is comparable.