Team Chat limits — channels, custom emoji, saved items and search history
A workspace can hold 2,000 channels and 5,000 custom emoji. Each person can keep 1,000 saved items. Search reaches back over the same history the workspace's plan keeps: if the plan never deletes messages, search never drops them; a plan with a bounded history keeps a bounded search window. No limit here removes a control from anyone — plans differ only in how much they hold.
The numbers
| What | Before | Now | Where it is decided |
|---|---|---|---|
| Channels per workspace | 200 | 2,000 | ABUSE_CEILINGS.max_team_chat_channels_per_workspace |
| Custom emoji per workspace | 200 | 5,000 | CUSTOM_EMOJI_WORKSPACE_MAX |
| Saved items per person | 200 | 1,000 | SAVED_CAP |
| Search history | 400 days for everyone | the workspace's message history | search-index.ts |
Channels
The channel count is enforced in teamChatCreateChannel, which counts a workspace's channels
(DMs excluded) before it creates another and refuses with "This workspace already has the most
channels it can hold." The plan limit still applies underneath it — a free workspace keeps its
smaller allowance, and a paid plan that lists channels as unlimited now really can reach 2,000.
The desktop sidebar listens for the channel list up to CHANNELS_LISTEN_LIMIT, raised to 2,000 so
a full workspace is actually visible. A workspace under the old limit reads exactly what it read
before — the listener cap only costs anything in workspaces that fill it.
The HTTP channel list used by the API keeps paging: 1,000 channels per page with a nextCursor,
so a caller asking for a full 2,000-channel workspace makes two bounded reads rather than one
giant one.
Custom emoji
CUSTOM_EMOJI_WORKSPACE_MAX is a client guard, not a Firestore rule: uploadCustomEmoji counts the
workspace's emoji on the server (getCountFromServer) before it touches Storage, and refuses at the
cap with "This workspace already has {limit} custom emoji, the most it can hold." The emoji picker
and the plugin API both read the same constant. The picker's listener was raised with it
(CUSTOM_EMOJI_LISTEN_LIMIT), so every emoji in a full workspace can be shown.
Saved items
Saved items live in one saved/{uid} document per person. 1,000 rich snapshots can reach
Firestore's 1 MiB document ceiling, so the cap is enforced two ways: the count (SAVED_CAP) and a
byte budget (SAVED_DOC_BYTE_BUDGET). Whichever is reached first, the save is refused with the
same "saved items are full" message instead of failing in Firestore — un-saving always works.
Typical saves are a few hundred bytes each, so the count is what a person actually meets.
The Firestore rule that guards the same document (maxSavedItems() in firestore.rules) carries
the same 1,000, so the app and the rules can never disagree about a save.
Search history
Search reads a mirror of each message, and that mirror carries an expireAt field a Firestore TTL
policy uses to age it out. The horizon now follows the plan:
- Free keeps the window it had:
SEARCH_INDEX_RETENTION_DAYS_DEFAULT(400 days). - Every paid plan — Pro, Team, Enterprise and Developer — gets no
expireAtat all, so everything the workspace keeps stays searchable, however old. - A tier the system cannot read resolves to free, never to unlimited.
The plan reaches the indexer through search-plan.ts, which reads the workspace owner's live
tier claim and caches it per tenant for the write path. When a workspace changes plan, the hourly
retention sweep moves the matching index rows in the same pass and clears expireAt when the
tenant became uncapped, so a stale window can never outlive the plan that set it.
What to know
- Nothing here is a feature gate. Every plan can use custom emoji, saved items, search and channel bookmarks; only the amount changes.
- A very full workspace costs its members more reads on first open, because the sidebar and the emoji picker stream the whole list. Workspaces below the old limits see no change.
- A deployment of
firebase/functionsis required for the channel ceiling and the saved-items cap;firestore.rulesneeds one for the saved-items rule. The desktop limits ship with the app. - Free and paid keep the SAME search window rule as the rest of this page: search history is a quantity, so a paid plan keeps more of it and free keeps what it always had.
Last verified 2026-11-20