Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.
Does Miro Work in China for Team Collaboration?
Jason Chen
October 5, 2026· 10 min read
Does Miro work in China? Test your actual permitted mainland connection before a workshop: this guide has no nationwide result, and Miro says a working dashboard does not prove the WebSocket-dependent board will work. Prepare authentication, permissions, live-edit checks, and an authorized export backup.［1］
Key Takeaways
- A dashboard, loaded board, and synchronized edit are different success criteria.
- SSO and board access belong to the organization and board owner.
- Check both participants' live edits, not only your own visible changes.
- An exported PDF or image is a snapshot, not a complete offline editing mode.
Use the China connection planning checklist before the session. If unrelated services fail together, the mainland app diagnostic helps you investigate the wider network layer.
Does Miro work in China beyond its home page?
Miro board loading involves more than displaying the public website. Miro's network help specifically describes a case in which the dashboard and settings open but boards do not, because WebSocket connectivity is unavailable. That makes the board itself the meaningful test target for a workshop.［1］
The official domain reference also lists multiple service dependencies. A managed network may permit one domain while filtering another required resource. Use the current reference through your administrator rather than maintaining an old copied IP list or assuming the home page's address represents every dependency.［2］
None of those documents provides a fresh mainland measurement for your device. A board that worked on another network or last month is useful preparation context, but it is not proof of the route you will use in the meeting. Record the date and connection when you test the actual session.
In mainland China, Article 6 of the Interim Provisions on International Networking of Computer Information Networks (2024 revision) requires direct international connections to use gateways provided by the national public telecommunications network and prohibits units and individuals from independently establishing or using other channels. Article 14 provides penalties for violations.［5］ Confirm the meeting route and applicable requirements before rehearsing a board connection; organizational approval is not a legal ruling, and a technical synchronization test cannot establish permission for the network or the workshop materials.
What should you verify before the meeting?
Prepare the exact board and participant roles. Ask the owner to confirm who may view, edit, export, or invite others. Check the meeting device, normal login method, and organizational requirements while support is available; do not make the first sign-in attempt at the workshop's start.
| Time | Useful check | Backup or stop condition |
|---|---|---|
| Before the meeting | Sign in with the intended account and SSO route | Ask the identity administrator about access failures |
| Before the meeting | Open the actual board and required assets | Resolve board permission and resource issues |
| Before the meeting | Compare a small authorized edit with another participant | Confirm that both sides see the same saved state |
| During the meeting | Watch connection warnings and remote updates | Pause important edits when synchronization is uncertain |
| After a disconnection | Confirm the visible work reached the shared board | Reconcile versions before continuing |
| For a fallback | Open an authorized export outside Miro | Treat it as a dated snapshot, not live editing |
Use non-sensitive sample content for the connection check. A disposable note or shape in an approved test area is enough to establish whether both participants can see an update. Record who changed what and whether the other participant saw it; your local display alone is not a shared-state test.
Save the board name, owner contact, approved meeting channel, and backup location somewhere that does not depend on Miro loading. Keep private board links and confidential material out of public troubleshooting reports. Agree on when to pause or switch to the backup so the decision does not depend on a facilitator's guess during the meeting.
How do SSO and board permissions differ from connectivity?
Miro's SSO documentation describes organization-managed authentication. The intended identity provider, account, organization, and session requirements are separate from whether a browser can reach the board service. A login failure can require the identity administrator, not a different route.［3］
A successful sign-in does not establish permission to open or edit every board. Check the intended team and account, invitation, and role with the board owner. Do not create a personal account or move work into a public board to evade the organization's controls.
If the board is visible but read-only, ask whether your assigned role permits editing. If resources embedded in it do not load, identify their own source and permissions rather than assuming all of Miro is unavailable. An external document or design integration may have its own authenticated service.
For that design dependency, Figma workflow preparation separates files, sign-in, permissions, and editing. Success in one service does not establish that the other service or an embedded connection works.
How should you check Miro real-time collaboration?
Miro real-time collaboration requires participants to agree on the shared state, not merely see an editable canvas. Open the intended board from both permitted connections and compare one small change in each direction. Then reconnect once and confirm the change remains visible to both participants.
Keep the browser, account, board, and short time window fixed when comparing another permitted route. Record board loading, asset loading, remote updates, and reconnection separately. Do not infer a guaranteed future session from one brief successful check.
Where local law, organizational policy, and Miro terms permit it, use AethoVPN for a rehearsal of the board connection: choose an appropriate nearby position from the current in-app list, open the same board, and ask a collaborator to verify the sample edit arrives. iPhone, iPad, and Mac configuration requires Pro or Premium. This route does not assign an SSO identity or board role and does not guarantee synchronized edits; start the 3-day Pro trial to prepare the rehearsal if needed, with one trial per new user.
Miro's network help suggests trying another connection and using or turning off a VPN for WebSocket-related trouble. A tunnel may therefore improve one route or interfere with another. On a managed network, ask the administrator to follow Miro's current domain and connection guidance rather than personally disabling firewall or security policy.［1］［2］
What should you do when the board disconnects?
Pause edits that cannot safely be lost or duplicated. Record which action was in progress, which participants still have a connection, and whether a warning is visible. Keep the application available long enough to inspect its state instead of reflexively refreshing, deleting browser data, or signing out.
When the route returns, compare the relevant area with another participant and confirm which changes exist in the shared board. A locally visible object can be misleading when the connection was interrupted. Reconcile differences with the facilitator before repeating changes; otherwise two people may recreate the same note or overwrite a later version.
Use an approved note-taking channel for decisions while the board is unavailable. Record the facilitator, time, decision, and responsible person so the result can be transferred back without guessing. Do not put confidential workshop content in an unapproved public chat just to keep the session moving.
If the board remains unreliable, switch to the agreed snapshot or another approved collaboration method. A read-only fallback can keep discussion moving, but it does not provide Miro's complete editing or synchronization behavior. Tell participants which version they are reviewing.
What can Miro board export preserve?
Miro board export can provide an image, PDF, or CSV according to the plan, device, browser, and board settings. The board owner may restrict export, and some formats or quality levels are unavailable in certain contexts. Verify the actual export action before relying on it as a fallback.［4］
Inspect the output outside Miro. Confirm that the required frames, labels, and information are readable at the size participants will use. Do not assume every interactive element, comment, embedded item, or relationship survives; a CSV or static image serves a narrower purpose than the board.［4］
Keep the exported file's date and version with the meeting materials. Limit distribution to authorized participants and use the approved retention and sharing policy. Export permission is not automatically permission to post confidential content publicly.
For a separate file handoff, WeTransfer delivery planning explains sender and recipient checks. That service has its own mainland access and IP restrictions, so it should not become an untested single backup for your Miro export.
When should the team stop troubleshooting?
Stop network changes for an SSO refusal, missing invitation, restricted role, prohibited export, security warning, or organizational policy decision. Ask the relevant administrator or board owner to resolve the condition. No successful route gives a user permission to act beyond the assigned role.
If several participants fail on different connections, inspect the official service status and contact Miro support through the approved process. That helps distinguish a broader incident from one route, although a green status page does not establish that every participant's connection works.
Provide sanitized evidence: browser and version, connection type, time, affected action, and a minimal reproducible description. Remove private board URLs, session material, personal identifiers, and confidential screenshots from public reports. The useful evidence is the failing layer and observed result, not unrestricted access to the workshop.
Summary
- Test authentication, board access, assets, and shared edits separately.
- Prepare the actual participant roles and the identity administrator contact.
- Pause during uncertain synchronization and reconcile the shared state afterward.
- Verify an authorized export and label it as a snapshot.
FAQ
Is Miro confirmed reachable everywhere in mainland China?
No nationwide result is established here. Test the actual board on the permitted connection and keep the observation's date and network with the meeting plan.
Why can the dashboard work while the board fails?
Board pages require WebSocket connections, according to Miro. A network can allow the dashboard while filtering the connection the board needs.［1］
Does signing in prove I may edit a board?
No. Authentication and board permissions are separate requirements. Confirm the intended account, team, invitation, and editing role with the owner before troubleshooting the route.
Can a VPN guarantee live edits synchronize?
No route guarantees synchronized collaboration. Rehearse a small edit in both directions and confirm the shared state rather than judging only your local canvas.
Should I repeat edits immediately after a disconnection?
Check the shared board with another participant first. Repeating an uncertain operation can duplicate notes or conflict with changes that already reached the board.
Is a PDF export a complete offline Miro editor?
No. A PDF is a static snapshot, not the full board's interactive editing environment. Inspect the actual export for the information your meeting needs.
Why might export be missing or incomplete?
Export depends on board permissions, plan, device, browser, and format. Ask the owner to verify the supported option and inspect the output before the meeting.［4］
Disclaimer: VPN regulations vary by country and region and are subject to change. This article does not constitute legal advice. Please review and comply with your local laws before using a VPN.
Sources
- Miro — Add Miro to allowed apps — https://help.miro.com/hc/en-us/articles/360017572694-Add-Miro-to-allowed-apps
- Miro — Miro domains reference — https://help.miro.com/hc/en-us/articles/20857452690706-Miro-domains-reference
- Miro — Single sign-on (SSO) — https://help.miro.com/hc/en-us/articles/360017571414-Single-sign-on-SSO
- Miro — How to export your board — https://help.miro.com/hc/en-us/articles/360017572754-How-to-export-your-board
- 中华人民共和国计算机信息网络国际联网管理暂行规定（2024 年修订） — https://xzfg.moj.gov.cn/front/law/detail?LawID=1713
Sources checked 5 October 2026.
Related Articles:
