Source: competitor + community research. "You can't sign on to several business organizations like you can in Slack. So dumb and disqualifying." ~39k feedback-portal votes for multiple-accounts.
Problem
Consultants, guests, and multi-org users constantly re-login or juggle windows across Teams tenants. This is the classic reason people reach for alt-clients (Ferdium/Rambox/Beeper).
Proposal
Sign into several tenants/accounts at once; a fast switcher and (stretch) a unified/merged chat + activity list. This is a genuine alt-client killer feature and leans on Teamsly's speed.
Graph feasibility
Likely. Graph OAuth is per-account; Teamsly holds multiple delegated token sets and swaps context. The hard part is the auth/session model (NextAuth is single-session today) — needs design. Start with fast account-switch, then merged views.
Sources: https://news.ycombinator.com/item?id=32932137 · https://www.m.io/blog/switching-microsoft-teams-tenants · https://rambox.app/features/
Source: competitor + community research. "You can't sign on to several business organizations like you can in Slack. So dumb and disqualifying." ~39k feedback-portal votes for multiple-accounts.
Problem
Consultants, guests, and multi-org users constantly re-login or juggle windows across Teams tenants. This is the classic reason people reach for alt-clients (Ferdium/Rambox/Beeper).
Proposal
Sign into several tenants/accounts at once; a fast switcher and (stretch) a unified/merged chat + activity list. This is a genuine alt-client killer feature and leans on Teamsly's speed.
Graph feasibility
Likely. Graph OAuth is per-account; Teamsly holds multiple delegated token sets and swaps context. The hard part is the auth/session model (NextAuth is single-session today) — needs design. Start with fast account-switch, then merged views.
Sources: https://news.ycombinator.com/item?id=32932137 · https://www.m.io/blog/switching-microsoft-teams-tenants · https://rambox.app/features/