Does Salesforce Knowledge Work in China? Data Residency, ICP & the Alibaba Cloud Instance
Your Salesforce Knowledge base is content stored in your org. On a standard global org that's an offshore Hyperforce region — none in mainland China — so your articles and any personal data in them cross the border under PIPL, and a public help center has no ICP footing. Salesforce runs in the mainland only as Service Cloud on a separate Alibaba Cloud instance. A compliance-first look at the two doors.
Does Salesforce Knowledge work in China?
Whether Salesforce Knowledge works for mainland China is first a data-residency and licensing question, not a speed one. Your knowledge base is content you build and store in your Salesforce org, so China's law responds to where those articles — and any personal data in them — live, and to whether a help center built on them may be operated from inside the country.
Salesforce describes Knowledge as a way to "Create a knowledge base of articles that can be securely shared," articles you can publish "in customer and partner sites and public websites." On a standard global org that knowledge base sits in an offshore Hyperforce region — Salesforce's own options are the U.S., U.K., Germany, India, Japan and more, none in mainland China — so your articles and the personal data they carry leave the country, a cross-border transfer PIPL governs. Salesforce does run in the mainland, but only as Service Cloud — the product Knowledge lives in — "hosted on Alibaba Cloud" since December 18, 2023, a separate, partner-operated instance. The table below is Salesforce's own wording and the rule each path triggers.
This is a risk picture, not a verdict — your duties turn on what your articles contain, your data volumes and whether the help center is public. Our China team can map your Salesforce Knowledge exposure with you →
Compliance snapshot
- ! Your Knowledge articles — and any personal data in them — live in your Salesforce org, offshore on a standard global org
- ✕ A global org has no mainland-China region (Hyperforce: US, UK, Germany, India, Japan — none in China)
- ! A public help center served to mainland visitors from inside China attaches to an ICP filing; an offshore org has no mainland footing
- ✓ Salesforce does run in the mainland — Service Cloud (which carries Knowledge) on a separate Alibaba Cloud instance (GA Dec 18, 2023)
- ✓ A compliant, ICP-filed in-country delivery path exists — an overlay on your org, no rebuild
What Salesforce Knowledge's own documentation says about China
| Fact | Primary source |
|---|---|
| In Salesforce's own words, Knowledge lets you "Create a knowledge base of articles that can be securely shared," and those articles can be "used internally or externally in a range of channels" and published "in customer and partner sites and public websites." The knowledge base is content you build and store in your Salesforce org — so where that org lives is where your articles, and any personal data in them, live. | Salesforce Help — Create a Knowledge Base with Salesforce Knowledge, retrieved 2026-10-08 |
| On a standard global org, that knowledge base sits offshore. By Salesforce's Hyperforce data-residency model, "customer data is stored in the country where their org is located," with region "options for the U.S., U.K., Germany, India, Japan, and more" — none in mainland China. So a global org holds your Knowledge articles and any personal data they carry outside the mainland. | Salesforce — Hyperforce (salesforce.com/products/platform/hyperforce), retrieved 2026-10-07 |
| Salesforce does run in the mainland — but on a separate Alibaba Cloud instance. By its own announcement, Sales Cloud, Service Cloud and Salesforce Platform went generally available "on Alibaba Cloud starting December 18, 2023," to "help comply with the latest data residency regulations." Salesforce Knowledge is a Service Cloud capability, so the mainland path for it is that separate, partner-operated instance — not the global org you already run. | Salesforce Newsroom — Salesforce Sales and Service Cloud on Alibaba Cloud, December 18, 2023 |
| Because a global org holds that content offshore, serving your Knowledge articles and any personal data they contain to and from China is a cross-border transfer of personal information PIPL governs. The handler — you, Salesforce's customer, not Salesforce — must give notice, obtain separate consent, and satisfy one transfer mechanism: a CAC security assessment, the CAC standard contract, or certification. | PIPL Chapter III, Articles 38–43 |
| If your Knowledge powers a public-facing help center for mainland visitors — an Experience Cloud help center, a customer community, a public knowledge site — serving it from inside China attaches to an ICP filing (State Council Order No. 292; MIIT Order No. 33) bound to a mainland hosting resource, which an offshore org has no footing for. And for a CIIO or large-volume handler, personal information collected in China must be stored in the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)). | State Council Order No. 292; MIIT Order No. 33; PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37) |
Sources verified by the 21YunBox compliance team on 2026-10-08.
For a mainland-China audience, the deciding question about Salesforce Knowledge is not how fast an article loads — it is where your knowledge base is allowed to live, and whether a help center built on it may be operated from inside the country at all. Your Knowledge articles are content you create and store inside your Salesforce org. On a standard global org that org sits offshore, so the articles and any personal data they carry leave the mainland, and a public help center served from that offshore org has no footing for the filing a mainland site requires. Salesforce does run inside China — but only as Service Cloud on a separate Alibaba Cloud instance. Those are the paths, and which one you are on decides your exposure.
Salesforce Knowledge in China at a glance
| What decides it | In Salesforce's own terms |
|---|---|
| Where a global org stores your articles | Your knowledge base is content held in your Salesforce org. On a global org that is an offshore Hyperforce region — “options for the U.S., U.K., Germany, India, Japan, and more.” None is in mainland China. |
| Your Knowledge content on a global org | Articles — and any personal data they carry about Chinese customers — are held in that offshore region: a cross-border transfer of personal information PIPL governs. |
| Does Salesforce run in the mainland? | Yes — Sales Cloud, Service Cloud and Salesforce Platform “on Alibaba Cloud starting December 18, 2023.” Knowledge is a Service Cloud capability, so that is its mainland path. |
| Is that your existing org? | No. The Alibaba Cloud instance is a separate, partner-operated path — not the global org your credentials already open. |
| Serving a public help center | A Knowledge-powered help center shown to mainland visitors from inside China attaches to an ICP filing; an offshore global org has no mainland footing for one. |
| Is it reachable? | Reaching Salesforce's cloud from China is generally not the obstacle. The exposure is residency and ICP, which loading the page does not resolve. |
Door one — a global Salesforce org keeps your knowledge content offshore
On a standard global org, Salesforce stores your data in the Hyperforce region tied to that org. In Salesforce’s own data-residency wording, “customer data is stored in the country where their org is located,” and the regions it offers are “options for the U.S., U.K., Germany, India, Japan, and more.” Not one is in mainland China. Your knowledge base is not a file you host somewhere else — the articles are records inside that org — so every article, and any personal data an article carries about a Chinese customer, is held outside the mainland. That, not the paint time, is what China’s law responds to.
Under China’s Personal Information Protection Law, moving that personal information into an offshore org is a cross-border transfer: the handler — you, Salesforce’s customer, not Salesforce — must give notice, obtain separate consent, and clear one transfer mechanism (a CAC security assessment, the CAC standard contract, or certification). The size of the duty scales with volume and role. Under the CAC’s March 2024 cross-border rules, a non-CIIO moving fewer than 100,000 individuals’ non-sensitive personal information in a calendar year is exempt from all three; a critical information infrastructure operator or large-volume handler must instead keep personal information collected in China inside the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)) — which an offshore org cannot do.
Door two — Salesforce in the mainland is Service Cloud on a separate Alibaba Cloud instance
Salesforce does run inside mainland China — but not as a region of the org you already have. By Salesforce’s own announcement, Sales Cloud, Service Cloud and Salesforce Platform became generally available “on Alibaba Cloud starting December 18, 2023,” expressly to “help comply with the latest data residency regulations.” Salesforce Knowledge is a Service Cloud capability, so the mainland home for a knowledge base is that Alibaba Cloud instance — reached and operated differently from your global org, closer to a distinct deployment than a setting you switch on. It is also Salesforce’s own answer to the residency question: in-country hosting on a Chinese partner. So “we already run Salesforce Knowledge” does not by itself place you on compliant footing — being on the global org and being on the Alibaba Cloud instance are two different places, and only one keeps your knowledge content on the mainland.
When an ICP filing enters — a public-facing help center
Data residency is one door; operating a public-facing service is the other. A knowledge base used only by your own agents inside the Service Console turns mostly on the residency and cross-border rules above. But the moment your Knowledge powers something shown to mainland visitors — an Experience Cloud help center, a self-service customer community, a public knowledge site — serving that experience from inside China attaches to an ICP filing (ICP 备案) under State Council Order No. 292 and MIIT Order No. 33, and that filing must bind to a hosting resource physically in the mainland. A global org served from offshore has no mainland footing to file against.
This is a risk map, not a verdict: whether you face a cross-border-transfer duty, a data-localization duty, an ICP filing, or some mix depends on what your articles contain, how much personal data you hold, and who reaches your help center — worth settling with counsel before you build.
Reachable, not the deciding question
Salesforce’s cloud is generally reachable from mainland China, so for most teams the obstacle is not whether an article opens — it is that reaching the content changes none of the facts above. A help center you can load from Shanghai is still served from an offshore org: it still holds your articles and any personal data outside the mainland, and it still has no ICP footing of its own. Those are compliance facts about where data lives and who may operate a mainland service, and no amount of network tuning closes them. (We publish delivery measurements only where we have a clean first-party method; the compliance exposure here does not depend on them.)
Where 21YunBox fits — a compliant overlay, not a migration
You keep running Salesforce Knowledge. We add the piece a global org cannot provide on its own: compliant, ICP-filed delivery from inside the mainland for any public-facing help center or knowledge site built on your org, placed in front of the org you already run — no rebuild, no second knowledge base, and no forced migration onto a different instance. Our China team maps your PIPL cross-border and data-residency exposure against your entity and data volumes, then stands up the in-country delivery and, where the law requires it, the in-country storage a lawful China presence needs — while your Salesforce org stays exactly where it already runs.
Related reading:
Frequently Asked Questions
Does Salesforce Knowledge store Chinese users' data in China?
Not on a standard global org. Your knowledge base is content stored in your Salesforce org, and on a global org that org sits in an offshore Hyperforce region — the options are the U.S., U.K., Germany, India, Japan and more, none in mainland China — so your articles and any personal data in them are held outside the mainland. Salesforce does offer a mainland path — Service Cloud, the product Knowledge runs in, hosted on Alibaba Cloud since December 18, 2023 — but that is a separate, partner-operated instance, not the global org you already run.
Is a Salesforce Knowledge help center subject to China's ICP filing?
If it is a public-facing help center shown to mainland visitors and you want it served from inside China, then yes — an ICP filing (ICP 备案) must bind to a hosting resource physically in the mainland, and an offshore global org has no footing for one. A knowledge base used only by your own agents inside the Service Console turns mainly on the cross-border and data-residency rules instead. Which rules apply depends on what your Knowledge does and who reaches it — worth settling with counsel.
Can 21YunBox help make our Salesforce Knowledge setup compliant in China?
Yes. Our China team can assess your PIPL cross-border and data-residency exposure for your entity, data volumes and users, and — where your Knowledge powers a public-facing help center for mainland visitors — stand up the compliant, ICP-filed in-country delivery it needs, as an overlay on the global org you already run. Get in touch to work through your specific case.
