Manage multiple businesses in one account
One AtomicPay login can access multiple business workspaces. Each workspace should behave like a separate operation with its own products, checkout links, Sales, Finance, and collaborators.
Use this guide when you run more than one brand, manage client accounts, or separate personal and company operations inside the same login.
When multiple businesses make sense
| Scenario | Example structure |
|---|---|
| Multiple brands | Course brand and software brand as separate workspaces |
| Personal vs company seller | Individual creator business and company-owned catalog |
| Agency or operator model | One workspace per client with scoped team access |
| Launch sandbox vs live brand | Separate test business only when policy allows real setup differences |
| Post-migration structure | New entity created during assisted migration |
What stays separate per business
| Area | Why separation matters |
|---|---|
| Products | Each brand sells its own offers and delivery model |
| Pricing | Plans, trials, and installments belong to one catalog |
| Checkout links | Links point to one business catalog and attribution context |
| Campaigns and Financial Overview | Revenue belongs to the correct entity |
| Finance | Balances, settlement timing, and withdrawals are per business |
| Integrations | Webhooks, pixels, and Notazz should not leak across brands |
| Team access | Collaborators may work on only one business or selected products |
Setup workflow for each business
- Create the business with the correct registration type.
[Screenshot: New business flow — Individual or Company selected for the new workspace.]
- Complete business setup tabs: details, activity, partners when required, and finance.
[Screenshot: All business setup tabs — Basic, Activity, Partners, Finance marked complete.]
- Add the correct bank account or PIX key for that entity.
[Screenshot: Finance tab — bank account or PIX key saved for this business only.]
- Invite team members to the correct workspace with the right roles.
[Screenshot: Team invite sent — correct business name shown in invite context.]
- Switch workspaces deliberately before creating products.
[Screenshot: Business selector listing multiple workspaces — each business name clearly labeled in the dropdown.]
[Screenshot: Products page — catalog belongs to the intended business per header label.]
- Run the first-sale workflow test per business before launch traffic.
[Screenshot: Approved test sale in Sales — scoped to the correct business workspace.]
- Document which brands, legal entities, and finance owners map to each workspace.
[Screenshot: Internal doc or naming — workspace names aligned to brands in the switcher list.]
Operating rules for multi-business accounts
| Rule | Practical effect |
|---|---|
| Switch before every edit | Reduces wrong-workspace product and pricing mistakes |
| Name workspaces clearly | Makes the selector usable for support and finance |
| Scope finance users intentionally | Not every finance collaborator needs every business |
| Keep reporting comparisons inside one workspace | Reconcile Dashboard and Finance per entity |
| Separate campaign naming | Use UTM conventions per brand |
| Offboard access per business | See remove collaborators |
What to verify before launch in each business
| Check | Why it matters |
|---|---|
| Registration type matches payout setup | Avoids bank account rejection |
| Products are in the intended workspace | Prevents cross-brand catalog mistakes |
| Checkout and funnel links are brand-specific | Reduces campaign attribution gaps |
| Team permissions are scoped correctly | Especially support-agent sales access |
| Finance knows which balance is withdrawable | See blocked withdrawals |
| Integrations point to the correct endpoints | Important for webhook security |
Best practices
- Treat each workspace like a separate company operation even when one person manages all of them.
- Give finance visibility only where needed using finance permissions.
- Use consistent internal naming for workspaces, products, and campaign links.
- Review inactive products per business so old links do not create support noise.
- Audit collaborators after launches and contractor offboarding.
Common mistakes
- Building all brands in the first workspace because it was already open.
- Comparing revenue across businesses without labeling the workspace in reports.
- Sending a team invite to the wrong business and only noticing after acceptance.
- Reusing the same custom campaign link naming across unrelated brands.
- Requesting withdrawals from the business that had sales but not the one finance expected.
FAQ
How many businesses can one account manage?
AtomicPay supports multiple workspaces under one login. Operational discipline matters more than count. Use switch business workspaces consistently.
Can the same collaborator access multiple businesses?
Yes, but access is granted per business and role. Review team roles and remove collaborators during offboarding.
Should affiliates be managed per business?
Yes. Affiliate programs, links, and commissions belong to the business that owns the product.
Where do I test a new business before launch?
Use the first-sale workflow and before-launch checklists inside the correct workspace.