How SGEN handles platform updates
How to stay current with SGEN platform updates
SGEN ships updates regularly — bug fixes, feature additions, performance improvements, security patches. This page explains what to expect on your side as a customer: when updates happen, what changes you see, how you find out, and what to do if something looks different than yesterday.
The short version: updates land in the background. You almost always continue working through them with no visible impact. When a change does affect your day-to-day workflow, you hear about it ahead of time.
This guide also walks through the small set of habits that keep you informed without adding load to your week — subscribing to the changelog, watching the status page during launches, and looping your team in when something useful ships.
What is this for?
This page answers questions customers ask about platform updates:
- How often does SGEN update? What is the cadence?
- Will updates interrupt my workflow? Should I plan around them?
- How will I know what changed? Where do change notes appear?
- Do I need to do anything when an update lands? Is there manual action required?
- What if an update affects how my site works? What happens to existing pages?
- Where do I find out about features I can opt into? Beta features, early access programs.
Customers operating mission-critical sites particularly care about the third and fourth questions. Operators who run on autopilot mostly care about whether anything will break.
The high-level answer: SGEN's update model is built around staying out of your way. Most updates are invisible — bugs you never noticed get fixed, performance improves quietly, security stays current. Updates that change visible behaviour get communicated ahead of time through the changelog.
For operators with mature teams: the update model rewards habit. A five-minute monthly read of the changelog plus opt-in email notifications is enough to never be surprised by what the platform can do.
For agencies and multi-site operators: building a "what changed this week on SGEN" segment into your team's weekly sync turns the changelog from a passive document into an active part of your operations rhythm.
Good use cases
Reading this page before launch sets expectations: updates are unlikely to affect a launch week unless you have specifically opted into a beta feature.
The agency can show "what has improved since last quarter" by pointing to the changelog. Customer-visible improvements over the last 90 days are listed.
The changelog is the first stop — if the change is mentioned, it is intentional and recent. If not, the support team is the next stop.
They get updated together. Every site under the platform runs the same version at any given time; there is no per-site update pinning.
The changelog filters by area. Subscribe to updates affecting your most-used areas.
Reading the recent changelog gives a quick read on which areas of the platform are getting active investment and which are mature.
Update cadence and quality is a signal of the platform's health. The public changelog shows steady investment.
The changelog doubles as a source for what is new since the last training pass. Refresh training docs from changelog entries.
What NOT to use this for
While the platform makes updates non-disruptive by default, occasional changes affect visible behaviour. The advance-notice process exists precisely so you can prepare.
Updates apply automatically. There is no "install update" action; the platform stays current on its own.
SGEN runs one version. There is no version pinning, no rollback to a previous version for your site, and no way to opt out of updates.
Updates do not change the need to watch your site's analytics, forms, and visitor experience. If something on your site stops working after an update, it usually has a clear root cause; investigate.
The changelog reports what has shipped. For what is coming next, see the public roadmap if available.
Some industries require version-pinning for compliance reasons. SGEN's continuous-update model does not support that. Industries with compliance constraints around platform versioning need to evaluate whether SGEN fits.
The changelog reports platform changes. It does not replace your own vendor-management practices for tracking changes to the tools your business depends on.
How this connects to other features
The customer-facing changelog is the canonical record of what changed and when. Subscribe to it for ongoing updates.
A separate page reports current platform health. Updates that affect availability — rare — show on the status page in real time.
Records actions you and your team take. It does not record platform updates. The two are separate streams.
Updates do not reset analytics. Historical data is preserved across updates.
Updates do not affect site backups. Your site's backup history is preserved through updates.
Updates that change platform behaviour are tested against documented features. If your site relies on undocumented behaviour, a future update could affect it; stick to documented features for predictable behaviour.
Forward-looking view of what is coming. Pairs with the changelog as the backward-looking view of what shipped.
Some plan tiers expose features that are still in beta. Beta features are clearly labelled in the admin; opting in is explicit.
Before you start
Nothing to set up — the update model is automatic. A few things to know:
- Subscribe to changelog notifications. Get an email when customer-visible updates ship. Available at Account → Notifications → Changelog Email.
- Bookmark the changelog page. Public changelog is at the documentation site. Check it monthly even if you have notifications on.
- Watch the status page during high-traffic events. If you are running a big launch, having the status page open is a quick reassurance that anything unusual is reported.
- Plan around announced changes. When the changelog announces a breaking change with a future date, plan your workflow updates ahead of that date.
- Document your workflow. A short doc on "how my team uses SGEN" makes it easy to spot whether an update affects you. Without documentation, the impact assessment is guesswork.
- Pick a cadence for review. Some teams read weekly, others monthly. Either works; consistency matters more than frequency.
- Decide who on your team owns "platform awareness." One person on each team is usually enough — the person who watches the changelog and surfaces important entries to others.
Where to go
The relevant pages:
- Changelog. Public, customer-facing record of every notable update. Filter by area, date range, or impact type.
- What's New. Highlights of major launches and improvements. Less detailed than the changelog, more curated.
- Status page. Real-time platform health. Shown during incidents; otherwise reports "all systems operational."
- Account → Notifications → Changelog Email. Subscribe to email updates.
The changelog page supports a search box at the top. Search by feature name, area, or keyword to find historical entries. Search results sort by date descending — newest first.
The What's New highlights are curated; not every changelog entry becomes a highlight. The highlights focus on launches and major improvements; smaller fixes go to the changelog without a highlight write-up.
Steps — Stay current with platform updates
1. Subscribe to changelog notifications
Open Account → Notifications → Changelog Email. Pick a cadence (weekly digest is the common choice). Confirm your email address. You start receiving updates the next time the platform ships customer-visible changes.
The first email arrives within a week — sooner if the platform ships something noteworthy soon after you subscribe.
2. Bookmark the public changelog
The changelog lives on the documentation site. Bookmark it in your browser. Open monthly even if you have email notifications — sometimes seeing the list of changes prompts you to try a feature you missed in the email.
A useful habit: drop the changelog bookmark on the same browser bar where your admin URLs live. The proximity makes it natural to check both.
3. Filter to areas you care about
The changelog supports filters: by area (admin, builder, forms, analytics, performance), by date, by impact level (visible change, behind-the-scenes improvement, fix). Filter to your most-used areas for a focused view.
If you primarily build with the page builder, filter to Builder and design. If you spend most of your time on Forms and Analytics, filter there. Filters narrow the volume to the entries that affect your day.
4. Plan around announced breaking changes
Breaking changes — rare — are announced ahead of time. The announcement includes the date the change takes effect and what you need to do (if anything) to adapt. Add the date to your calendar; complete any required prep before the date.
A small habit that pays off: when you read about an upcoming breaking change, immediately add it to your team's planning doc with the prep date a week before the change date. The week's buffer absorbs any last-minute coordination.
5. Watch the status page during launches
If you are running a launch or campaign with high visibility, keep the status page open in a browser tab during the launch window. Any platform-wide incident shows there in real time.
Bookmark the status page separately from the changelog. They serve different purposes — the changelog is "what changed," the status page is "is everything working right now."
6. Read the monthly highlights post
If the change volume is high, the monthly What's New highlights post is faster reading than the full changelog. Subscribe to it for a curated summary.
The highlights post covers the launches and major improvements. Smaller updates (fixes, refinements) live only in the full changelog.
7. Try new features when they ship
When a new feature appears in the changelog, opening it and giving it a 5-minute exploration is the fastest way to know whether it fits your workflow. Most new features have a "Get started" pointer to the relevant docs.
Block 15 minutes once a week for "platform exploration" — open whatever shipped in the last week and try one or two features hands-on.
8. Follow up on changes that affect your workflow
If an update changes how a feature works, read the related doc to confirm your team's workflow still applies. Most changes are additive — the old way still works — but occasionally a workflow becomes a hair more efficient after an update.
When you find an efficiency-improving change, update your team's workflow doc. The next teammate who follows it benefits.
9. Loop your team in
If your team has shared admin access, forward changelog emails or summarize at your team's regular sync. A 30-second mention of "new feature in Forms" prevents one person discovering it and others not knowing for months.
A shared team channel for "Platform updates" works well for teams of three or more. Drop the weekly digest there; let teammates react to entries they find interesting.
What success looks like
A customer staying current with platform updates feels like: For a small operator: subscribing to the monthly digest is enough. Five minutes per month keeps you current. For a large team or agency: forwarding the weekly digest to a shared team channel makes update awareness collective rather than individual. For an operator running mission-critical sites: pair the changelog with the status page and a habit of checking both before any major site change you make. For a brand or marketing team: the changelog is also a content-marketing input. Improvements to features your customers see (like the Generate Alt Text button) are talkable in your own customer communications. For a customer-success or sales team: knowing what is new on the platform is a relevant input for customer conversations. The changelog gives the source material.
- You hear about new features within a few days of release, not months later.
- Breaking changes never surprise you — you saw the announcement and adapted before the date.
- Your team's workflow document stays current as features improve.
- When a teammate asks "did SGEN add X?" you can answer with confidence (either yes-here or not-yet).
- Status page is open during high-stakes launches and gives quick reassurance.
- Your team has a consistent place — Slack channel, internal doc, or weekly email — where updates get shared.
What to do if it does not work
Less-obvious cases:
Reload the admin and the public site to confirm the change is visible. Check the changelog for related entries. If the change is unintentional on the platform's side, contact support with screenshots.
First check the changelog — features rarely disappear, but they sometimes move. Search for the feature name. If genuinely removed, the changelog usually has a transition note for the replacement.
Confirm the subscription is active at Account → Notifications → Changelog Email. Check your email's spam folder. If the email address is wrong, update it.
The advance notice should have included migration steps. Re-read the changelog entry. If steps are unclear, contact support.
That happens — incidents can affect some accounts and not others, or affect features you do not use. The status page reports platform health; your site experience is the ground truth.
Could be a brand-new issue not yet documented. Reproduce reliably (steps, screenshots) and contact support. The support team can correlate with platform events on their side.
Some features roll out gradually. Wait 24 hours; if still not visible, check that your plan tier includes the feature. The changelog entry usually notes any tier requirements.
Worked example — Acme Coffee adapts to a forms update
In April 2026 the platform announced a Forms area improvement: a new "Generate Alt Text" button on media uploads. Acme Coffee's content lead saw the announcement in the weekly digest the following Monday.
The content lead:
- Read the changelog entry. Two paragraphs explained the new button, what it does, and where it appears.
- Opened the media library to try the feature. Uploaded a new product image, clicked Generate Alt Text. The platform suggested an alt text; the content lead refined it and saved.
- Decided to use the feature going forward. Updated the team's content checklist to mention the new button as the default path for alt text.
- Forwarded the changelog email to the rest of the team. With a one-line note: "Use this on new uploads. Saves a step."
Total adaptation time: 15 minutes. The feature became part of the team's workflow the same week it shipped.
Worked example — Agency handles a breaking-change announcement
In March 2026 the platform announced an upcoming change to how form submissions get archived after 90 days. The change was scheduled for May. Acme Studio runs sites for eight clients; the agency operations manager handled it:
- Read the changelog entry as soon as it appeared. Two-paragraph announcement, scheduled date in May, link to a deeper migration guide.
- Drafted a short note for each client. Explained the change, what the client would see, what (if anything) the client should do.
- Sent the note to all eight clients three weeks before the change. Two clients responded with clarifying questions; the agency answered both within a day.
- Marked the change date in the agency's calendar. Two days before, the operations manager did a final pre-flight check on each client site to confirm everything was in order.
- On the change date, confirmed sites were unaffected. No client reported issues. The change landed quietly.
The advance notice meant the agency was ahead of the change rather than reacting after. Most breaking changes go this way when teams subscribe to the changelog.
Notes on the update model
A few details worth knowing:
Updates are continuous, not scheduled. There is no maintenance window. Updates land throughout the week, mostly during business hours in the platform's primary time zone. They do not require taking the platform down.
The platform stays available during updates. You can keep working through a routine update. The admin may briefly flash a "refreshing" indicator if a UI change lands while you have the admin open; refreshing the page picks up the new version.
Customer data is unchanged by updates. Your content, your media, your form submissions, your analytics history — all preserved through every update. Updates change platform code; they do not change customer data.
Some updates are platform-tier-gated. A feature might appear on higher-tier plans before rolling out to lower tiers. The changelog notes tier requirements.
Breaking changes have lead time. When a change will affect customer workflows, the announcement comes weeks to months before the change takes effect. The lead time is enough for any operator to adapt.
The platform tests updates extensively before release. Updates pass through automated tests, internal testing, and (for major changes) a soft-launch period before reaching all customers. Issues do still occasionally slip through; the changelog and status page surface them when they do.
Beta features are clearly labelled. Anything still in beta carries a visible Beta tag in the admin. Opting into a beta is explicit; you will not accidentally land on a beta feature.
Deprecations follow a longer schedule than changes. Features marked for sunset typically have a several-month deprecation window before removal. The deprecation appears in the changelog when announced; the actual removal appears when it ships.
Reading the changelog effectively
A few habits that turn the changelog from "another document to read" into something useful:
Lead with your week's questions. Before opening the changelog, write down two or three questions you want answered ("did anything change in forms?", "any speed improvements?"). Skim with those in mind. Most entries will not apply; the ones that do will jump out.
Re-read entries that affect you twice. Once for "what changed?" and a second time for "what should I do about it?" The second pass surfaces the action items.
Note your own use cases in the margin. If your team has a shared notes doc on workflows, jot which changelog entries touched which workflows. Six months later, "remind me why we changed our form-archive cadence?" has a clear answer.
Use the changelog for training. When onboarding a new teammate, point them at the last 90 days of the changelog. It is one of the fastest catch-up paths.
Treat the highlights as marketing-input. The biggest improvements are the things customers might want to hear about. Brand-marketing teams can repurpose highlights into customer communications.
Common questions
How often does SGEN ship updates? Continuous. Customer-visible updates land roughly weekly to bi-weekly. Behind-the-scenes improvements (performance, security, bug fixes) ship more often.
Can I roll back an update? Not on the customer side. SGEN runs one platform version. If an update introduces a regression, the platform team rolls it back centrally — your action is not needed.
Will updates ever cause downtime? Routine updates do not. Major migrations occasionally require a brief maintenance window, which is always announced in advance.
Do updates affect my site's appearance? Almost never. The platform separates platform code from your site's design. Updates change the platform, not your site's content or theme.
Where do I report a bug that might be from a recent update? Contact support. Include the date you noticed the change, what you were doing, and screenshots if possible.
Can I opt out of a specific update? No. Every site runs the same platform version. The platform-wide testing process exists to make opt-out unnecessary.
Does subscribing to the changelog email cost anything? No. The subscription is free for every plan tier.
What happens if I am offline when an update lands? Nothing. The next time you sign in, the new version is what you see. You did not miss anything.
Are there beta features I can try early? Some plan tiers include a beta program. Check Account → Settings → Beta Features if your plan offers it.
How do I know what is rolled out vs in beta? The changelog distinguishes between "generally available" entries and "beta" entries. Beta entries note the access path.
Can I delay an update because I am about to launch a big campaign? Not on the customer side. The platform team coordinates with major customers running high-visibility launches; contact your account contact if you have specific timing concerns.
Will an update ever change my SEO settings or sitemaps? Updates respect existing customer settings. New defaults apply to new sites; existing sites keep what you have configured.
What is the relationship between updates and the public roadmap? The roadmap is forward-looking (what is coming); the changelog is backward-looking (what shipped). The two are kept consistent — items move from roadmap to changelog as they release.
Does the platform support an audit-friendly version history for compliance teams? The public changelog is the canonical record. For specific compliance asks, contact your account contact — some plan tiers include compliance documentation packages.
How do I find out about deprecations far in advance? Major deprecations are announced months ahead. The changelog includes a deprecations section that lists upcoming sunsets and their dates.
Related reading
Staying current with platform updates is a 5-minute-a-month habit. Subscribe to the changelog, read the weekly digest, forward to your team. The compound effect over a year is a much sharper sense of what the platform can do for you.
SGEN reliability and uptime explained — what to expect during platform incidents.
SGEN site performance explained — how to keep your site fast.
SGEN data security and privacy — how the platform handles your data.
SGEN backups and disaster recovery — recover from accidents.