Connections count collaborative editing instances, rather than registered users or documents.
When a connection is used
- An instance uses one connection on its first successful submission. Opening a document, read-only access, and editing without collaboration do not count.
- Every submission resets a two-minute timer. The connection is released after two minutes without a submission, or when the page closes or disconnects.
- A later submission uses a connection again. People and agents share the same license allowance; agent operations within an instance already counted do not add connections or tool-call charges.
When editing connection capacity is full
At full capacity, instances that already hold a connection can continue collaborative editing and submitting changes. Only instances that need to acquire or reacquire a connection are affected. Opening documents, read-only access, and non-collaborative editing remain available.
Browser instances that cannot obtain a connection keep changes locally and retry submissions for several minutes. If capacity remains unavailable, those instances switch to offline editing and resume submissions when back online.
Your integration can query connection limits and usage to show a waiting status or set only affected instances to read-only mode. Clearly distinguish locally saved changes from changes submitted to the server.
When an agent cannot obtain capacity
When capacity is full, agent instances that cannot acquire or reacquire a connection receive a capacity error. Instances already holding a connection can continue submitting changes. The SDK does not retry failed submissions automatically.
Connection counting examples| Scenario | Connections used |
|---|
| Editing without collaboration | 0 |
|---|
| Document opened, with no changes submitted | 0 |
|---|
| One instance submits its first change successfully | 1 |
|---|
| One person holds three active editing instances | 3 |
|---|
| Ten people submit changes to the same document | 10 |
|---|
| Two instances on the same page submit changes | 2 |
|---|
| Two independent agent instances submit changes | 2 |
|---|
| An agent operates in an instance already counted | No additional connection |
|---|
| No submission for two minutes; connection released | 0 |
|---|
| Instance keeps submitting on its existing connection at full capacity | 1 |
|---|
| Instance has no connection; browser changes wait locally at full capacity | 0 |
|---|
| Instance acquires capacity and successfully submits a change | 1 |
|---|
| Released connection needs to be reacquired while capacity is full | 0 |
|---|
| Read-only access | 0 |
|---|
Imports are unlimited. Connection capacity and monthly export allowances are independent. Reaching the connection limit does not restrict imports or exports; exhausting the export allowance does not affect editing connections, imports, or native saves.