> ## Documentation Index > Fetch the complete documentation index at: https://docs.linkiasoft.com/llms.txt > Use this file to discover all available pages before exploring further. # How many people can work at the same time > Seats versus people online, how many agents can share one channel, what happens when two people open the same chat, and the limits that actually exist. **Everyone in your workspace can work at the same time.** There is no concurrent-user licence, no limit on how many agents can be online, and no limit on how many agents can share one channel or one WhatsApp number. The only ceiling is **Max users** on your plan, and it counts accounts, not people online.

Seats are accounts, not sessions

| | What it counts | Where it bites | | -------------------------- | ------------------------- | ------------------------------------------------------ | | **Max users** (plan limit) | Accounts in the workspace | Inviting, creating a user, or approving a join request | | People online | Nothing — uncapped | Never | | Devices per person | Nothing — uncapped | Never | When you hit the plan limit, the invitation is refused with *User limit reached* and a prompt to upgrade. Nothing about how many of those people are logged in at once changes that number. Suspended and removed accounts still occupy a seat. Removing someone who has left does **not** free up room for their replacement today — if you removed a user and the limit still blocks you, that is why. [Contact support](/help/troubleshooting/contact-support) or upgrade the plan. See [Plans and usage](/help/billing/plans-and-usage) for the other plan limits, and [Users and invitations](/help/team/users-and-invitations) for the removal order that avoids stranding customers. ## One person, several devices You can be signed in on a laptop, a second tab and a phone at once. Presence is tracked across all of them: you stay **Ready** until your *last* tab closes, so closing one window does not take you out of the rotation. See [Ready, Busy and Off](/help/routing/presence-ready-busy-off). ## Many agents, one channel A channel is not owned by an agent. One WhatsApp number, one Facebook Page or one Instagram account can be worked by the whole team simultaneously — that is the point of a shared inbox. What decides who handles what is not the channel but [assignment](/help/routing/how-assignment-works): new chats go to the eligible agent with the fewest open ones, and a returning customer goes back to the agent who owns them. Add five more agents and distribution simply spreads the same conversations more thinly. The exception is [personal WhatsApp](/help/channels/whatsapp-personal), where the *phone* is the constraint, not the team. One phone holds one linked session and must stay online; your whole team still answers from Linkiasoft, but if that phone goes offline everybody stops at once. It is the main reason to move a busy team to [WhatsApp Business](/help/channels/whatsapp-cloud-api). ## What each person sees Frontline agents see **only the conversations assigned to them**. Managers and admins see everything their channel grants allow. This is what stops a ten-agent team from tripping over each other: in normal use, no two agents are looking at the same chat. Where two people *can* see one chat — a manager and the assigned agent — there is no lock. Both can type, and both messages will send. Assignment is the convention that prevents it, not a technical barrier, so if a manager takes over a conversation it is worth reassigning it rather than answering over the agent's shoulder. Channel access binds on top of all of this: a manager restricted to Messenger cannot open an Instagram chat, however senior they are. See [Roles and permissions](/help/team/roles-and-permissions#channel-access-and-teams). ## The limits that do exist None of these are about how many people are working — but they are what people are usually asking about when they ask this question. | Limit | What it actually caps | | ------------------------------------------ | ------------------------------------------------------------------------------------------------------- | | **Max users** | Accounts in the workspace | | **Max channels** and allowed channel types | How many channels you can connect | | **Units per month** | Active contacts and AI replies, shared from one pool — see [units](/help/billing/plans-and-usage#units) | | **Meta messaging limit** | Unique customers your WhatsApp number may message in 24 hours — a number limit, not an agent limit | | **Meta throughput** | How fast a number may send during a broadcast. Broadcasts are paced automatically | | **Personal WhatsApp session** | One linked phone per channel | ## Sizing a team Because distribution is least-loaded rather than a strict rota, adding agents raises capacity smoothly — there is no rota to rebuild and no setting to change. What actually limits throughput in practice is usually one of: * **Chats left open.** Distribution counts open chats. An agent who never closes anything looks permanently busy and stops receiving work. * **Channel grants.** Ten agents on a role that does not include the busy channel leaves one person carrying it. Check **Roles → the role → Channels**. * **Presence.** With *Only distribute to Ready agents* on, anyone who forgets to go Ready is invisible to distribution. ## Related Who receives which chat, and why. Data scope, channel access and teams. Adding, deactivating and removing people. Every plan limit in one place.