Why Orchestrate Global SaaS and China Apps Together

If a company uses both global SaaS and DingTalk, WeCom, or Feishu, connecting a separate assistant on each side often breaks work that must cross both: permissions are maintained twice, and confirmation for writes is scattered. FIM One, from Beijing FIM Network Technology Co., Ltd., is a self-hosted agent platform for this kind of use: it connects existing systems, orchestrates work across them in one place, pauses for a person to confirm a write, and records each operation. The license is source-available; the repository terms govern specific uses.

Companies that use both global SaaS and DingTalk, WeCom, or Feishu can often get by with a separate assistant on each side for everyday questions. Once a task has to cross both sides, for example when someone asks for a status in a collaboration app and the answer has to come from a business system on the other side, the two assistants no longer line up: permissions are maintained twice, the sources are split, and confirmation for writes does not sit in one place.

Finishing that kind of work takes more than “both sides can connect.” It takes orchestration in one platform: there may be several entry points, but systems and permissions are maintained once, steps across systems follow the same rules, and a person confirms a write before data is changed. For how cross-system work is orchestrated, see the orchestration notes. FIM One, from Beijing FIM Network Technology Co., Ltd., is a self-hosted agent platform for companies that use both global SaaS and DingTalk, WeCom, or Feishu: it connects existing systems, orchestrates work across them, pauses for a person to confirm a write, and records each operation. The license is source-available. The sections below explain why orchestration should sit in one platform. They do not repeat how to connect the two sides, and they do not describe a particular connection method.

1. A separate assistant on each side cannot finish cross-side work

It is common, and not in itself a problem, for overseas teams to use global SaaS and domestic teams to use DingTalk, WeCom, or Feishu. The problem appears when a task must use entry points and systems on both sides. If the assistants are also split by side, three things fall out of line:

  • Identity and permissions are maintained twice. If the same person’s permissions are configured separately, a change of role or a departure is easy to miss on one side.
  • Knowledge and sources are split. If the systems or files that support an answer are not managed in one place, the same question may receive different answers on the two sides.
  • Confirmation for writes is scattered. A write should wait for a person to confirm it. If confirmation happens in different assistants, it is later hard to see who agreed to which write.

So “both sides can connect” only solves the entry point. To finish a piece of cross-side work, the steps still have to be orchestrated in one place.

2. Orchestration in one platform means several entries, and one set of rules

FIM One is used in three steps: connect existing systems, orchestrate work across them, and wait for a person to confirm a write before it runs. For a company that uses both global SaaS and domestic collaboration apps, keeping these three steps in one platform means:

Collaboration apps can be connected as several entry points, and business systems can be connected behind them as tools, but the assistant and the permissions are built once. Steps that cross systems follow the same orchestration, rather than finishing the first half in one assistant and the second half in another.

A write pauses before it runs, a responsible person confirms it, and the operation is recorded. This step is meant to stop a change from being written before anyone has seen it, or a write to the wrong record, on unclear grounds, or with no way to tell who agreed. For what this step is meant to stop, see What human confirmation before a write is meant to stop. The confirmation rules should also be maintained once, not as two unrelated sets on the two sides.

How to connect both sides into one set of permissions and data scope is already described, step by step, in When you already use global SaaS and DingTalk or Feishu, how to connect one AI assistant. This article does not repeat those connection steps. It only stresses that after the connections are in place, cross-side work still has to be orchestrated in one place; otherwise the connections themselves will not fix the mismatch.

3. Write down first which tasks must be orchestrated across both sides

Not every question has to be handled across systems. A query that can be answered on one side can stay on that side. What belongs in one platform is the work that cannot be finished without systems on both sides. Write those tasks down before you start: which entry point starts the work, which systems are called, who confirms a write, and whether the data may be used across sides.

Whether data may cross a border should be confirmed first by legal or compliance. Restricted data should be used only where it is allowed to sit, and should not be aggregated to the other side by default. Those boundaries should also be written into the orchestration note, not added after the work is already running.

FIM One can be self-hosted. The Community edition has the complete feature set and can be self-hosted on an ongoing basis; look at Enterprise when extra support is needed. The license is source-available, and specific uses follow the terms in the repository. These are platform conditions. They do not replace the task note above.

Connecting both global SaaS and DingTalk, WeCom, or Feishu only means the entry points are in place. To finish work that crosses both sides, the tasks still have to be orchestrated in one platform: permissions and sources maintained once, and confirmation for writes sitting in the same place. Write down which tasks must cross both sides before you start connecting and orchestrating, so the two sides do not each go their own way.

FAQ

**Can the two teams keep using their own collaboration apps?**Yes. The apps can be connected as entry points. What needs to be unified is the system calls, permissions, and write confirmation behind them, not a requirement that everyone switch to the same tool.

**Does every question have to go through cross-system orchestration?**No. A query that can be finished on one side does not have to be pulled to the other side. Use orchestration for tasks that must use systems on both sides.

**Can write confirmation be set separately on each side with no connection between them?**You can name a confirmer per task, but the rules should be maintained in one platform and recorded in the same way. If they are fully split, it is later hard to match who agreed to which write.

Back to all articles
Two ways to run

Try it in the cloud today.