Default: one account, intentional filters
Most people should run one Stackora user and shape behavior with forwarding rules, not by duplicating accounts.
You already choose what reaches Stackora — that is the real boundary. Tight filters plus short Intelligence hints (focus, ignore, correlation) keep school mail separate from office mail before it ever hits the digest, even when both forward from the same Gmail login.
Signs you are in the right place:
- You can describe, in one sentence, what mail is allowed to forward.
- Volume is predictable enough that a weekly (or plan-supported multi-day) review still fits in twenty minutes.
- Nothing in the digest surprises a partner you share output with.
Optional: shared workspace for family or team collaboration
On eligible plans, Stackora offers a shared workspace — a place for members you invite to coordinate context, not a second private mailbox.
Use it when:
- A partner should see the same digest items or shared notes without re-forwarding threads.
- You want a durable home for “how we run the household” knowledge alongside mail-driven tasks.
The workspace is for people, not for “my finance label vs my school label.” Topic separation still lives in filters and Intelligence.
When you actually need two Stackora accounts
Create another user only when the boundary is contractual or cultural, not cosmetic.
Hard separation examples
- Work email that must never share infrastructure with personal mail for compliance.
- A side business that bills separately and should not inherit household digest defaults.
- Two adults who want completely independent forwarding addresses and schedules — each person already counts as their own Stackora user.
Not a separate-account problem
- “I want finance and school in different mental buckets.” Fix that with two Gmail filters (or two forwarding rules), correlation hints, and possibly two digest sections in how you review — not two Stackora logins.
What “multiple workspaces” is not
You cannot maintain several isolated Stackora “mail workspaces” inside one login the way some CRMs allow. The product assumption is simpler: one intake pipeline per user, tuned with rules.
If you tried to simulate multiples by constantly swapping forwarding destinations, you will fight the product. Either loosen the scope or admit you need another account.
Recovery if you over-split accounts
If you created a second login and the overhead annoys you, consolidate:
- Pick the account that should survive.
- Point all Gmail or Outlook rules at the surviving forwarding address.
- Export Intelligence hints from the old account and paste them into the keeper.
- Cancel or pause the redundant subscription when billing allows.
Keep the dormant login for a month if you fear losing historical items, then close it deliberately.