Sohay works on Multisite. The thing to understand before you plan a rollout is that nothing is shared between sites.
What each site keeps to itself
Every site in the network has its own:
- Knowledge Base articles, categories, and tags
- Conversations and messages
- Settings — provider, model, welcome message, spend caps
- API keys
That last one surprises people. There is no network-level key. Each site stores and uses its own, and each site’s usage bills against whatever account that key belongs to.
The isolation is deliberate. A network is often several unrelated businesses, and one site’s support conversations have no business appearing in another’s inbox.
Activating
Network-activate to switch Sohay on everywhere. Each site sets itself up on first load — tables, capabilities, and taxonomy terms are created per site, when that site is first visited.
Or activate per site, if only some of them need a chatbot.
Either works. Network activation is simpler when every site wants it; per-site is better when they do not, since it avoids setup work on sites that will never use it.
Planning a rollout
The per-site isolation means the setup work multiplies. For each site that needs a chatbot, someone has to:
- Save an API key.
- Pick a model and set spend caps.
- Write Knowledge Base articles.
- Run the first sync.
There is no “configure once, apply everywhere”. Budget for that before promising a chatbot on forty sites.
Two things make it less painful:
- Spend caps can be set in code, through
sohaychat_usage_tracker_options, so a network-wide default lives in one mu-plugin instead of forty admin screens. - The allowed-model lists can be pinned the same way, with
sohaychat_allowed_openai_models, so no site administrator can quietly move to an expensive tier.
Both are worth doing on a network you do not personally administer site-by-site.
Costs
Usage is billed per key, and every site has its own. If several sites share one API key, they share one bill and one set of provider rate limits — and one site’s runaway loop becomes everybody’s problem. Per-site keys keep the blast radius small.
Sohay’s own daily caps are per site, so they do not add up to a network-wide ceiling on their own.
Uninstalling
Uninstalling from the network removes Sohay’s data from every site.
As on a single site, Knowledge Base articles are kept — they are ordinary WordPress content. To remove those as well, delete them under KB Articles on each site before uninstalling.
