Upcoming change: Segregation of KM environments
Overview
Starting 6 October 2026, each of your Knowledge Management (KM) environments (for example Staging, UAT, Pre-Prod and Production) will run independently. Content and configuration will no longer be copied automatically from Production to your lower environments.
This means you can set up and test changes in a lower environment without them being overwritten by Production, and move them to a higher environment only when you are ready.
What's changing
| Area | Until 6 October | From 6 October |
|---|---|---|
| Automatic sync from Production to lower environments | Production content, connectors and settings are copied down automatically | Stopped. Nothing is copied between environments unless you choose to move it |
| Bot settings | Copied down from Production | Managed separately in each environment |
| Connector configurations | Copied down from Production | Configured separately in each environment |
| Manually added articles | Copied down from Production | Added and maintained separately in each environment |
| Deleting an article | A deletion in Production also removes the article from lower environments | A deletion applies only to the environment where you make it |
| Changes made in a lower environment | Overwritten by the next Production sync | Kept |
Release timeline
On 6 October, syncs will be paused for a short maintenance window while we complete the release.
- 1:30 AM EDT (11:00 AM IST) — New connector syncs and article syncs are paused in all KM environments. Any sync already running is allowed to finish.
- Once running syncs complete — The release is deployed and your environments become independent.
- Next — Leena AI prepares your lower environments so they start with their current content and configuration.
- Around 6:30 AM EDT (5:00 PM IST) — Syncs resume in all environments.
Maintenance window in your time zone
| Time zone | Syncs paused | Syncs resume (approx.) |
|---|---|---|
| India (IST) | 11:00 AM, 6 Oct | 5:00 PM, 6 Oct |
| UTC | 5:30 AM, 6 Oct | 11:30 AM, 6 Oct |
| UK (BST) | 6:30 AM, 6 Oct | 12:30 PM, 6 Oct |
| US Eastern (EDT) | 1:30 AM, 6 Oct | 7:30 AM, 6 Oct |
| US Pacific (PDT) | 10:30 PM, 5 Oct | 4:30 AM, 6 Oct |
During the maintenance window
- You will not be able to start connector syncs or article syncs.
- Scheduled (auto) syncs that fall inside the window will not run.
- Syncs already in progress at 1:30 EDT (11:00 AM IST) will complete normally.
- Your bot continues to answer end users using content that has already been synced.
- No content will be deleted or moved.
After the release
Your lower environments start where they are today
Your Staging, UAT and Pre-Prod environments keep the content, connectors and settings they have at the time of the release. From that point on, each environment changes only when you change it.
Manage each environment separately
The following now need to be managed in each environment on its own:
- Bot settings
- Connector configurations
- Manually added articles
- Deletions — to remove an article everywhere, delete it in each environment
Connect a lower environment to the same source as Production
You can create a connection in a lower environment using the same source credentials as Production — for example, the same SharePoint tenant or ServiceNow instance. This lets you validate new content sources, permissions and KM features in UAT before rolling them out to Production.
Within a single environment, each content source (such as a SharePoint site library, ServiceNow knowledge base or Confluence space) can be selected by only one connection. This prevents duplicate content.
Move tested changes to a higher environment
Once a change has been validated in a lower environment, use Pull from lower environment in the higher environment to bring over articles, connections and bot settings. Auto-sync schedules are not copied, so set them up in the target environment once you have reviewed the result.
Things to keep in mind
- Production changes no longer reach UAT. If you test in UAT, make sure it has the content you want to test against.
- Source system load. If both a lower environment and Production sync the same source on a schedule, your source system receives requests from both. Keep auto-sync off in lower environments unless you need it, or stagger the schedules.
- Deletions do not carry across environments. Remove content from each environment where it exists.
Recommended actions
Before 6 October
- Avoid planning content updates or connector changes during the release window.
- Let your team know that UAT will no longer mirror Production after the release.
After the release
- Review each lower environment: connectors, article counts and bot settings.
- Check auto-sync schedules in your lower environments.
- Agree on a process for promoting changes: test in the lower environment, then pull into the higher one.
Frequently asked questions
Will my bot be unavailable during the release?
No. Your bot continues to answer end users throughout. Only new syncs are paused.
Will any content be deleted?
No. All existing content in every environment stays in place.
What happens to a sync that is running at 1:30 AM EDT (11:00 AM IST)?
It will be allowed to finish before the release is deployed.
Does this change anything in Production?
No. Production content, connectors and settings are unchanged.
Can I turn automatic sync from Production back on?
No. After the release, environments stay independent.
How do I get Production content into a lower environment after the release?
Set up the same connection in the lower environment and run a sync. Settings and manually uploaded articles on Leena AI will have to be updated manually as per requirement.
Who do I contact with questions?
Reach out to your Leena AI Customer Success Manager
