On this page
  1. What is not counted
  2. The ceilings you can meet
  3. Ceilings counted against a clock
  4. What a refusal looks like

Data

Fair use

This page lists the ceilings a workspace can meet and what happens at each one.

A ceiling here refuses one new thing. It never removes, hides or prunes what the workspace already holds, and at every ceiling below the library stays readable, searchable, assemblable and exportable.

What is not counted

Members, snippets, collections, documents, templates and shared libraries are uncapped, and so is revision history: every save that changed something stays readable as long as the snippet does. There is no storage ceiling.

The ceilings you can meet

  • One imported file — 10 MB for all three kinds that come in: Markdown, plain text and code. File formats lists the extensions and the largest file beside each. Over it, the row names the size and the kind it measured.
  • One image in the editor — 10 MB, in the Rich editor, the only mode that takes one. Over it the refusal names both sizes, the ceiling as 10.0 MB.
  • Cues on one snippet — 40. The band under the editor's body says so at the ceiling; cues covers the rest.
  • Collection nesting — at the deepest level New collection is present and off, reading Nesting is limited to five levels.
  • One diagram's source — 20,000 bytes. Over it nothing is drawn: the document preview in pane 3 puts the message where the picture would be, and the Rich editor keeps the source on screen with the message under it. The message ends nothing is removed and it still exports. Split it into two diagrams and both draw.
  • One file from a GitHub repository — 1024 KB. Over it the file is not imported and no row names it: the import's last line counts only what came in. One import lists up to 2,000 files from a tree.

Ceilings counted against a clock

Some things are counted per period rather than in total: sign-in codes sent to one address, codes asked for from one connection, sign-in attempts against one address, invitations sent from one workspace, and the Live Answers requests that reach the model — detection, answering and documentation lookup, each per member.

A refusal names what the limiter measured, when there is a number to name: the invitation one states how many have gone out from this workspace in the last hour, then The ones already sent still work and when the next one can go out. The Live Answers ones carry no count — a docs line reads Too many docs lookups in a minute, so this one waits for the after-call pass. and the call carries on. Ten docs lookups to a call is the most, and the line says so.

What a refusal looks like

It is never a banner, never a modal, never proactive, never an email, and it never sends you to a price. Most are inline at the control you pressed, naming what the limiter measured, what still works and what to try next; the import list's row carries the size and the limit, with no code and nothing to try. Some carry a stable code — error codes lists them.

Note: a refusal is the whole consequence. Nothing is deleted, hidden, or kept from exporting by a ceiling — see Retention for the one thing you can read that goes on a clock.