Admins: technical and configurable Co-browse limits
Which limits each Co-browse tier brings, which are fixed by design, and which an admin can tune per organization.
Watch this step in the video · Simultaneous sessions and limits
This is the technical reference for the Co-browse add-on: what each tier defines, which limits are fixed by design, and which an admin can override per organization.
Per-tier limits
| Tier | Concurrent sessions | Price | Self-serve |
|---|---|---|---|
| Standard | 3 | $50/mo | Yes |
| Pro | 6 | $90/mo | Yes |
| Business | 10 | $150/mo | Yes |
| Enterprise | Custom | Negotiated | No (sales) |
Concurrency is the only limit that changes between tiers. It's the maximum number of Co-browse sessions active at the same time across the whole organization.
Fixed by design
- Session duration: 600 seconds (10 minutes). Identical on every tier. When the cap is reached the session auto-ends, with countdown warnings at the final 60 and 30 seconds.
- Heartbeat: customer and agent each ping every ~10s. If none lands within 30s, the session is treated as dropped and ends to free the concurrency slot.
- Per-agent permission: who can start Co-browse is controlled per user (the
can_start_cobrowsecolumn). By default, while the add-on is active every active member can; the owner can opt specific users out.
What an admin can configure
From the Omnifox admin panel (/admin/organizations/{org}), per organization you can:
- Activate or change the tier of the add-on.
- Override concurrency (
cobrowse_max_concurrent): a manual value that ignores the tier's. Handy for Enterprise customers or one-off adjustments. - Adjust session duration (
cobrowse_max_session_duration_seconds): minimum 60 seconds. Leave it empty to fall back to the tier value (600s). - Deactivate the add-on.
The concurrency override takes priority over the tier. Resolution order: admin override → tier value → 0 (no quota).
Verify
After saving an override, start test sessions up to the new cap: session N+1 should be blocked with "limit reached". For duration, time a session: it should end at the configured time with the 60 and 30s warnings.
If it doesn't work
- The override isn't applied: confirm you saved a number and didn't leave it blank (blank = use the tier).
- "Minimum session duration is 60 seconds": you entered a value below the allowed floor.
- An agent can't start sessions: check that they have
can_start_cobrowseset to NULL or true on at least one active workspace.
Tips
- For Enterprise customers, always set the concurrency override: without it, the Enterprise tier carries no default quota.
- Shortening duration below 10 min suits demos or very short support; you can't extend it beyond the tier limit via self-serve.
Related articles
Related articles
-
What Co-browse is and how to enable it
Co-browse lets you see the customer's screen in real time to guide them better. Learn how to enable it.
-
Co-browse complete guide
Co-browse in depth, in 32 chapters: radar, identified visitors, consent, remote control, masking, marks, voice call, page changes and how a session ends, all real.
-
Co-browse: add-on tiers and pricing
Co-browse is bought separately on any plan: Standard 50 USD/mo (3 concurrent sessions), Pro 90 (6), Business 150 (10) and custom Enterprise.
-
How to start a Co-browse session with a customer
Step by step to invite the customer to share their screen and guide them in real time.
-
Prerequisites for using Co-browse
Before you start your first Co-browse session, check the add-on, your permissions and the Webchat channel conditions.