Count the log-ins your team has. The real number, not the one in your password manager. Include the staging admin panel, the analytics dashboard, the on-call paging tool, the help center backend, the marketing CMS, and the thing your designer set up two years ago that everyone forgot about until last Tuesday.
A typical ten-person startup has somewhere between forty and eighty distinct identity surfaces. Each one is a place where someone can be over-permissioned, under-permissioned, or — when an employee leaves — quietly left behind. Identity sprawl is the silent tax on small teams.
Why we built shared identity first
Before we wrote a single line of Tickets, we wrote the identity layer. Every ByeBloat product — Tickets, Live Chat, Channels, Tasks, Notes, and every app we ship after — sits behind a single sign-in and a single member directory. Adding a new hire to your team grants them access to every product you own, with the permissions you set once. Removing them does the opposite, in one click, everywhere.
This is not glamorous engineering. It is plumbing. But the plumbing is what makes the suite feel like a suite instead of a loose pile of products with the same logo.
What you get
- One member list. Add a contractor once. They show up in every product they have access to.
- One off-boarding click. When someone leaves, you remove them in one place. No more quarterly access audits where you discover a former employee still has admin on the help center.
- One avatar everywhere. Update your photo in account settings and it propagates to every product without a sync job.
- One audit log. Every login, every product switch, every permission change — recorded in one place, not five.
What we deliberately did not do
Shared identity is not the same as a shared database. The temptation, when you control the auth layer, is to also control the data layer — to put every product’s tables in one giant schema and call it “synergy.”
We did not do that. Each product has its own database, its own deploy pipeline, and its own on-call rotation. Tickets going down does not take Live Chat with it. The only thing they share is the token in your cookie that says userId: 7f3a....
Shared identity, independent databases. The team feels like one product. The infrastructure does not.
The procurement bonus
A practical side effect we did not anticipate: because the identity layer is shared, your procurement team gets a single DPA, a single security questionnaire, and a single line item on the invoice. We are still small enough that this matters mostly to the founder filling out a security review at midnight, but it adds up.
SSO is coming, and that is the only roadmap promise
Today, the shared identity layer uses email plus a magic link. That is enough for early teams. We will add SAML and SCIM when enough customers ask, and not before. When we do, it will be a single configuration that lights up every product at once — because the identity layer is one place. That is the whole point.