# Your book club does not need access to your company's Server

> One person, several communities and a refreshing lack of surprise membership.

Source: https://llll.gg/blog/multi-server-identities

You belong to a work team, a book club and a group of friends planning a trip. The work team discusses budgets. The book club discusses a novel. The trip group has spent three days choosing between two restaurants.

These are different communities. They probably don't need one another's membership lists, private conversations or opinions about Chapter Seven.

## Several Servers, several boundaries

In L4, each Server owns its own Accounts and Members. You can belong to several Servers, but access to one does not grant access to another. The same email address on two Servers doesn't automatically link Accounts or establish membership.

The Shell helps you navigate between saved Server connections on a device. A bookmark is a shortcut: it doesn't create an Account or open a private Channel. You can also visit a Server directly at its address.

A Server can have a primary address and configured aliases while retaining the same persistent UUID. That's useful when an address changes without wanting the community to become a completely different Server. Unconfigured hostnames do not automatically become trusted addresses just because they reach it.

## No accidental crossover episode

Direct Messages stay inside one Server. L4 does not currently promise cross-Server DMs or a universal identity that follows you into every community. Each Server's operator is responsible for its own setup and membership.

This may sound less dramatic than a grand unified social graph. It is also nice when your colleague cannot accidentally discover that you gave the book club's favorite novel two stars. Some boundaries are worth preserving.